When you run the Event Manager run all scheduled events, Event Manager may be running an event and report the message "not responding", or act as if the application is "frozen" or "stuck" on the event, where it does not finish the event and does not move on to the next event. 

Windows may also report the open Event Manager application as "not responding." During this time, all your actions with Event Manager have no effect, and Event Manager will not stop the running event.  Other Servicing Director applications on the computer continue to respond normally. 

Workaround:

Wait for the event to complete:

• In most cases, the event is expected to be "not responding", and it is not "frozen" or "stuck".
• You may have to wait longer than normal for the event to complete for many reasons and variable factors.
• How long you have to wait depends on factors unique to your organization, and no general estimate can be made. Wait as long as you can to be sure. 
• Generally speaking, the most common Event Manager events simply select and update data on your Servicing Director database server. For example, report events are selecting data for the report, and update events are updating their related data. Import and Export events are sending or receiving data. 
• When your server completes the event, the event will finish, and the next event will be run. While the Event Manager is waiting for the server to complete the event, Windows can report the Event Manager as "not responding" and you may not be able to use the waiting Event Manager screen, and it may appear "frozen." The Event Manager will wait as long as is needed for your server to respond, and in most cases the request will not timeout or expire. 
• In an extreme example, if your server responds in 30 minutes, then the event waiting for the response will appear to be "frozen" for 30 minutes. 
• This means, apart from a specific known or identified issue for a specific version of Event Manager, then one likely root cause for the Event Manager to be slow can be from a slow response from your server. The events will be as fast as the underlying systems which it uses. Therefore, to troubleshoot the slow performance of an event, be sure to include troubleshooting for the underlying systems it uses. For example, the Microsoft Windows server and Microsoft SQL server you provided to host Servicing Director is key to the performance. Microsoft is the authority on their products, and they will have several ways to gauge or evaluate or improve the performance of their products. One of the most common ways Microsoft recommends to improve performance of a SQL server database is to "reindex or reorganize or update statistics" on any databases as often as needed. If your local IT or system administrator has not performed these Microsoft recommended steps to "reindex or reorganize or update statistics" on your Servicing Director, then have those steps performed first in your troubleshooting of this issue. 

If waiting many times longer than normal does not resolve the issue, and the event will not finish, then do the following: 

1. IMPORTANT! You may need to terminate Event Manager but do not click Run All again. Do not choose to Run All scheduled events again until troubleshooting this problem is completed, and you want to move forward and Run All scheduled events for the end of a new business day.
2. Note the exact full title of the event which would not finish. Note whether the event type was an Update (Upd), a report (Rpt), a letter (Ltr), or an import/export, as described in the title of the event.
3. Stop all users from entering new transactions. Do not enter new transactions until troubleshooting this problem is completed. Enabling Servicing Director read-only mode is one way to do this. See other articles for more information about how to enable read-only mode.
4. Confirm the transaction dates in the System Administration application by selecting Table Setup > Company, then clicking the Transactions tab. Confirm all three dates listed in the Transact Posting Dates section, for Current, Prior, and Last. See other articles about the meaning of these dates.
5. Create the Event Log By Date report from Event Manager (use another Servicing Director desktop), using the start time criteria of the last known good Run All scheduled events. Enter the StartTime > date of last known good Run All scheduled event in the criteria. See other articles about how to run the Event Log by Date report.
6. Locate and confirm your most recent Servicing Director database backup files.
7. If the event which would not finish was a report, which are events with the word Report or Rpt in their title, you may be able to continue by rebooting the Windows computer running Event Manager (which will terminate Event Manager EventMgr.exe program), and then reopening Event Manager. Do not click Run All, and run any events which were not completed individually by highlighting each individual event and clicking Run. Use the Event Log by Date report to show you which event were not completed.  Do not re-run any events which were already completed. 
8. If the event which would not finish is not a report, then do not continue until further reviewed with support. Contact support using Case Management in the Finastra Finastra Customer Success Community web site, and attach the Event Log by Date report you created to the case. 

ArticleNumber:

000063451