Post reply

Error 549 in Event Log - The connection to the SQL Server has failed

  • February 7, 2014 at 5:13 am

    #303796

    Guys,

    I'm getting a recurring error 549 in the Application event log from the "SQL Server Store" every few seconds on a server. The system then generates a "The SQL Server connection has been restored" info event shortly afterwards. This appears to be continual.

    I can't find any information the Internet regarding this. Anyone got a clue what may be causing it?

    Thanks.

    Here's the event in full:

    "The description for Event ID 549 from source SQL Server Store cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    The connection to the SQL Server has failed"

  • February 7, 2014 at 5:56 am

    #1686991

    The message states the error could be originated from another computer. Perhaps an application server that keeps trying to connect... Can you find out this other computer? Perhaps the Event log on that computer has a more descriptive message.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • February 7, 2014 at 5:59 am

    #1686993

    And is there additional information in the SQL Error logs?

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • February 7, 2014 at 6:08 am

    #1686999

    As far as the event log is concerned, the 'Computer' field points to itself. There's nothing in the SQL logs either.

  • February 7, 2014 at 6:13 am

    #1687001

    Is this on a dedicated SQL Server or on a combined Application/SQL server?

    Look for some kind of polling mechanism (because you get the message frequently). This could be a (powershell-)script, a scheduled job, etc.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • February 7, 2014 at 6:16 am

    #1687002

    Application and SQL server.

  • February 7, 2014 at 6:26 am

    #1687007

    john.doolan (2/7/2014)

    Application and SQL server.

    Can you check if the application is the cause of these messages (if possible temporarily shut down the application/service)?

    Assuming the application is the cause:

    - Does the application has it's own logging?

    - Is the application using a correct connection method/string?

    - Can you contact the vendor of this application about the messages?

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

Viewing 7 posts - 1 through 7 (of 7 total)

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