June 12, 2007 at 10:54 pm
Hi,
I have installed SQL Server 2K and SQL Server 2K5 on same box. First,I installed SQL Server 2K5 and then 2K.
2K5 is working fine..I am able to connect my server from client. But while trying to connect to SQL 2K from client, it is giving me error and I am not able to connect to the SQL Servr 2K installed on server machine.
June 13, 2007 at 12:17 pm
What error are you getting? What client are you using? (QA, application, EM?)
June 14, 2007 at 4:38 am
Hi,
I installed SQL Server 2K5 first and then SQL Server2K then.
On server machines both are running fine but on client machine, it is giving me following error:
A connection could not be established to the ServerName
REason: SQL Server doesnot exist or access denied
ConnectionOpen(Connect())..
Please verify SQL Server is running and check for SQL registration properties and try again.
I cannot uninstall SQL SErver2005 and then try installing SQL Server 2000 again.
I am in a urgent need.Any help is appreciated.
June 14, 2007 at 5:02 am
I found the following error logged in the log file:
SuperSocket Info: Bind failed on TCP port 1433.
What can the reason for this error?
June 14, 2007 at 6:48 am
Is SQL Server running with port 1433. If so try with servername,1433. Else check whats the port being used by sql and login with that port.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
June 14, 2007 at 7:35 am
Started to play around with SQL Server 2005 Express the other day.
It would be useful to know how (with what) you are trying to connect from the remote clients.
In any case, a good place to start looking is files in the log directory (c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG of the server.
Another useful test is from DOS on the remote client:
telnet server-name 1433 (for SS2000)
telnet server-name 1415 (for SS2005)
If unsuccessful, it will come back with an error message. If the DOS screen goes black the test is positive.
I have noticed that to connect to SQL Server 2005 the service SQL Server Browser needs to be running. Not too sure (yet) what this service does.
I have tried to break things to see if I get your exact error message, but without success.
The thing that had me miffed for a long time in SS2005 is that if you do the install as a default instance then the connect string can be just the server-name. If you do it as a named instance then you must use server-name\instance-name.
June 15, 2007 at 2:31 am
Is remote connection enabled. I hope they are by default disabled in SQL express version.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
June 15, 2007 at 2:55 am
Got the problem solved.
Needed an alias to be created.
Thanks everyone for all your help.
June 15, 2007 at 2:59 am
Can you explain this 'alias' thing.
I tried to break Sugesh's suggestion, i.e. in Management Studio I right click on the instance then properties then connections then unclick 'Allow remote connections to this server' then restart the services (just to be sure). I can still connect from a remote computer.
June 15, 2007 at 3:34 am
I guess this refers to remote SERVERS connecting to this server (not remote clients connecting to this server).
All this connection stuff where you mix 2000 with 2005 on both the client and server side is very weird. I can mix and match and do connections in all 4 ways:
2000 client talks to 2005 server
2000 client talks to 2000 server
2005 client talks to 2005 server
2005 client talks to 2000 server
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply