This article has been archived. It is offered "as is" and will no longer be updated.
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.
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
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
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:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
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.
You do not have to restart the computer after you apply this hotfix.
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.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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
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