Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Engine Administration
  Search  |  Index
Process Reference  
Process Engine Administration
Workflow administration tasks
System administration tasks
  Configuring the Process Engine
  Configuring users and groups (Workplace)
  Configuring users and groups (Open Client/FileNet Web Services Client)
  Configuring optional features
  Running the Process Engine
  Improving system performance
  Troubleshooting
    What to do when something goes wrong
    Listing the timestamps for your software
    Verifying the workflow database
    Running vwverify
   

What to do when something goes wrong

In general, each problem-solving scenario involves the following steps:

  • Trace the events leading to the problem
  • Look for the problem’s cause

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, you’ll 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 problem’s cause

For more information, see Troubleshooting.