Microsoft KB Archive/887700

= FIX: Server Network Utility may display incorrect protocol properties in SQL Server 2000 =

Article ID: 887700

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Desktop Engine (Windows)
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Workgroup Edition

-



Bug #: 470826 (SQL Server 8.0)



''Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.''



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart the computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
When you have multiple named instances of Microsoft SQL Server 2000 installed on a server, Server Network Utility may display incorrect protocol properties. When you click Properties in Server Network Utility, the protocol properties that are displayed for the default selection in the Instance(s) on this server list may be the protocol properties of another named instance.

Note This problem only occurs when there is no default instance.

For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a



CAUSE
This problem occurs when you have multiple named instances installed on a server and when the first installed instance is not the first alphabetically named instance.

For example, you first install an instance that is named ZInstance and then install an instance that is named AInstance. In this example, the protocol properties that are displayed may be the protocol properties of the ZInstance named instance.

Note You can determine the installation order by looking at the InstalledInstances registry entry that is located under the following registry key:



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
 Microsoft SQL Server 2000 Service Pack 3 (SP3)

For more information about how to obtain SQL Server 2000 SP3, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

 Microsoft SQL Server 2000 hotfix build 2000.80.1007

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

842960 Description of the 32-bit SQL Server 7.0 and SQL Server 2000 hotfix installer

872912 Description of the 64-bit SQL Server 2000 hotfix installer



