This article describes the following about this hotfix release:

•	The issues that are fixed by the hotfix package
•	The prerequisites for applying the hotfix package
•	Whether you must restart the computer after you apply the hotfix package
•	Whether the hotfix package replaces any other hotfix package
•	Whether you must make any registry changes after you apply the hotfix package
•	The files that are contained in the hotfix package

Back to the top

Consider the following scenario. In Microsoft SQL Server 2005, you create an immediate updating pull subscription for a transactional replication. Then, you query a table that is published in the transactional replication. In this scenario, you may receive inconsistent results. For example, data that was deleted in a previous transaction may be returned.

Additionally, transactional replication may fail, and you may receive error messages that resemble the following:

Back to the top

Whether this issue occurs depends on the timing of the agents that you are running. This issue occurs in SQL Server 2005 because of changes that are have been made in the loopback detection. These changes enable republishing of immediate updating replication scenarios. The changes propagate commands that are initiated from a Subscriber back to that Subscriber. The changes rely on Subscriber-side custom stored procedures to filter out duplicates.

This issue occurs in the following scenario:

•	You insert a row at a Subscriber.
•	You run the Logreader.exe file at the publisher. Then, the Publisher runs the INSERT command.
•	You delete this row at the Subscriber.
•	You run the Distribution Agent from the Publisher to the Subscriber.

The Distribution Agent will deliver the row that you inserted back to the Subscriber. This behavior occurs although the insertion was initiated by the Subscriber and although the row no longer exists on the Subscriber. When you run the Logreader.exe file later, the Distribution Agent delivers the DELETE command to the Subscriber. At this point, the Publisher and the Subscriber become synchronized again.

Back to the top

Service pack information

To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Microsoft SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: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

To apply this hotfix, you must have SQL Server 2005 Service Pack 1 (SP1) installed. For more information about SQL Server 2005 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Registry information

You do not have to change the registry after you apply this hotfix.

File information

This hotfix contains only those files that are required to correct the issues that are listed in this article. 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.

Microsoft SQL Server 2005, 32-bit version

File name	File version	File size	Date	Time
Logread.exe	2005.90.2198.0	398,112	12-Oct-2006	23:32
Microsoft.analysisservices.adomdclient.dll	9.0.2198.0	543,520	12-Oct-2006	23:32
Microsoft.analysisservices.deploymentengine.dll	9.0.2198.0	138,016	12-Oct-2006	23:32
Microsoft.analysisservices.dll	9.0.2198.0	1,215,264	12-Oct-2006	23:32
Microsoft.sqlserver.mgdsqldumper.dll	2005.90.2198.0	75,552	12-Oct-2006	23:32
Microsoft.sqlserver.sqlenum.dll	9.0.2198.0	908,064	12-Oct-2006	23:32
Msasxpress.dll	9.0.2198.0	22,304	12-Oct-2006	23:32
Msgprox.dll	2005.90.2198.0	197,920	12-Oct-2006	23:32
Msmdlocal.dll	9.0.2198.0	15,608,096	12-Oct-2006	23:32
Msmdredir.dll	9.0.2198.0	3,990,304	12-Oct-2006	23:32
Replprov.dll	2005.90.2198.0	547,616	12-Oct-2006	23:32
Replrec.dll	2005.90.2198.0	782,112	12-Oct-2006	23:32
Sqlaccess.dll	2005.90.2198.0	347,936	12-Oct-2006	23:33
Sqlagent90.exe	2005.90.2198.0	318,752	12-Oct-2006	23:33
Sqlservr.exe	2005.90.2198.0	28,963,160	12-Oct-2006	23:33
Xpstar90.dll	2005.90.2198.0	292,640	12-Oct-2006	23:33
Xpstar90.rll	2005.90.2198.0	152,864	12-Oct-2006	23:32

Microsoft SQL Server 2005, x64-based version

