# Common errors

This section provides troubleshooting information for commonly received errors.

## Unable to Find Pipeline.epx

If Forge fails, check the logs ( [appdir]/logs/baseline/err.forge) to make sure that Forge was able to find the pipeline.epx file in its proper location. Remember that a basic deployment template application assumes that it will find the project's pipeline.epx file in [appdir]\config\pipeline\.

On UNIX platforms, file names are case sensitive. The deployment template expects the primary pipeline file to be named pipeline.epx and the partial update pipeline (if one is required for the deployed application) to be named partial_pipeline.epx. Ensure that the files in your deployment use this capitalization.

## Missing Configuration Files

This more common error is also more difficult to detect. Since all pipelines created by the Oracle Endeca Developer Studio typically contain a Pipeline.epx file, it is unlikely that the Forge process will be unable to find the file, unless it was placed in the wrong directory. If the XML configuration files, however, have a different prefix from the deployment template [appname], these files will not be copied into the [appdir]/data/forge_output/ , [appdir]/data/dgidx_output/, and [appdir]/data/dgraphs/*/dgraph_input/ directories. All processes will likely complete successfully, but any configuration information specified by these XML files, such as search interfaces, business rules, sort keys, etc. will be missing from the resulting MDEX Engine. To correct this problem, check the XML files located in [appdir]/config/pipeline/ and make sure they have the correct prefix. Also check the directories mentioned above to make sure that these XML files are being properly copied.

## MDEX Engine Fails to Start

If an MDEX Engine fails to start, check the log for the appropriate Dgraph in [appdir]/logs/dgraphs/[dgraph]/[dgraph].log. If the log indicates that the Dgraph failed to start because no record specifier was found, follow the steps in this document to create a unique record specifier property for you project.

## Record Adapter Unable to Open File

Another common error may occur if a record adapter is unable to find or open a specified file for either input or output. In this case, the Forge error log ([appdir]/logs/baseline/err.forge) should specify which file or directory could not be found. To correct this problem, make sure the files or directories specified by the record adapters correspond to the directory structure established by the deployment template application. Note that this error may be masked if the "Require Data" property is not checked for a given input adapter, since Forge will only log a warning instead of a fatal error.

Related concepts
Input record adapters
Output record adapters