Note This hotfix is a SQL Server 2000 post-SP3 hotfix. This hotfix cannot be applied on SQL Server 2000 Service Pack 4.

Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000 32-bit versions
  Date         Time   Version            Size    File name --  20-Apr-2005  07:11  2000.80.1021.0    664,128  Autoplt.dll 20-Apr-2005 07:11  2000.80.1021.0     78,400  Console.exe 20-Apr-2005 07:11  2000.80.1021.0    332,352  Ctasksui.dll 20-Apr-2005 07:11  2000.80.1021.0    315,968  Custtask.dll 20-Apr-2005 07:11  2000.80.1021.0     33,340  Dbmslpcn.dll 15-Apr-2005 01:17                    786,432  Distmdl.ldf 15-Apr-2005 01:17                  2,359,296  Distmdl.mdf 15-Apr-2005 01:17                        180  Drop_repl_hotfix.sql 20-Apr-2005 07:11  2000.80.1021.0  1,905,216  Dtspkg.dll 20-Apr-2005 07:11  2000.80.1021.0    528,960  Dtspump.dll 20-Apr-2005 07:11  2000.80.1021.0  1,557,052  Dtsui.dll 20-Apr-2005 07:11  2000.80.1021.0    639,552  Dtswiz.dll 20-Apr-2005 07:11  2000.80.1021.0    102,992  Impprov.dll 15-Apr-2005 01:17                    747,927  Instdist.sql 15-Apr-2005 01:17                      1,581  Inst_repl_hotfix.sql 20-Apr-2005 07:11  2000.80.1021.0    352,828  Isqlw.exe 20-Apr-2005 07:11  2000.80.1021.0     82,492  Itwiz.exe 20-Apr-2005 07:11  2000.80.1021.0     90,692  Msgprox.dll 15-Apr-2005 00:58  8.11.41022.0      226,304  Mssdi98.dll 20-Apr-2005 07:11  2000.80.1021.0     62,024  Odsole70.dll 20-Apr-2005 07:11  2000.80.1021.0     25,144  Opends60.dll 20-Apr-2005 07:11  2000.80.1021.0     57,904  Osql.exe 20-Apr-2005 07:11  2000.80.1021.0    279,104  Pfutil80.dll 15-Apr-2005 01:13                    551,012  Procsyst.sql 15-Apr-2005 01:17                     12,305  Qfe469315.sql 15-Apr-2005 01:17                     19,195  Qfe469571.sql 15-Apr-2005 01:17                      5,157  Qfe472197.sql 20-Apr-2005 07:11  2000.80.1021.0    143,940  Qrdrsvc.exe 19-Apr-2005 23:10                  1,136,160  Replmerg.sql 20-Apr-2005 07:11  2000.80.1021.0    221,768  Replprov.dll 20-Apr-2005 07:11  2000.80.1021.0    307,784  Replrec.dll 19-Apr-2005 23:12  2000.80.1021.0    159,813  Replres.rll 15-Apr-2005 01:17                  1,088,240  Replsys.sql 15-Apr-2005 01:17                    986,746  Repltran.sql 15-Apr-2005 01:17                         55  Repl_uninstall.sql 20-Apr-2005 07:11  2000.80.1021.0    287,304  Rinitcom.dll 20-Apr-2005 07:11  2000.80.1021.0     78,416  Sdiclnt.dll 20-Apr-2005 07:11  2000.80.1021.0    823,872  Semexec.dll 20-Apr-2005 07:11  2000.80.1021.0     66,112  Semmap.dll 20-Apr-2005 07:11  2000.80.1021.0     57,916  Semnt.dll 20-Apr-2005 07:11  2000.80.1021.0    492,096  Semobj.dll 19-Apr-2005 23:46  2000.80.1021.0    172,032  Semobj.rll 20-Apr-2005 07:11  2000.80.1021.0     53,832  Snapshot.exe 15-Apr-2005 01:13                    125,540  Sp3_serv_uni.sql 20-Apr-2005 07:10  2000.80.1021.0     28,672  Sqlagent.dll 20-Apr-2005 07:11  2000.80.1021.0    311,872  Sqlagent.exe 20-Apr-2005 07:10  2000.80.1021.0    168,001  Sqlakw32.dll 20-Apr-2005 07:11  2000.80.1021.0     33,344  Sqlctr80.dll 20-Apr-2005 07:11  2000.80.1021.0  4,215,360  Sqldmo.dll 20-Apr-2005 07:11                     25,172  Sqldumper.exe 19-Apr-2005 23:09  2000.80.1021.0     28,672  Sqlevn70.rll 20-Apr-2005 07:11  2000.80.1021.0    156,224  Sqlmaint.exe 20-Apr-2005 07:11  2000.80.1021.0    180,792  Sqlmap70.dll 20-Apr-2005 07:11  2000.80.1021.0    188,992  Sqlmmc.dll 19-Apr-2005 23:24  2000.80.1021.0    479,232  Sqlmmc.rll 20-Apr-2005 07:11  2000.80.1021.0    401,984  Sqlqry.dll 20-Apr-2005 07:11  2000.80.1021.0     57,920  Sqlrepss.dll 20-Apr-2005 07:11  2000.80.1021.0  7,721,041  Sqlservr.exe 20-Apr-2005 07:11  2000.80.1021.0    590,396  Sqlsort.dll 20-Apr-2005 07:11  2000.80.1021.0     45,644  Sqlvdi.dll 20-Apr-2005 07:11  2000.80.1021.0    106,588  Sqsrvres.dll 20-Apr-2005 07:11  2000.80.1021.0     33,340  Ssmsgnet.dll 20-Apr-2005 07:11  2000.80.1021.0     33,340  Ssmslpcn.dll 20-Apr-2005 07:11  2000.80.1021.0     33,340  Ssmsqlgc.dll 20-Apr-2005 07:11  2000.80.1021.0     82,492  Ssnetlib.dll 20-Apr-2005 07:11  2000.80.1021.0     25,148  Ssnmpn70.dll 20-Apr-2005 07:11  2000.80.1021.0    123,456  Stardds.dll 20-Apr-2005 07:11  2000.80.1021.0    158,268  Svrnetcn.dll 20-Apr-2005 07:11  2000.80.1021.0     76,416  Svrnetcn.exe 20-Apr-2005 07:11  2000.80.1021.0     49,228  Ums.dll 20-Apr-2005 07:11  2000.80.1021.0     74,304  Xplog70.dll 20-Apr-2005 07:11  2000.80.1021.0     98,872  Xpweb70.dll

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.



WORKAROUND
To work around this problem, select any other named instance in the Instance(s) on this server list, and then select the named instance that you want to display. When you do this, the named instance information is updated, and the correct protocol properties are displayed.

For example, if the AInstance instance is the default selection in the Instance(s) on this server list when you open Server Network Utility, select another named instance in the Instance(s) on this server list. Then, select the AInstance instance.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about the terminology that is used when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: SQL2000

Keywords: kbfix kbbug kbpubtypekc kbhotfixserver kbqfe KB887700

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.