Troubleshooting

Version Set Problem

Solution

You are defining a job, and a file path reads "Unable to Determine File Path"

A version set has not been defined; publish a version set.

The Indexer version set is incorrect and the problem affects indexed values.

Delete the incorrect index references. Fix the DDF problem. Publish a new (correct) version set. Run Indexer against the new version set.

The Indexer version set is incorrect and the problem does not affect indexed values.

Fix the DDF problem. Publish a new (correct) version set.

You deleted the most recent version set, then index, and the job used an old version set.

System looks for and uses most recent version set. If no version set of required type exists, eaDirect generates an error. Publish a new version set.

You published the wrong or incorrect files.

Delete the incorrect version set. Publish a new version set. Consider the timing of publishing a new version set and ongoing job processing.

You published a version set to the wrong application.

Delete the incorrect version set. Publish the version set to the correct application. Consider the timing of publishing a new version set and ongoing job processing.

You published the wrong type of version set (i.e. static HTML job instead of dynamic web view)

Delete the incorrect version set. Publish the correct version set.

The view name as you defined when publishing the version set is not the exact call from the JSP.

Delete the incorrect version set. Publish a version set with the correct view name.

Auxiliary file(s) are missing.

Delete the version set and republish with all files or binary FTP/Copy file into correct directory.

When defining a version set, you selected a wrong file as required file.

Delete the version set and republish with the correct files. Or, if the wrong file and correct file have the same name, binary FTP copy the correct file over the wrong file in the version set directory.

Production Problem

Solution

A lot of jobs are failing.

Check the connections between your database and application servers.

System Problem

Solution

You have trouble logging in for the first time after installing eaDirect.

Check the connections between your database and application servers.

System services are missing.

Close Command Center and shut down and restart WebLogic from your WLHome directory.