Users cannot save documents due to slow performance

Overview

This article provides a workaround that can be implemented when Everest exhibits progressive performance degradation resulting in the inability for users to save documents (e.g. Sales Orders) coupled with out-of-memory errors unless the server is rebooted.

Rebooting the server is often a temporary reprieve as the inability to save documents and users experiencing slow performance can resurface days later necessitating yet another server reboot.

Solution

The above symptoms point to memory overutilization causing a database performance problem which can be confirmed by examining the SQL server logs for the following errors:

To mitigate the above problem, create a scheduled Windows task to execute a script that will restart SQL Server services and kill all tasks that are causing memory overutilization. 

The Windows task scheduler can be configured to execute the following script weekly or more often depending on the frequency of the performance degradation, ideally during after-hours when there are no users logged in:

@ECHO OFF
NET STOP SQLSERVERAGENT
NET STOP MSSQLSERVER
TASKKILL /F /IM dllhost.exe
NET START MSSQLSERVER
NET START SQLSERVERAGENT

The above workaround will alleviate the need for frequent server reboots and restore acceptable performance for Everest users.

Refer to How to Schedule PowerShell Script using Task Scheduler for more information on configuring the Windows Task Scheduler to execute the above script.

Back to top