Backup databases and other stuff like normal.If anyone has any suggestions on improvements or things I missed, I appreciate the effort to improve Note, this is using SCCM 1806, Windows Server 2012 R2, and I'm not using HTTPS on any of the internal facing interfaces. Please go over to the SQL group and smack them for me for pulling SRS out of SQL. Once I figured it out it actually worked pretty good. To proceed, notify your system administrator.Since I couldn't find this anywhere and it took me some time to figure out, here are the steps to upgrade in place the SQL database from 2012 to 2017. A protocol was specified in the socket function call that does not support the semantics of the socket type requested.'ĥ - ' Server failed to listen on 'any' 0. Reason: Unable to initialize the TCP/IP listener. Not support the semantics of the socket type requested.'Ĥ- 'TDSSNIClient initialization failed with error 0x2739, status code 0xa. A protocol was specified in the socket function call that does Reason: Initialization failed with an infrastructure error. To determine the cause, review the errors immediately preceding this one in the error log.'ģ - ' TDSSNIClient initialization failed with error 0x2739, status code 0x1. Check the SQL Server error log and the Windows event logs for information about possible related problems.'Ģ - 'Could not start the network library because of an internal error in the network library. In the Application logs of Event Viewer, there are 5 errors listed bellow.ġ - ' SQL Server could not spawn FRunCommunicationsManager thread.

' The SQL Server (SQLEXPRESS) service terminated with service-specific error A protocol was specified in the socket function call that does not support the semantics of the socket type requested.' In the System Event Log, Following error is listed: If this is a non-Microsoft Service, contact the service vendor, and refer to service-specific error code 10041' For more information, Review the System Event Log. 'Windows could not start the SQL Server (SQLEXPRESS) on Local Computer. Installation was completed successfully. For my application to work with the remote DB, we need to enable TCP/IP in the configuration Manger and need to restart the service.īut when the TCP/IP is enabled, the SQL service is not getting restarted. I have installed SQL 2012 Express on Windows Server 2008 R2 ( with SP1) machine.

Sql express 2012 r2