April 22, 2009 at 11:19 am
SQL 2008 Developer Edition
I was changing the SQL Server service (in SQL Server Configuration Manager) to log on w/ the LocalService vs. Network Service account.
When restarting the service, I get the following in the application event log (note: tab delimited).
Everything on the internet points me to doing:
1. Protocols properties: set Force Encryption to No (was already there).
2. Protocols properties: clear all certificates (was already clear).
All help gratefully appreciated!
Thanks!!
Wayne
----- application event log ----- (all events relating to starting the service)
TypeDateTimeSourceCategoryEventUserComputer
Error4/22/200912:41:12 PMMSSQLSERVERServer 17120N/ACQSHEFFIELDWG1SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Error4/22/200912:41:12 PMMSSQLSERVERServer 17826N/ACQSHEFFIELDWG1Could 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.
Error4/22/200912:41:12 PMMSSQLSERVERServer 17182N/ACQSHEFFIELDWG1TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
Error4/22/200912:41:12 PMMSSQLSERVERServer 17182N/ACQSHEFFIELDWG1TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
Information4/22/200912:41:12 PMMSSQLSERVERServer 26017N/ACQSHEFFIELDWG1Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
Error4/22/200912:41:12 PMMSSQLSERVERServer 17190N/ACQSHEFFIELDWG1FallBack certificate initialization failed with error code: 1.
Information4/22/200912:41:12 PMMSSQLSERVERServer 17136N/ACQSHEFFIELDWG1Clearing tempdb database.
Information4/22/200912:41:12 PMMSSQLSERVERServer 17663N/ACQSHEFFIELDWG1Server name is 'CQSHEFFIELDWG1'. This is an informational message only. No user action is required.
Information4/22/200912:41:12 PMMSSQLSERVERServer 17137N/ACQSHEFFIELDWG1Starting up database 'model'.
Information4/22/200912:41:11 PMMSSQLSERVERServer 958N/ACQSHEFFIELDWG1The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
Information4/22/200912:41:11 PMMSSQLSERVERServer 17137N/ACQSHEFFIELDWG1Starting up database 'mssqlsystemresource'.
Information4/22/200912:41:11 PMMSSQLSERVERServer 19030N/ACQSHEFFIELDWG1SQL Trace ID 1 was started by login "sa".
Information4/22/200912:41:11 PMMSSQLSERVERServer 5579N/ACQSHEFFIELDWG1FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
Information4/22/200912:41:11 PMMSSQLSERVERServer 33218N/ACQSHEFFIELDWG1SQL Server Audit has started the audits. This is an informational message. No user action is required.
Information4/22/200912:41:11 PMMSSQLSERVERServer 33217N/ACQSHEFFIELDWG1SQL Server Audit is starting the audits. This is an informational message. No user action is required.
Information4/22/200912:41:11 PMMSSQLSERVERServer 10981N/ACQSHEFFIELDWG1Resource governor reconfiguration succeeded.
Information4/22/200912:41:11 PMMSSQLSERVERServer 17137N/ACQSHEFFIELDWG1Starting up database 'master'.
Information4/22/200912:41:11 PMMSSQLSERVERServer 17152N/ACQSHEFFIELDWG1Node 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.
Information4/22/200912:41:11 PMMSSQLSERVERServer 17125N/ACQSHEFFIELDWG1Using 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.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17180N/ACQSHEFFIELDWG1SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the awe enabled option to 1 by using the sp_configure stored procedure.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17164N/ACQSHEFFIELDWG1Detected 2 CPUs. This is an informational message; no user action is required.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17162N/ACQSHEFFIELDWG1SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17110N/ACQSHEFFIELDWG1Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
Information4/22/200912:41:10 PMMSSQLSERVERServer 17176N/ACQSHEFFIELDWG1This instance of SQL Server last reported using a process ID of 4860 at 4/22/2009 12:39:01 PM (local) 4/22/2009 4:39:01 PM (UTC). This is an informational message only; no user action is required.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17111N/ACQSHEFFIELDWG1Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
Information4/22/200912:41:10 PMMSSQLSERVERServer 15268N/ACQSHEFFIELDWG1Authentication mode is MIXED.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17104N/ACQSHEFFIELDWG1Server process ID is 4128.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17103N/ACQSHEFFIELDWG1All rights reserved.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17101N/ACQSHEFFIELDWG1(c) 2005 Microsoft Corporation.
Information4/22/200912:41:10 PMMSSQLSERVERServer 17069N/ACQSHEFFIELDWG1Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Developer Edition on Windows NT 5.1
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
April 22, 2009 at 1:10 pm
Well, I got it working, by doing it the "wrong" way. I went to computer management, services, and set the logon acct that way.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply