When you run the Event Manager run all scheduled events, you may find the time to complete all the events appears slow or takes longer.  It may appear the performance of Event Manager is slow. You may find the time to complete all the events is increasing or at certain times, such as the end of the month, completing all the events takes longer.

During the run all 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 Event Manager to complete all the events:

• In most cases, the Event Manager has an ever increasing amount of data and processing to complete, as your loan portfolio and other transactions increase. Periodically, such as around the end of the month, you may have even more events and processing added to your daily events. The increasing data and processing leads to needing more time to complete all the events, and as time goes by, completing all the events should be expected to take more time.
• Interacting with an running event is expected to display as "not responding", and it is not "frozen" or "stuck".
• You may have to wait longer than expected for Event Manager to complete all the events 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.  Completing all the events then takes as much time as the total time of all the events run one at a time in sequence.
• 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.
• Not all events will take the same amount of time to complete.  Create the Event Log by Date report for a date range you specific in the report criteria, and you will see the start and end time of each event in the report.  Review the start and end times of the events in the report, and you may find one or a few events which take most the total time to complete all the events. Note which events are taking most of the time.  For more information about creating the Event Log by Date report, search Knowledge Center with the key words Servicing Director Event Log by Date.
• It is not recommended to end or stop Event Manager during the run all events.  If you should ever stop Event Manager during the run all events, be sure to never click the Run All again for the same business day, or you may lose data.

ArticleNumber:

000071929