Article ID: 919929
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Bug #: 435062 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by the 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
Consider the following scenario. You have a merge replication subscription in Microsoft SQL Server 2005. The Replication Merge Agent runs to synchronize the merge replication subscription. In this scenario, the merge replication subscription is incorrectly expired. Additionally, you may receive the following error message:
This problem occurs if the following conditions are true:
- A Subscriber subscribes to two publications in the same Subscriber database.
- No published merge articles are common to both publications.
RESOLUTION
Hotfix information
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
- SQL Server 2005 Service Pack 1 (SP1)
For more information, click the following article number to view the article in the Microsoft Knowledge Base:913089 How to obtain the latest service pack for SQL Server 2005
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 item in Control Panel.
SQL Server 2005 32-bit version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2164.0 | 75,552 | 14-Jun-2006 | 20:29 | x86 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2164.0 | 908,064 | 14-Jun-2006 | 20:32 | x86 |
| Msgprox.dll | 2005.90.2164.0 | 197,920 | 14-Jun-2006 | 20:29 | x86 |
| Msmdlocal.dll | 9.0.2164.0 | 15,661,856 | 14-Jun-2006 | 20:33 | x86 |
| Replprov.dll | 2005.90.2164.0 | 547,616 | 14-Jun-2006 | 20:31 | x86 |
| Replrec.dll | 2005.90.2164.0 | 782,112 | 14-Jun-2006 | 20:32 | x86 |
| Sqlaccess.dll | 2005.90.2164.0 | 347,936 | 14-Jun-2006 | 20:31 | x86 |
| Sqlservr.exe | 2005.90.2164.0 | 28,950,872 | 14-Jun-2006 | 20:33 | x86 |
SQL Server 2005 x64-based version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2164.0 | 75,552 | 14-Jun-2006 | 20:29 | x86 |
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2164.0 | 91,424 | 14-Jun-2006 | 21:10 | x64 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2164.0 | 875,296 | 14-Jun-2006 | 21:12 | x86 |
| Msgprox.dll | 2005.90.2164.0 | 259,360 | 14-Jun-2006 | 21:10 | x64 |
| Msmdlocal.dll | 9.0.2164.0 | 15,661,856 | 14-Jun-2006 | 20:33 | x86 |
| Replprov.dll | 2005.90.2164.0 | 745,248 | 14-Jun-2006 | 21:12 | x64 |
| Replrec.dll | 2005.90.2164.0 | 1,008,416 | 14-Jun-2006 | 21:12 | x64 |
| Sqlaccess.dll | 2005.90.2164.0 | 355,104 | 14-Jun-2006 | 21:11 | x86 |
| Sqlservr.exe | 2005.90.2164.0 | 39,251,232 | 14-Jun-2006 | 21:13 | x64 |
SQL Server 2005 Itanium architecture version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2164.0 | 163,104 | 14-Jun-2006 | 20:29 | IA-64 |
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2164.0 | 75,552 | 14-Jun-2006 | 20:29 | x86 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2164.0 | 875,296 | 14-Jun-2006 | 20:29 | x86 |
| Msgprox.dll | 2005.90.2164.0 | 542,496 | 14-Jun-2006 | 20:28 | IA-64 |
| Msmdlocal.dll | 9.0.2164.0 | 48,733,984 | 14-Jun-2006 | 20:30 | IA-64 |
| Replprov.dll | 2005.90.2164.0 | 1,617,184 | 14-Jun-2006 | 20:29 | IA-64 |
| Replrec.dll | 2005.90.2164.0 | 2,141,472 | 14-Jun-2006 | 20:29 | IA-64 |
| Sqlaccess.dll | 2005.90.2164.0 | 349,472 | 14-Jun-2006 | 20:28 | x86 |
| Sqlservr.exe | 2005.90.2164.0 | 72,208,672 | 14-Jun-2006 | 20:30 | IA-64 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
This hotfix does not change the state of a subscription that is incorrectly expired in the scenario that is mentioned in the "Symptoms" section. After you apply this hotfix, a subscription that is incorrectly expired remains expired and must be reinitialized.
If the expired subscription has changes that must be uploaded to the Publisher, the Replication Merge Agent overwrites the changes when the Replication Merge Agent reinitializes the subscription. Therefore, the changes are lost. To avoid this behavior, you must manually upload the changes to the Publisher before the Replication Merge Agent reinitializes the subscription.
For more information about how to upload changes to the Publisher, visit the following Microsoft Developer Network (MSDN) Web site:
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 software update terminology, 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
Keywords: kbtshoot kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005repl KB919929
