Article ID: 934188
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard 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 #: 50000952 (SQL Hotfix)
Bug #: 50000686 (SQL Hotfix)
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
In Microsoft SQL Server 2005, a Distribution Agent may enter a state in which the Distribution Agent does not deliver commands to the Subscriber. This problem may occur even if the Distribution Agent is running. When the Distribution Agent enters this state, the Distribution Agent does not recover by itself. You must restart the Distribution Agent. Alternatively, you must terminate all the processes that are based on the session IDs (SPIDs) for the Distribution Agent.
This problem occurs if you configure the Distribution Agent to use multiple subscription streams. You do this by setting the SubscriptionStreams parameter to a value that is larger than 1.
When this problem occurs, all the SPIDs for the Distribution Agent may continuously run a query that resembles the following on the Subscriber.
select spid, blocked, lastwaittype from master..sysprocesses where '~280~~1336~~1853~~2702~' like '%~' + cast (spid as nvarchar)+ '~%' and '~280~~1336~~1853~~2702~' like '%~' + cast (blocked as nvarchar)+ '~%'
CAUSE
This problem occurs because of a problem in the thread-scheduling logic in the Distribution Agent. If one of the threads times out when the thread is applying the replicated commands, all the other threads also stop applying the replicated commands.
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 2
For more information about how to obtain SQL Server 2005 Service Pack 2, 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.maintenanceplantasks.dll | 9.0.3154.0 | 296,304 | 10-Mar-2007 | 05:49 | x86 |
| Mssqlsystemresource.ldf | Not Applicable | 524,288 | 10-Mar-2007 | 02:59 | Not Applicable |
| Mssqlsystemresource.mdf | Not Applicable | 40,173,568 | 10-Mar-2007 | 02:59 | Not Applicable |
| Rdistcom.dll | 2005.90.3154.0 | 644,464 | 10-Mar-2007 | 05:49 | x86 |
| Msmdlocal.dll | 9.0.3154.0 | 15,930,224 | 10-Mar-2007 | 05:49 | x86 |
| Sqlaccess.dll | 2005.90.3154.0 | 350,576 | 10-Mar-2007 | 05:49 | x86 |
| Sqlservr.exe | 2005.90.3154.0 | 29,191,536 | 10-Mar-2007 | 05:49 | x86 |
SQL Server 2005 x64-based version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.maintenanceplantasks.dll | 9.0.3154.0 | 296,304 | 10-Mar-2007 | 05:49 | x86 |
| Mssqlsystemresource.ldf | Not Applicable | 524,288 | 10-Mar-2007 | 02:59 | Not Applicable |
| Mssqlsystemresource.mdf | Not Applicable | 40,173,568 | 10-Mar-2007 | 02:59 | Not Applicable |
| Rdistcom.dll | 2005.90.3154.0 | 828,272 | 10-Mar-2007 | 11:12 | x64 |
| Msmdlocal.dll | 9.0.3154.0 | 15,930,224 | 10-Mar-2007 | 05:49 | x86 |
| Sqlaccess.dll | 2005.90.3154.0 | 357,744 | 10-Mar-2007 | 11:12 | x86 |
| Sqlservr.exe | 2005.90.3154.0 | 38,655,344 | 10-Mar-2007 | 11:12 | x64 |
WORKAROUND
To work around this problem, use one of the following techniques:
- Restart the Distribution Agent job.
- Set the value of the SubscriptionStreams parameter to 1. For more information about the SubscriptionStreams parameter, visit the following Microsoft Developer Network (MSDN) Web site:
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
The SubscriptionStreams parameter lets the Distribution Agent use multiple threads. Therefore, the Distribution Agent can apply batches of changes in parallel to a Subscriber. Additionally, many of the transactional characteristics that are present when the Distribution Agent uses a single thread are maintained.
To examine the Distribution Agent sessions that are running, run the following statement in SQL Server Management Studio.
select a.spid, c.text, a.blocked, a.lastwaittype,a.login_time, a.last_batch, a.hostname, a.program_name from sys.sysprocesses a, sys.dm_exec_requests b cross apply sys.dm_exec_sql_text(b.sql_handle) c where a.spid = b.session_id and a.program_name like '%<NAME OF YOUR DISTRIBUTION AGENT JOB>%'
This hotfix is also included in the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available
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
Additional query words: transactional replication distribution agent hang unresponsive high cpu latency
Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver KB934188
