![]() ![]() |
|
Help for Process Engine Administration | |
Search | Index | |
![]() |
|
![]() |
![]() |
![]() |
What to do when something goes wrongIn general, each problem-solving scenario involves the following steps:
Step 1: Trace the events leading to the problem Gather any messages that the Process Engine has written to the log files. The log files record exceptions that occur during normal processing, or debugging information to be used by your FileNet support representative. Maintaining the log files describes each log file. Once you have gathered the messages logged by the Process Engine up to the time the problem occurred, place the messages in chronological order. In many cases, youll notice that a message that was encountered on an Application Engine or web server was actually the result of something that happened on the Process Engine previously. Depending on the type of error or problem on the Process Engine, numerous Application Engine or web server messages that seem unrelated might be explained (and potentially ignored) because they were caused by a single problem on the Process Engine. Step 2: Look for the problems cause For more information, see Troubleshooting.
|
![]() |
|
![]() |
|