Database Engine becomes unresponsive

  • Hi All,

    Running MSSQL Server 2005 Enterprise Edition.

    Recently there's been an upgrade to an application and ever since we are seeing an issue.

    Randomly the application server starts reporting that it's unable to connect to the database. I'm able to remotely login on the SQL Server...but I'm not able to login on the database engine. It throws an "error occurred while establishing connection to SQL server"

    There is no CPU or memory issue on the server. CPU is around 10% and free mem around 1GB

    The resolution is to restart the app server...then SQL is fine. Once I can get in, checking the error logs...there are no errors of note. The only error I see is "I/O requests taking longer than 15 seconds" around the time the issue was experienced. Each time this happens, the I/O error is for different data files.

    Checking the Event Viewer I see the following -

    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSSQLSERVER service.

    I'm not sure if it's a connection issue with the application server...I'm not sure how I would investigate this

    Looking at the wait types...there's nothing I see different to other SQL servers

  • Denesh Naidoo (6/18/2013)


    The resolution is to restart the app server...then SQL is fine. Once I can get in, checking the error logs...there are no errors of note. The only error I see is "I/O requests taking longer than 15 seconds" around the time the issue was experienced. Each time this happens, the I/O error is for different data files.

    Can you check the drive system for any malfunctions? the error messsage is obvious with either Io issue or your IO is not be able to catch large number of transaction,(but in your case, you cant be able to login).

    I see connection problem could be from different area. Is this connection failure is intermittent?

  • Thanks for your response.

    Yes...its very random.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply