October 2, 2009 at 1:42 pm
Getting error attempting to start instance of server LAPTOP/SQLEXPRESS. Running express edition and have had no problems until attempting to setup a new data source in Visual Basic Editor. Appreciate someone looking into this problem. I changed several settings in config manager (not sure what the original settings were - I know - not good - should have known better...). I think it was set to Network Service. I changed to local service. Here are the log entries:
2009-10-02 11:44:46.43 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86)
Mar 29 2009 10:27:29
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
2009-10-02 11:44:46.43 Server (c) 2005 Microsoft Corporation.
2009-10-02 11:44:46.43 Server All rights reserved.
2009-10-02 11:44:46.43 Server Server process ID is 4208.
2009-10-02 11:44:46.43 Server Authentication mode is MIXED.
2009-10-02 11:44:46.43 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2009-10-02 11:44:46.43 Server This instance of SQL Server last reported using a process ID of 5564 at 10/2/2009 11:43:41 AM (local) 10/2/2009 6:43:41 PM (UTC). This is an informational message only; no user action is required.
2009-10-02 11:44:46.43 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2009-10-02 11:44:46.46 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-10-02 11:44:46.46 Server Detected 1 CPUs. This is an informational message; no user action is required.
2009-10-02 11:44:46.65 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-10-02 11:44:46.76 Server Node configuration: node 0: CPU mask: 0x00000001 Active CPU mask: 0x00000001. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-10-02 11:44:46.80 spid7s Starting up database 'master'.
2009-10-02 11:44:47.02 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2009-10-02 11:44:47.06 spid7s SQL Trace ID 1 was started by login "sa".
2009-10-02 11:44:47.06 spid7s Starting up database 'mssqlsystemresource'.
2009-10-02 11:44:47.09 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2009-10-02 11:44:47.37 spid7s Server name is 'LAPTOP\SQLEXPRESS'. This is an informational message only. No user action is required.
2009-10-02 11:44:47.38 spid7s Informational: No full-text supported languages found.
2009-10-02 11:44:47.38 spid10s Starting up database 'model'.
2009-10-02 11:44:47.38 spid7s Starting up database 'msdb'.
2009-10-02 11:44:47.40 Server Error: 17190, Severity: 16, State: 1.
2009-10-02 11:44:47.40 Server Initializing the FallBack certificate failed with error code: 1, state: 1, error number: -2146893802.
2009-10-02 11:44:47.40 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-10-02 11:44:47.40 Server Error: 17182, Severity: 16, State: 1.
2009-10-02 11:44:47.40 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2009-10-02 11:44:47.40 Server Error: 17182, Severity: 16, State: 1.
2009-10-02 11:44:47.40 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-10-02 11:44:47.40 Server Error: 17826, Severity: 18, State: 3.
2009-10-02 11:44:47.40 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-10-02 11:44:47.40 Server Error: 17120, Severity: 16, State: 1.
2009-10-02 11:44:47.40 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.
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply