June 23, 2004 at 10:49 am
We are in the process of upgrading for SQL 7 to SQL 2000. On the same box, we have installed SQL 2000 as a named instance. The named instance is "SQL2000".
I can register the new server in EM with no problem. I type the server name the the instance name, select the login mode an enter the password and it works fine. I have users that can use EM to see the SQL 7, but can not register the named instance. Additionally, I am on a LAN while my users are on a WAN. Does that make any difference?
Thanks!
Jeff
June 23, 2004 at 11:38 am
Hi,
try to check client tools of your users. Only EM from sql 2000 client tools can register named instance od SQL server.
vbenus
June 23, 2004 at 11:50 am
Sorry, but how do I determine they are running client tools from SQL 2000?
June 24, 2004 at 1:45 am
Hi,
1. You should see Microsoft SQL SERVER 7.0 in Start-Programs
2. VERSION 7 in registry
3. open EM, click Microsoft SQL Server, right click in the right part of the window, open "About SQL Server Enterprise Manager". If you will not see this menu you have probably version 7.
4. just install client tools from sql 2000
vbenus
June 24, 2004 at 1:53 am
You may also want to check that your WAN users are connecting to SQL Server using TCP/IP protocol.
In SQL Server Client Network Utility, make sure TCP/IP is listed first in the "Enabled Protocols by order".
You may also need to check that TCP/IP is enabled on the SQL Server, by (in EM) right clicking the server and choosing properties then going into Network Configuration. I've seen a number of installs start without network configurations(MSDE defaults to this).
Julian Kuiters
juliankuiters.id.au
June 24, 2004 at 3:13 am
If your clients are on a WAN, ensure that the port used by the named instance is not blocked by firewalls. Firewall blocking may not inhibit registration, but it would affect access.
The previous post about some clients not being able to register a named instance is partly correct. There are many non-Microsoft clients that can register and access named instances, but not all clients can do this.
One way to troubleshoot the connection problems would be to get the client software installed on the LAN. If it cannot connect on the LAN, it may be a client problem. If it can on the LAN but not the WAN, it is more likely to be a network configuration issue.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
June 24, 2004 at 9:30 am
One thing you might wonder - you can use the EM from SQL 2000 to view SQL 7 servers but you cannot use the SQL 7 EM to view SQL 2000 servers.
We have a few SQL 7 and SQL 2000 servers here, and using the 2000 EM, you can see both sets very easily.
One thing I did notice is that one of our applications kept rolling back the SQL DLL files on the client side. So if you have the SQL 2000 EM with the SQL 7 DLL loaded, it won't work. If you happen to be in this case, just copy the SQL 2000 DLL back into the system32 directory and mark it as read only.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply