March 29, 2006 at 3:32 pm
DB-Library: Unable to connect: SQL Server is unavailable or does not exist. Unable to connect: SQL Server does not exist or network access denied.
Net-Library error 2: ConnectionOpen (Connect()).
When I try to run ISQL from the cmd line locally and use Enterprise Mgr remotely I cannot connect.
Any suggestions?
I did not use port 1433...
March 29, 2006 at 3:53 pm
If it is MSDE than you have to enable network protocols first. If it is not MSDE, use Server Network utility and check the port. After that create an entry in Client Network utility for your port.
In both cases make sure that SQL Server service is started. Sometimes it is not started after applying the service pack, you have to start is yourself.
Regards,Yelena Varsha
March 29, 2006 at 4:23 pm
Yelena,
It is a SQL Server. I made sure the port was active and listening and I opened the Client Network Utility and found it setup on 1433 and changed it to the port I am using and I still get the error.
March 30, 2006 at 12:48 am
Could you please check latest SQL Server Error Log. It will be avaialble under <DriveLetter>:\Program Files\Microsoft SQL Server\MSSQL$M<InstanceName>\LOG
Here you will find Port and Protocols where SQL is Listening.
Paste the error log in next post. We may get some idea about whats going on.
Feel free to ping me at bmlakhani@yahoo.com
March 30, 2006 at 8:39 am
Les,
In addition to posting here several entries for the port and protocol from the SQL Server Error log from the startup part of the log as Balmukund asked you may want to try to create another entry in the Client Network Utility for the Named Pipes and try connection over the Named Pipes.
Yelena
Regards,Yelena Varsha
March 30, 2006 at 8:50 am
2006-03-29 20:08:53.38 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-03-29 20:08:53.38 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-03-29 20:08:53.38 server All rights reserved.
2006-03-29 20:08:53.38 server Server Process ID is 4620.
2006-03-29 20:08:53.38 server Logging SQL Server messages in file 'e:\SQL Server\Data\MSSQL$HOUDBSQL01P\log\ERRORLOG'.
2006-03-29 20:08:53.39 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2006-03-29 20:08:53.44 server SQL Server configured for thread mode processing.
2006-03-29 20:08:53.44 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2006-03-29 20:08:53.52 server Attempting to initialize Distributed Transaction Coordinator.
2006-03-29 20:08:54.55 spid3 Starting up database 'master'.
2006-03-29 20:08:54.77 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-03-29 20:08:54.77 spid5 Starting up database 'model'.
2006-03-29 20:08:54.79 server SQL server listening on 192.xxxx81: 1967.
2006-03-29 20:08:54.79 server SQL server listening on 12x.xxx.1: 1967.
2006-03-29 20:08:54.79 spid3 Server name is 'HOUDBSQL01P\HOUDBSQL01P'.
2006-03-29 20:08:54.79 spid8 Starting up database 'msdb'.
2006-03-29 20:08:54.79 spid9 Starting up database 'pubs'.
2006-03-29 20:08:54.85 server SQL server listening on TCP, Shared Memory, Named Pipes.
2006-03-29 20:08:54.85 server SQL Server is ready for client connections
2006-03-29 20:08:55.05 spid5 Clearing tempdb database.
2006-03-29 20:08:55.91 spid5 Starting up database 'tempdb'.
2006-03-29 20:08:56.07 spid3 Recovery complete.
2006-03-29 20:08:56.07 spid3 SQL global counter collection task is created.
2006-03-29 20:09:27.51 spid51 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
2006-03-29 20:12:25.77 spid53 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'sp_MSgetversion'.
March 30, 2006 at 9:07 am
Very Good!
Do you use HOUDBSQL01P\HOUDBSQL01P as a server name when trying to connect or in the Client / network utility? It is obvious that you have installed Named Instance so you have to address it as servername\instancename. I would go into Client Network Utility and in the Server Name textbox of your entry enter HOUDBSQL01P\HOUDBSQL01P, specify your port as you probably already did and for the Server Alias textbox enter some convenient name like SQL01P and when you try to use your Enterprise Manager or OSQL or an application always use this convenient name. Do not forget, Client Network Utility entry MUST be on Every client that connects to your server because of the custom port and the named instance (latest for your convenience)
Regards,Yelena Varsha
March 30, 2006 at 9:23 am
This corrected the issue thanks. This is what happens when you become a useless mgr.
thanks a lot!
Les
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply