Troubleshooting: Autorotate error message

In processes that include the Autorotate activity, the following error message may be displayed: 

"The Autorotate process was restarted due to an error in the OCR engine..."

Explanation

Autorotate uses a third-party component that contains an unresolved error. XBOUND stops the process when this error occurs. The task status must then be reset and the corresponding session must be deleted. Therefore, when your process includes an Autorotate process step, the recommendations below apply.

Configuring system agents to automatically react to this error during processing

Assign the Agent for Session Removal and two instances of the Agent for Updating Task Status to a System Agent Service (see instructions).

Then set up three XBOUND agents as described below.

1. Click and configure the Agent for Session Removal as follows:

   1. Select Delete sessions based on how long root documents have been checked out.

   2. Specify a Launch removal time of 5 minutes, for example.

   3. Specify a Minimum check-out time, depending on the size of the root documents that are to be processed in the Autorotate step:

      • Average root document size <= 500 media: 30 minutes.
      • Average root document size 500 to 2000 media: 60 minutes.

   4. Under Selected activities, select only AutoRotate.

2. Click and configure one Agent for Updating Task Status:

   1. For Current task status, select Error.

   2. For New task status, select Ready.

   3. For Polling cycle, 5 minutes is recommended.

   4. In the table of activities, select only Autorotate.

3. Click and configure the other Agent for Updating Task Status:

   1. For Current task status, select Busy.

   2. For New task status, select Ready.

   3. For Polling cycle, 5 minutes is recommended.

   4. In the table of activities, select only Autorotate.

Also recommended

• Set the Instances of the Autorotate activity in the Activities Service as follows:

  • On servers with 1–3 cores: 1 instance.

  • On servers with 4 or more cores: The number of cores minus 1.

• To determine the required additional RAM, we recommend the following calculation:

  • For the first xboundWorker process: 700 MB.

  • For each additional process: 500 MB.

Resolving problems if system agents were not configured as above

1. Use the Session Manager to manually delete old sessions.

2. Use the Process Monitor to manually change the status of the affected task.

Related topics

Troubleshooting: Overview