Post reply

SQL Server is terminating in response to a 'stop' request from Service Control Manager

  • August 26, 2008 at 7:24 am

    #130990

    Hello,

    I've got one serous problem that i cant check what is happening, at the same hour of yesterday and today my SQL Server instance shut downs without any human interaction.

    The error that i can see in error log is as follow (i get this error by the eventvwr)

    Date26-08-2008 8:35:45

    LogWindows NT (Application)

    SourceMSSQL$SQLSRV_1

    CategoryServer

    Event3221243528

    UserSGPSEXTRA\MOSService

    ComputerPC09PPSER119

    Message

    The client was unable to reuse a session with SPID 105, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

    Then:

    SQL Server is terminating in response to a 'stop' request from Service Control Manager..

    Can you help me or send me information that i can send you to check this problem.

    Thanks and regards,

    JMSM 😉

  • August 26, 2008 at 8:16 am

    #863155

    I saw something similar a few years ago, but I can't remember what was causing it. I'd call PSS since this is one of those strange errors and they can probably solve it quickly.

  • August 26, 2008 at 8:44 am

    #863195

    Hi there,

    Thanks a lot but my SQL Server instance is SQL Server 2005, is there any tool so that i can get the same info that is given by PSSCONFIG

    thanks and regards

    JMSM 😉

  • March 29, 2010 at 4:48 am

    #1141303

    Did you ever find a fix for this issue? I have had the same thing happen on a SQL 2005 box.

    Thanks

  • March 29, 2010 at 6:03 am

    #1141353

    If this has happened to you recently and you're running Windows 2003 SP 2, you need to check out the following links:

    Microsoft Support about SP2 and TCP Chimney

    KB Alertz about 2003 SP2 and TCP Chimney

    Basically the same article, slightly different info in each. Apparently this is a MAJOR deal.

    EDIT: The SQL Error message isn't the exact same, but it's something to check, anyway.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • March 31, 2010 at 3:09 am

    #1142910

    Thanks for the help, I will investigate.

    Much appreciated.

  • February 1, 2011 at 12:14 pm

    #1281105

    Hello,

    I have the same exact issue, can u please let me know how it was resolved..? all I see on google is people having problems and no solutions.

    01/26/2011 09:33:37,spid5s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    01/26/2011 09:33:37,spid5s,Unknown,SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.

    01/26/2011 09:33:37,spid12s,Unknown,Service Broker manager has shut down.

    01/26/2011 09:33:36,spid52,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

    Mine is a QA box luckily. configuration as below

    Windows 2003 service pk 2, 2GB RAM

    SQL Standards Edition 9.3.4035 Sv.pk level 3

  • June 30, 2011 at 3:14 pm

    #1346773

    I have the same issue. Any one has solutions about this?

    Thanks

  • July 1, 2011 at 4:55 am

    #1346939

    Did you check the links I posted and tried the solutions in them?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • September 5, 2012 at 1:03 am

    #1533644

    What about MS Server 2008 R2 (std) and SQL Server 2008 R2 (std).

    The issue is still there, would the solution work in this environment as well?

Viewing 10 posts - 1 through 9 (of 9 total)

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