Applications freeze or appear to be slow and show as not responding

Applications freeze or appear to be slow and show as not responding

The Servicing Director applications appear to be slow, where the time between a screen action and a result on the screen takes longer than expected. 

Windows reports the open Servicing Director applications are "not responding." You can't use the applications when during this time, with all actions having no effect on the applications screen. and the screens appear to "freeze" or appear "stuck" for a long period of time.

The slowness repeats with certain application actions, such as posting payments, and more than one desktop doing the same actions has the same slowness. The slowness can also occur across all desktops at the same time, for all applications actions.

Workaround:

This information is for your system administrator or local IT. 

  • Generally speaking, the Servicing Director applications simply select and update data from your Servicing Director database server. When your server responds with the data, the applications display the data.
  •  While the applications are waiting for a response, Windows can report the applications as "not responding" and you may not be able to use the waiting application screen, and it may appear "frozen." The applications 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 10 minutes, then the open application waiting for the response will appear to be "frozen." for 10 minutes.
  • This means, apart from a specific known or identified issue for a specific version of Servicing Director, then one likely root cause for the applications to be slow can be from a slow response from your server. 
Note: The Event Manager application may be the most demanding of your underlying systems, selecting, updating, importing and exporting data from your server. The performance of each event in Event Manager may vary, depending the on the event. Like described in this article, if an Event Manager event is waiting for the server to complete the request, the Event Manager application will be reported as "not responding" and the Event Manager application will appear "frozen" on the currently running event. 
  • If at all possible, do not terminate, interrupt or stop your Servicing Director applications when they are most likely waiting for your server to complete a request. Wait as long as possible for the server to respond. 
  • It can be particularly important to not terminate, interrupt, or stop your Event Manager application during the end of day Run All scheduled events. For more information, review Servicing Director Event Manager Shows as "Not Responding", "Frozen" or "Stuck" on an Event 
  • The Servicing Director applications will be as fast as the underlying systems which it uses. Therefore, to troubleshoot the slow performance of the applications, be sure to include troubleshooting for the underlying systems it uses. 
  • 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 and update statistics" on any databases as often as needed. Database indexes are commonly key to accessing data quickly on a SQL server. As data is changed on a database, the indexes and statistics for the data may need to be periodically updated. Applying this recommendation to the Servicing Director server would mean to be sure you are reindexing the entire database named Service. You may need to do this nightly if you find reindexing helps your performance significantly. Reindexing the entire database can update all indexes which may need to be updated.  Add to this updating the statistics of the entire Service database.
  • Reindexing, updating statistics, and other Microsoft recommendations for performance should be evaluated and applied as needed. Other factors such as memory,  hard drive bottle necks or networking bottlenecks could also contribute to slowness. The server may also have other tasks or demands on it depending on if you have other non-Servicing Director databases or other roles for the server. These other demands may redirect server resources to the other demands at times, leaving less for your Servicing Director tasks and slower performance. Additionally, if your development resources created custom programming or reporting for the Servicing Director system, check the design of the custom additions to see if they are a source of slower performance.

ArticleNumber:

000063443