October 18, 2008 at 1:17 pm
I just installed SQL Server 2008 on my XP Pro system. Management Studio failed. I then found that SQL Server never started. I tried starting it from services with no success. I then tried to logon as a local systen account but that didn't work. The error log says "Error: 17054, Severity: 16, State: 1." Any ideas?
October 18, 2008 at 1:52 pm
Give this a read
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=337816&SiteID=1
and check the SQL Logs for more detailed logging
typically found under C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG
October 18, 2008 at 2:43 pm
I tried starting it from services with no success
And error message is?
October 18, 2008 at 3:00 pm
There was no definitive error message. Here is the log:
2008-10-18 13:51:52.57 Server Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2008-10-18 13:51:52.57 Server (c) 2005 Microsoft Corporation.
2008-10-18 13:51:52.57 Server All rights reserved.
2008-10-18 13:51:52.60 Server Server process ID is 460.
2008-10-18 13:51:52.60 Server Authentication mode is WINDOWS-ONLY.
2008-10-18 13:51:52.60 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2008-10-18 13:51:52.60 Server This instance of SQL Server last reported using a process ID of 6084 at 10/18/2008 12:12:48 PM (local) 10/18/2008 7:12:48 PM (UTC). This is an informational message only; no user action is required.
2008-10-18 13:51:52.64 Server Registry 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
2008-10-18 13:51:52.70 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-10-18 13:51:52.70 Server Detected 1 CPUs. This is an informational message; no user action is required.
2008-10-18 13:51:53.78 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.
2008-10-18 13:51:53.93 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.
2008-10-18 13:51:54.07 spid7s Starting up database 'master'.
2008-10-18 13:51:54.87 spid7s Resource governor reconfiguration succeeded.
2008-10-18 13:51:54.87 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2008-10-18 13:51:54.87 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2008-10-18 13:51:54.90 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2008-10-18 13:51:55.35 spid7s SQL Trace ID 1 was started by login "sa".
2008-10-18 13:51:55.37 spid7s Starting up database 'mssqlsystemresource'.
2008-10-18 13:51:55.43 spid7s The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2008-10-18 13:51:56.06 spid10s Starting up database 'model'.
2008-10-18 13:51:56.07 spid7s Server name is 'NEW-FROM-BYTES'. This is an informational message only. No user action is required.
2008-10-18 13:51:57.50 spid10s Clearing tempdb database.
2008-10-18 13:51:58.06 spid13s Error: 9954, Severity: 16, State: 1.
2008-10-18 13:51:58.06 spid13s SQL Server failed to communicate with filter daemon launch service (Windows error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
). Full-Text filter daemon process failed to start. Full-text search functionality will not be available.
2008-10-18 13:51:58.39 spid7s Starting up database 'msdb'.
2008-10-18 13:51:59.26 Server A self-generated certificate was successfully loaded for encryption.
2008-10-18 13:51:59.28 Server Error: 26055, Severity: 16, State: 1.
2008-10-18 13:51:59.28 Server The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.
2008-10-18 13:51:59.32 Server Error: 17182, Severity: 16, State: 1.
2008-10-18 13:51:59.32 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: Unable to initialize the VIA listener. The specified module could not be found.
2008-10-18 13:51:59.34 Server Error: 17182, Severity: 16, State: 1.
2008-10-18 13:51:59.34 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The specified module could not be found.
2008-10-18 13:51:59.34 Server Error: 17826, Severity: 18, State: 3.
2008-10-18 13:51:59.34 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.
2008-10-18 13:51:59.34 Server Error: 17120, Severity: 16, State: 1.
2008-10-18 13:51:59.34 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.
October 18, 2008 at 3:17 pm
Do you have ANY version of SQL 2005 on the same machine?
October 18, 2008 at 3:46 pm
No, but I did haveSQL Server 2005 Express on it. I removed it in favor of 2008 full version. I did an uninstall and then deleted the SQL directories in Program Files. I also ran Registry Mechanic and then rebooted.
October 18, 2008 at 3:57 pm
I fixed it! I had enabled VIA in Client Protocols in SQL Server Conig Mgr. I finally found the problem by carefully reading the error log twice and remembering what i had done to try to get SQL Server to start. Thanks for the help.
October 18, 2008 at 5:32 pm
Glad you found the problem (from the log)
2008-10-18 13:51:59.28 Server The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply