SQL Server Express 2008 instance fails to start

I've installed SQL Server Express with a named instance 'SQLSERVER2'. I was able to connect to it and reference it in the management studio. There was a problem though with Visual Studio 9 when running an ASP.NET web application that required connecting to the same instance. So, I went into the configuration manager to change the security level of the instance from network to local service. The change went through but could not restart the instance. That is what has created my next round of problems. I can't go in and change it back to network because the instance is permanently stopped. I cannot start it with the services manager. How can I fix this?

Here is the connection log:

2009-12-21 11:36:32.20 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
 Jul  9 2008 14:43:34
 Copyright (c) 1988-2008 Microsoft Corporation
 Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)

2009-12-21 11:36:32.50 Server      (c) 2005 Microsoft Corporation.
2009-12-21 11:36:32.51 Server      All rights reserved.
2009-12-21 11:36:32.51 Server      Server process ID is 21856.
2009-12-21 11:36:32.51 Server      Authentication mode is MIXED.
2009-12-21 11:36:32.53 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG'.
2009-12-21 11:36:32.89 Server      This instance of SQL Server last reported using a process ID of 3216 at 12/18/2009 6:06:56 PM (local) 12/19/2009 2:06:56 AM (UTC). This is an informational message only; no user action is required.
2009-12-21 11:36:32.89 Server      Registry startup parameters:
  -d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\master.mdf
  -e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG
  -l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\mastlog.ldf
2009-12-21 11:36:33.26 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-12-21 11:36:33.29 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2009-12-21 11:36:35.15 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2009-12-21 11:36:36.64 Server      Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-12-21 11:36:37.42 spid6s      Starting up database 'master'.
2009-12-21 11:36:38.98 spid6s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS2'.
2009-12-21 11:36:39.40 spid6s      SQL Trace ID 1 was started by login "sa".
2009-12-21 11:36:39.50 spid6s      Starting up database 'mssqlsystemresource'.
2009-12-21 11:36:39.59 spid6s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-12-21 11:36:40.14 spid10s     Starting up database 'model'.
2009-12-21 11:36:40.17 spid6s      Server name is 'USER-F19E13BA9B\SQLEXPRESS2'. This is an informational message only. No user action is required.
2009-12-21 11:36:40.56 spid6s      Informational: No full-text supported languages found.
2009-12-21 11:36:40.57 spid6s      Starting up database 'msdb'.
2009-12-21 11:36:40.60 Server      Error: 17190, Severity: 16, State: 1.
2009-12-21 11:36:40.60 Server      FallBack certificate initialization failed with error code: 1.
2009-12-21 11:36:40.70 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.

2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.

2009-12-21 11:36:40.71 Server      Error: 17826, Severity: 18, State: 3.
2009-12-21 11:36:40.71 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-12-21 11:36:40.71 Server      Error: 17120, Severity: 16, State: 1.
2009-12-21 11:36:40.71 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.

December 21st, 2009 11:08pm

I've installed SQL Server Express with a named instance 'SQLSERVER2'. I was able to connect to it and reference it in the management studio. There was a problem though with Visual Studio 9 when running an ASP.NET web application that required connecting to the same instance. So, I went into the configuration manager to change the security level of the instance from network to local service. The change went through but could not restart the instance. That is what has created my next round of problems. I can't go in and change it back to network because the instance is permanently stopped. I cannot start it with the services manager. How can I fix this?

Here is the connection log:

2009-12-21 11:36:32.20 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
 Jul  9 2008 14:43:34
 Copyright (c) 1988-2008 Microsoft Corporation
 Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)

2009-12-21 11:36:32.50 Server      (c) 2005 Microsoft Corporation.
2009-12-21 11:36:32.51 Server      All rights reserved.
2009-12-21 11:36:32.51 Server      Server process ID is 21856.
2009-12-21 11:36:32.51 Server      Authentication mode is MIXED.
2009-12-21 11:36:32.53 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG'.
2009-12-21 11:36:32.89 Server      This instance of SQL Server last reported using a process ID of 3216 at 12/18/2009 6:06:56 PM (local) 12/19/2009 2:06:56 AM (UTC). This is an informational message only; no user action is required.
2009-12-21 11:36:32.89 Server      Registry startup parameters:
  -d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\master.mdf
  -e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG
  -l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\mastlog.ldf