File name	File version	File size	Date	Time	Platform
Logread.exe	2005.90.2198.0	522,528	15-Oct-2006	13:16	x64
Microsoft.analysisservices.adomdclient.dll	9.0.2198.0	543,520	12-Oct-2006	23:32	x86
Microsoft.analysisservices.adomdclient.dll	9.0.2198.0	543,520	15-Oct-2006	13:16	x86
Microsoft.analysisservices.deploymentengine.dll	9.0.2198.0	138,016	12-Oct-2006	23:32	x86
Microsoft.analysisservices.dll	9.0.2198.0	1,215,264	12-Oct-2006	23:32	x86
Microsoft.sqlserver.mgdsqldumper.dll	2005.90.2198.0	75,552	12-Oct-2006	23:32	x86
Microsoft.sqlserver.mgdsqldumper.dll	2005.90.2198.0	91,424	15-Oct-2006	13:16	x64
Microsoft.sqlserver.sqlenum.dll	9.0.2198.0	875,296	15-Oct-2006	13:16	x86
Msasxpress.dll	9.0.2198.0	22,304	12-Oct-2006	23:32	x86
Msasxpress.dll	9.0.2198.0	27,424	15-Oct-2006	13:16	x64
Msgprox.dll	2005.90.2198.0	259,360	15-Oct-2006	13:16	x64
Msmdlocal.dll	9.0.2198.0	15,608,096	12-Oct-2006	23:32	x86
Msmdredir.dll	9.0.2198.0	3,990,304	12-Oct-2006	23:32	x86
Replprov.dll	2005.90.2198.0	745,248	15-Oct-2006	13:16	x64
Replrec.dll	2005.90.2198.0	1,008,416	15-Oct-2006	13:16	x64
Sqlaccess.dll	2005.90.2198.0	355,104	15-Oct-2006	13:16	x86
Sqlagent90.exe	2005.90.2198.0	389,920	15-Oct-2006	13:16	x64
Sqlservr.exe	2005.90.2198.0	39,344,928	15-Oct-2006	13:17	x64
Xpstar90.dll	2005.90.2198.0	540,960	15-Oct-2006	13:17	x64
Xpstar90.rll	2005.90.2198.0	153,376	15-Oct-2006	13:16	x64

Microsoft SQL Server 2005, Itanium architecture version

File name	File version	File size	Date	Time	Platform
Logread.exe	2005.90.2198.0	1,095,456	13-Oct-2006	09:06	IA-64
Microsoft.analysisservices.adomdclient.dll	9.0.2198.0	543,520	12-Oct-2006	23:32	x86
Microsoft.analysisservices.adomdclient.dll	9.0.2198.0	543,520	13-Oct-2006	09:06	x86
Microsoft.analysisservices.deploymentengine.dll	9.0.2198.0	138,016	12-Oct-2006	23:32	x86
Microsoft.analysisservices.dll	9.0.2198.0	1,215,264	12-Oct-2006	23:32	x86
Microsoft.sqlserver.mgdsqldumper.dll	2005.90.2198.0	75,552	12-Oct-2006	23:32	x86
Microsoft.sqlserver.mgdsqldumper.dll	2005.90.2198.0	163,104	13-Oct-2006	09:06	IA-64
Microsoft.sqlserver.sqlenum.dll	9.0.2198.0	875,296	13-Oct-2006	09:06	x86
Msasxpress.dll	9.0.2198.0	22,304	12-Oct-2006	23:32	x86
Msasxpress.dll	9.0.2198.0	55,072	13-Oct-2006	09:06	IA-64
Msgprox.dll	2005.90.2198.0	542,496	13-Oct-2006	09:07	IA-64
Msmdlocal.dll	9.0.2198.0	48,590,112	13-Oct-2006	09:07	IA-64
Msmdredir.dll	9.0.2198.0	6,244,640	13-Oct-2006	09:07	IA-64
Replprov.dll	2005.90.2198.0	1,617,184	13-Oct-2006	09:07	IA-64
Replrec.dll	2005.90.2198.0	2,141,472	13-Oct-2006	09:07	IA-64
Sqlaccess.dll	2005.90.2198.0	349,472	13-Oct-2006	09:07	x86
Sqlagent90.exe	2005.90.2198.0	1,141,024	13-Oct-2006	09:07	IA-64
Sqlservr.exe	2005.90.2198.0	72,226,592	13-Oct-2006	09:07	IA-64
Xpstar90.dll	2005.90.2198.0	951,072	13-Oct-2006	09:01	IA-64
Xpstar90.rll	2005.90.2198.0	152,352	13-Oct-2006	09:07	IA-64

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2005 Service Pack 2.

Back to the top

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

Back to the top