• Content
  • Comments (0)
  • Related articles
Jun
15
2012

Microsoft Windows Server 2003 – Event ID: 7024 / 2000 – SQL Server Service Terminated Friday, 15 June 2012

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7024
Description: The SQL Server (SERVER) service terminated with service-specific error 10049 (0x2741).
Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:  2000
Description: The server’s call to a system service failed unexpectedly
Event Type:    Error
Event Source:    MSSQL$SERVER
Event Category:    Server
Event ID:    26024
Description: Server failed to listen on 192.168.0.150 1433. Error: 0x2741. To proceed, notify your system administrator.
Event Type:    Error
Event Source:    MSSQL$SERVER
Event Category:    Server
Event ID:    17182
Description: TDSSNIClient initialization failed with error 0x2741, status code 0xa. Reason: Unable to initialize the TCP/IP listener. The requested address is not valid in its context.
Event Type:    Error
Event Source:    MSSQL$SERVER
Event Category:    Server
Event ID:    17182
Description: TDSSNIClient initialization failed with error 0x2741, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The requested address is not valid in its context.
Event Type:    Error
Event Source:    MSSQL$SERVER
Event Category:    Server
Event ID:    17826
Description: 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.
Event Type:    Error
Event Source:    MSSQL$SERVER
Event Category:    Server
Event ID:    17120
Description: SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

 

Resolution:

  •  The problem is network interface (NIC) IP Address related. All addresses declared on SQL Server service TCP/IP* must be active and operational, else SQL Server will not start properly.

 *SQL Server service TCP/IP – Service and Applications > SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for SERVER > TCP/IP (Properties) > IP Addresses

  • In case of VPN interface that is activated on demand there is another option, to set SQL Service > Recovery > First / Second / Subsequent failures > Restart the Service. May work in case of imediat VPN interface activation, incoming client connection.

 

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*