2009-12-21 11:36:33.26 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-12-21 11:36:33.29 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2009-12-21 11:36:35.15 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2009-12-21 11:36:36.64 Server      Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-12-21 11:36:37.42 spid6s      Starting up database 'master'.
2009-12-21 11:36:38.98 spid6s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS2'.
2009-12-21 11:36:39.40 spid6s      SQL Trace ID 1 was started by login "sa".
2009-12-21 11:36:39.50 spid6s      Starting up database 'mssqlsystemresource'.
2009-12-21 11:36:39.59 spid6s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-12-21 11:36:40.14 spid10s     Starting up database 'model'.
2009-12-21 11:36:40.17 spid6s      Server name is 'USER-F19E13BA9B\SQLEXPRESS2'. This is an informational message only. No user action is required.
2009-12-21 11:36:40.56 spid6s      Informational: No full-text supported languages found.
2009-12-21 11:36:40.57 spid6s      Starting up database 'msdb'.
2009-12-21 11:36:40.60 Server      Error: 17190, Severity: 16, State: 1.
2009-12-21 11:36:40.60 Server      FallBack certificate initialization failed with error code: 1.
2009-12-21 11:36:40.70 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.

2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.

2009-12-21 11:36:40.71 Server      Error: 17826, Severity: 18, State: 3.
2009-12-21 11:36:40.71 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-12-21 11:36:40.71 Server      Error: 17120, Severity: 16, State: 1.
2009-12-21 11:36:40.71 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.

Free Windows Admin Tool Kit Click here and download it now
December 21st, 2009 11:10pm

hi,
a question.. did you change the account running the sql server instance via the SQL Server Configuration Manager or via the "standard" services management applet?
if this is the case, please try using SSCM..
regards
December 22nd, 2009 1:48am

hi,
a question.. did you change the account running the sql server instance via the SQL Server Configuration Manager or via the "standard" services management applet?
if this is the case, please try using SSCM..
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2009 2:17am

Please check these ,

1. Check 'Forced Encryption' (Turned False) and 'Certificate' value is cleared under SQL Server Configuration Manager.
2> Check the following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQL2008\MSSQLServer\SuperSocketNetLib\Certificate
and clear the Certificate values.
December 22nd, 2009 4:38am

Please check these ,

1. Check 'Forced Encryption' (Turned False) and 'Certificate' value is cleared under SQL Server Configuration Manager.
2> Check the following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQL2008\MSSQLServer\SuperSocketNetLib\Certificate
and clear the Certificate v
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2009 11:35pm

Hi,

This problem can occur if the new Service Account does not have a profile on the machine. To resolve the issue connect to the SQL Server machine using the New Service account. This will create a profile for the user.

SQL Server creates a self-generated certificate if a certificate is not explicitly specified and/or is not installed. This information is saved in the profile for the SQL Server service account. If the profile has not been created then SQL cannot register the self-generated certificate.

If there are any more questions, please let me know.
Thanks.
December 23rd, 2009 12:41pm

Hi,

This problem can occur if the new Service Account does not have a profile on the machine. To resolve the issue connect to the SQL Server machine using the New Service account. This will create a profile for the user.

SQL Server creates a self-generated certificate if a certificate is not explicitly specified and/or is not installed. This information is saved in the profile for the SQL Server service account. If the profile has not been created then SQL cannot register the self-generated certificate.

If there are any more questions, please let me know.
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2009 8:00pm

Hi,

The service account I mentioned is the account used to start the SQL Server service. You could check the SQL Server service account by using the following steps:
1. Open SQL Server Configuration Manager.
2. In SQL Server Configuration Manager, expand Services, and then double click SQL Server (<instance_name>).
3. In the SQL Server Properties dialog box, you could check the log on account.

In this case, the error might be caused by the SQL Server service account not having a profile on the machine. To work around it, you could use this account to log on the machine that is running SQL Server.

If there are any more questions, please let me know.
Thanks and Merry Christmas.
December 24th, 2009 9:53am

The logon account to sql server is the 'Built-in account'. It was installed as a 'Network Service'. I was able to start and stop the instance but not able to connect through an ASP.NET web application. So, I changed it to 'Local Service', since everything is running on my PC. Configuration manager was able to stop the instance and update the security context but could not restart it. I tried to switch it to 'This account' and tried a number of accounts starting with my logon that I use for the PC. Tried to apply it but the message returned says I've entered an 'invalid network password'. Don't understand this message at all. Since it's asking me to confirm the password, I have to assume I'm assigning a password and not trying to authenticate at this time. Sorry for my ignorance...
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2009 2:03am

create it works on os-2012 with sql-2012 AAG.

solved after x hours troubleshooting

regards

Dean

February 7th, 2014 4:44am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics