November 9, 2004 at 12:17 pm
Here's the scenario:
On a developer machine, I'm installing SQL2005 Beta 2 I got from the PASS conference.
Machine has a default instance of SQL7, a named instance of SQL2000, and now a named instance of SQL2005.
After installation, I can use the SQL Server Management Studio to connect to all three instances, but existing applications cannot connect to the new named instance.
I found this reference and tried to do the steps outlined in it:
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
the steps were basically this:
run sqlcmd -S.\sqlexpress from a command prompt to see if this is working.
Enable Np and TCP in Server Network Configuration
net stop the service MSSQL$SQL2005
net start the service MSSQL$SQL2005
net start sqlbrowser
The problem is that after stopping the service, it cannot be restarted again.
uninstalling SQL 2005 beta and reinstalling lets me get the service running again, but stopping it by following the steps above, results in it in a condition where it never starts again.
running the same command called as the service reveals some more detailed errors pasted below, but I cannot seem to google the errors raised to find a resolution.
Can anyone help me get started on this issue?
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" -sSQL2005
C:\Documents and Settings\lizaguirre>"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" -sSQL2005
2004-11-09 13:50:47.13 Server Authentication mode is MIXED.
2004-11-09 13:50:47.14 Server Microsoft SQL Server Yukon - 9.00.852 (IntelX86) Jul 19 2004 22:09:12 Copyright (c) 1988-2003 Microsoft Corporation Beta Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2004-11-09 13:50:47.14 Server (c) 2004 Microsoft Corporation.
2004-11-09 13:50:47.14 Server All rights reserved.
2004-11-09 13:50:47.14 Server Server process ID is 2772.
2004-11-09 13:50:47.14 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2004-11-09 13:50:47.14 Server This instance of SQL Server last reported using a process ID of 2888 at 11/9/2004 1:49:00 PM (local) 11/9/2004 6:49:00 PM (UTC). This is an informational message only; no user action is required.
2004-11-09 13:50:47.14 Server Registry startup parameters:
2004-11-09 13:50:47.14 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2004-11-09 13:50:47.14 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2004-11-09 13:50:47.14 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2004-11-09 13:50:47.14 Server Command Line Startup Parameters:
2004-11-09 13:50:47.14 Server -s SQL2005
2004-11-09 13:50:47.16 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2004-11-09 13:50:47.16 Server Detected 1 CPUs. This is an informational message; no user action is required.
2004-11-09 13:50:47.22 Server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2004-11-09 13:50:47.25 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2004-11-09 13:50:48.27 Server Database mirroring has been enabled on this instance of SQL Server.
2004-11-09 13:50:48.27 spid4s Starting up database 'master'.
2004-11-09 13:50:48.46 spid4s SQL Trace started. Trace ID = '1'. Login Name = 'sa'.
2004-11-09 13:50:48.49 spid4s Starting up database 'mssqlsystemresource'.
2004-11-09 13:50:48.71 Server Error: 17182, Severity: 16, State: 1.
2004-11-09 13:50:48.71 Server TDSSNIClient initialization failed with error 0xd, status code 0x36.
2004-11-09 13:50:48.71 spid7s Starting up database 'model'.
2004-11-09 13:50:48.71 Server Error: 17182, Severity: 16, State: 1.
2004-11-09 13:50:48.71 Server TDSSNIClient initialization failed with error 0xd, status code 0x1.
2004-11-09 13:50:48.71 Server Error: 17826, Severity: 18, State: 3.
2004-11-09 13:50:48.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.
2004-11-09 13:50:48.71 Server Error: 17120, Severity: 16, State: 1.
2004-11-09 13:50:48.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.
Lowell
November 9, 2004 at 12:59 pm
In theSQL Computer Manager>>Server Network Configuration, for Server Protocols, I had additionally enabled the "Via" selection. disabling this setting allowed my instance to start, and I can connect to it with the SQl Server Management Studio, but have not resolved the Application connection issue;
essentially I've restored a database backup from a SQL 2000 machine on the 2005 instance; using ADO i'm trying to connect with a connection string that looks like this:
for a SQL2000 db, this works fine:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=whatever;Initial Catalog=gmfl;Network Library=dbnetlib;Data Source=lowelli\sql2000;
for SQL2005, this fails:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=whatever;Initial Catalog=gmfl;Network Library=dbnetlib;Data Source=lowelli\sql2005;
Lowell
November 10, 2004 at 8:04 am
Not sure whether you can access the following newsgroup, it's about sql2k5 beta2. Maybe you can some help from there.
http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us
November 10, 2004 at 8:20 am
I'm slowly growing here.....
my issue was the provider in the connection string...i had assumed that the provider I currently use, SQLOLEDB /SQLOLEDB.1 would work for all versions of SQL; it works only for SQL 7 and SQL 2000;
for 2005 i had to change the provider to SQLNCLI (SQL Native Client);
I also tweaked the Netowrk Library to make sure i used DBNETLIB.
Once that was done, i was able to use my application (vb6 based) to connect.
Lowell
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply