Error: Database Connection Lost (Server) - SQL Server is too busy and is not processing requests

From WebWatchBotWiki
Jump to: navigation, search
 Share 

Summary

Entries in the Windows Event Application log show from WebWatchBot the error: "Database Connection Lost (Server) - SQL Server is too busy and is not processing requests. The WebWatchBot service will restart."

Problem/Cause

The communication link between WebWatchBot and SQL Server is controls by ODBC drivers. When there is too much communication traffic between the two, SQL Server and/or the ODBC driver will break the connection without warning to WebWatchBot. The error occurs more frequently with older ODBC drivers.

Resolution/Workaround

To reduce the occurance of this problem, ensure you have the newest drivers installed. It is highly recommended that the "Microsoft SQL Server 2005/2008 Native Client" is installed.

Download Links Microsoft SQL Server 2008 Feature Pack, August 2008: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=16177

Once it is installed:

  1. Stop the WebWatchBot Service
  2. Close WebWatchBot Manager
  3. Run WWBUpgrade.exe, located in the install folder C:\Program Files\WebWatchBot 5\
  4. Check the log file “wwbupgrade_log.txt”, which is in C:\ProgramData\ExclamationSoft\WebWatchBot 5, or can be located by starting WebWatchBot Manager and select the menu options: Help -> ExclamationSoft Support -> View Data Folder. At the bottom of the log file, check for text stating that the new connection string has been tested successfully.