MSSQLSERVER can't be started after updates
Results 1 to 5 of 5

Thread: MSSQLSERVER can't be started after updates

  1. #1
    Banned
    Join Date
    Aug 2001
    Location
    Yes
    Posts
    4,429

    MSSQLSERVER can't be started after updates

    Just had something strange happen.

    I install some updates (KB973825, 961371, 972260, 972636), reboot the box (Server 2003, SQL Server 2005), and I can't connect to the database anymore. I try manually starting MSSQLSERVER, but I get "The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

    Here's what the logs say:


    2009-08-10 12:39:43.76 Server Error: 17182, Severity: 16, State: 1.
    2009-08-10 12:39:43.76 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60.
    2009-08-10 12:39:43.76 Server Error: 17182, Severity: 16, State: 1.
    2009-08-10 12:39:43.76 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1.
    2009-08-10 12:39:43.76 Server Error: 17826, Severity: 18, State: 3.
    2009-08-10 12:39:43.76 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2009-08-10 12:39:43.76 Server Error: 17120, Severity: 16, State: 1.
    2009-08-10 12:39:43.76 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    I look up that error, and find this - http://blogs.msdn.com/sql_protocols/...31/487090.aspx

    Check what network protocols are enabled for SQL Server in the SQL Configuration Manager application. If the VIA protocol is enabled disable it and then try starting the SQL Server service again.
    Sure enough, that did the trick...

    Anyone have any idea why this would happen? This is our dev server - now I'm paranoid about installing those updates on the live server (although it seems unlikely that the updates would cause this), even though I know how to solve it...

  2. #2
    AO's Filibustier Cheap Scotch Ron's Avatar
    Join Date
    Nov 2008
    Location
    Swamps of Jersey
    Posts
    378
    Neg, Just curious...Why are you using VIA protocol? Not typical. Usually TCPIP or Named Pipes. In fact, I've never seen VIA enabled. Special hardware?
    In God We Trust....Everything else we backup.

  3. #3
    Banned
    Join Date
    Aug 2001
    Location
    Yes
    Posts
    4,429
    Good question... I have come to realize that something (one of the updates?) must have enabled VIA. I installed the database and I'm the sole administrator for that dev box - and I know for sure I didn't enable VIA...

  4. #4
    AO's Filibustier Cheap Scotch Ron's Avatar
    Join Date
    Nov 2008
    Location
    Swamps of Jersey
    Posts
    378
    Yup. Been there too. I've had problems with updates changing connection protocol configs. No idea why.
    In God We Trust....Everything else we backup.

  5. #5
    Banned
    Join Date
    Aug 2001
    Location
    Yes
    Posts
    4,429
    Very strange... Thanks!

Similar Threads

  1. Windows Error Messages
    By cheyenne1212 in forum Miscellaneous Security Discussions
    Replies: 7
    Last Post: February 1st, 2012, 01:51 PM
  2. Administrative Tools - Services
    By carenath in forum Operating Systems
    Replies: 8
    Last Post: January 8th, 2006, 05:03 AM
  3. MS Baseline Security Analyzer
    By Vorlin in forum Microsoft Security Discussions
    Replies: 6
    Last Post: October 31st, 2004, 02:41 AM
  4. October MS updates
    By mohaughn in forum Microsoft Security Discussions
    Replies: 2
    Last Post: October 13th, 2004, 04:31 AM
  5. Replies: 6
    Last Post: October 5th, 2004, 08:26 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •