Tuesday, March 27, 2012

Error installing SQL Server 2005 on Vista

Here's the ERRORLOG:

2007-05-15 01:52:05.69 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 6.0 (Build 6000: )

2007-05-15 01:52:05.69 Server (c) 2005 Microsoft Corporation.
2007-05-15 01:52:05.69 Server All rights reserved.
2007-05-15 01:52:05.69 Server Server process ID is 3860.
2007-05-15 01:52:05.69 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-05-15 01:52:05.69 Server This instance of SQL Server last reported using a process ID of 3252 at 5/15/2007 1:51:57 AM (local) 5/15/2007 6:51:57 AM (UTC). This is an informational message only; no user action is required.
2007-05-15 01:52:05.69 Server Registry startup parameters:
2007-05-15 01:52:05.69 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-05-15 01:52:05.69 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-05-15 01:52:05.69 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-05-15 01:52:05.69 Server Command Line Startup Parameters:
2007-05-15 01:52:05.69 Server -m SqlSetup
2007-05-15 01:52:05.69 Server SqlSetup
2007-05-15 01:52:05.69 Server -Q
2007-05-15 01:52:05.69 Server -q SQL_Latin1_General_CP1_CI_AS
2007-05-15 01:52:05.69 Server -T 4022
2007-05-15 01:52:05.69 Server -T 3659
2007-05-15 01:52:05.69 Server -T 3610
2007-05-15 01:52:05.69 Server -T 4010
2007-05-15 01:52:05.70 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-05-15 01:52:05.70 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-05-15 01:52:05.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.
2007-05-15 01:52:05.78 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-05-15 01:52:07.85 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-05-15 01:52:07.85 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-05-15 01:52:07.85 spid5s Warning ******************
2007-05-15 01:52:07.85 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2007-05-15 01:52:07.85 spid5s Starting up database 'master'.
2007-05-15 01:52:08.17 spid5s SQL Trace ID 1 was started by login "sa".
2007-05-15 01:52:08.22 spid5s Starting up database 'mssqlsystemresource'.
2007-05-15 01:52:08.61 spid8s Starting up database 'model'.
2007-05-15 01:52:08.61 Server Error: 17182, Severity: 16, State: 1.
2007-05-15 01:52:08.61 Server TDSSNIClient initialization failed with error 0x2, status code 0x80.
2007-05-15 01:52:08.61 Server Error: 17182, Severity: 16, State: 1.
2007-05-15 01:52:08.61 Server TDSSNIClient initialization failed with error 0x2, status code 0x1.
2007-05-15 01:52:08.61 Server Error: 17826, Severity: 18, State: 3.
2007-05-15 01:52:08.61 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.
2007-05-15 01:52:08.61 Server Error: 17120, Severity: 16, State: 1.
2007-05-15 01:52:08.61 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.

It is a good idea to read this blog about Vista/SQL Server issues.

SQL Server 2005 Express and Vista
http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

|||

I've already read that, didn't help. That blog is basically talking about giving users sysadmin rights.

The problem I'm having is related to the TNSSNIClient, and I'm guessing it's related to SSL certificates, but that's as far as I can go with it. I've googled every error message, every event code, and every combination of words that relate to the problem, and haven't found a solution yet.

|||I've tried everything I can think of... Anyone?sql

No comments:

Post a Comment