Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bigrack
Starting Member
9 Posts |
 Posted - 2007-02-26 : 14:40:23
|
| I've had a VB 6 / SQL Server 2000 app running in a network enviroment for a couple of years now at a client of mine. Recently, he upgraded to the latest version of Quickbooks which installed SQL Server 2005 on the server. Now there is SQL Server 2000 and 2005 residing on the same server. My VB app still runs on the server but will not run on other machines. I can ping the server from the other machines. Has SQL 2005 taken over the port I was using or maybe has new security features that won't let me access SQL 2000 using my current connection string? Here is my current connection string: mstrConnStr = "Provider=SQLOLEDB.1;Persist Security Info=True;User ID=" & strServerLogin & ";Password=" & strServerPW & ";Initial Catalog=" & strDBName & ";Data Source=" & strServer.Any help will be greatly appreciated.Keith |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-02-26 : 15:27:50
|
| Well he could have switched ports on you. Check out Server Network Utility from the actual database server to determine what port is in use. If it's not the default port, then you can reference the server via ServerName\InstanceName,PortNumber (for named instance) or ServerName,PortNumber (for default instance).Tara Kizer |
 |
|
|
bigrack
Starting Member
9 Posts |
Posted - 2007-02-26 : 16:17:33
|
| Interesting. I tried to go to Server Network Utility (for SQL 2000) and it gave me an error that the module doesn't exist. I can open Enterprise Manager and other utilities but not that one. Is there another way to find out which port it's using? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-02-26 : 16:46:48
|
| Well you can view the information in the SQL Server Error Log, but it can be hard to find if you aren't familiar with it. You can also check the registry, via regedit. For the default instance:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\TcpFor a named instance:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceNameGoesHere\MSSQLServer\SuperSocketNetLib\TcpTara Kizer |
|
|
|
bigrack
Starting Member
9 Posts |
Posted - 2007-02-27 : 08:55:36
|
| I'm waiting to hear from the client but this looks like it's going to work. Thanks for the help, oh Goddess.Keith |
|
|
|
|
|
|
Lost Connection to SQL 2000 after SQL 2005 Install