BUG: Addition of Local Server Is Case SensitiveID: Q118809
|
When using SQL Administrator to add remote servers, the local server may be added as ID 1 instead of as the local server (ID 0).
When adding remote servers using SQL Administrator, ensure the case of the server name being added is the same as the added server.
Microsoft has confirmed this to be a problem in SQL Administrator version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
When adding remote servers, SQL Administrator checks to see if the server
being added has the same name as the server it is currently connected to.
If the names match, SQL Admin specifies that the server is local when
issuing the sp_addserver stored procedure. The check for name matching is
case sensitive, regardless of the case sensitivity of the server.
For example, if SQL Administrator is used to log in to a server specifying
the name "server1," the Manage.Remotes.AddRemoteServer dialog box is called
up, and a server name of SERVER1 is entered. The ID sysservers is entered
as a non-zero value. Specifying server1 as the remote name will cause the
server to be added as ID 0.
Additional query words: RPC remote procedure calls 7214 login
Keywords : kbtool SSrvSQL_Admin kbbug4.20 SSrvWinNT
Version : 4.2
Platform : WINDOWS
Issue type :
Last Reviewed: March 20, 1999