The Run All Log File of Servicing Director Event Manager unexpectedly reports Read-Only Mode started

The Run All Log File of Servicing Director Event Manager unexpectedly reports Read-Only Mode started

When you do not have the Read-Only mode feature enabled on your Servicing Director system, the Event Manager may unexpectedly report Read-Only mode is started in the run all log file.

You have the Event Manager application automated to run all scheduled events unattended using scheduling software, such as Microsoft Task Scheduler.

Other users of Servicing Director do not find the system in Read-Only mode.

All the events may be run and be completed (with or without event errors), but this issue can cause Event Manager (the process named EventMgr.exe) to continue to run within the scheduled software and not exit or end by itself as expected.

Having a previous Event Manager left running when the next scheduled run of Event Manager starts should lead to the failure of starting the next Event Manager on the same computer.


Workaround:

First, confirm all your scheduled events completed and address any event issues by reviewing the created Event Log by Date report, specifying the date of the events you want to confirm.  Use a second computer with the Event Manager application if necessary to create the Event Log by Date report.

You have the following options:

  • Confirm you have not enabled the Servicing Director Read-Only feature, which is incompatible with an automated and unattended Event Manager. Disable the Servicing Director Read-Only feature if you are using an automated and unattended Event Manager. For more information about the Read-Only feature, search the Knowledge Center using the key words Servicing Director Read-Only.
  • There is an issue in Event Manager which causes the automated and unattended Event Manager alone to act as if Read-Only mode is enabled, which causes it to continue to run and not end or exit normally within the scheduling software after the events are completed.   
  1. You can ignore the Read-Only messages.
  2. To workaround this Event Manager issue, have your scheduling software set to automatically end or terminate the Event Manager application after an appropriate amount of time after all the events would be completed in the most extreme length of time possible for your system.  For example, if you are using Microsoft Task Scheduler to run Event Manager, then on the Microsoft Task properties Settings tab, enable the option "Stop the Task if the task run longer than" and set it to 12 hours.

ArticleNumber:

000071333