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.
On This Page
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
When the Log Reader Agent runs for a transactional publication in Microsoft SQL Server 2005, an error message that resembles the following is logged in the job history of the Log Reader Agent:
2007-01-03 00:17:41.891 Status: 0, code: 18836, text: 'Invalid Text Info
Block for UpdateText: m_pHead->GetType() : 1, m_TextDataType : 0, m_TextOpType :
3, ti: {RowsetId 72057594093830144, {TextTimeStamp 605721131745280, {RowId
{PageId 611808, FileId 7}, SlotId 12}}, coloffset -1, textInfoFlags 0x4,
textSize 172, offset 20, oldSize 18, newSize 0}.'.
2007-01-03 00:17:41.891 Status: 0, code: 18805, text: 'Logreader failed to
construct replicated command from LSN {00023b85:0001a2f1:0061}.'.
. 2007-01-03 00:17:41.891 Status: 0, code: 22037, text: 'The process could not
execute 'sp_replcmds' on 'CMATHEWS11'.'.
In Replication Monitor, you can see this error message in the agent history of the Log Reader Agent.
This problem occurs if the following conditions are true:
•
You publish a table in transactional replication.
•
The table contains a column that has the text data type.
•
You update the column by using the TEXTPTR function together with the UPDATETEXT statement.
When this problem occurs, the Distribution Agent stops distributing any changes from the publication to the subscriptions. The Distribution Agent stops distributing any changes until the transactional publication is reinitialized.
To resolve this problem, use one of the following methods.
Note Method 1 requires that you have SQL Server 2005 Service Pack 2 installed. Method 2 requires that you have SQL Server 2005 Service Pack 1 installed.
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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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 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 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. To create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" section and the online request forms display 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.
Prerequisites
•
SQL Server 2005 Service Pack 1
For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
913089 (http://support.microsoft.com/kb/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.
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.
To work around this problem, do not use the UPDATETEXT statement to update a column that has the text data type if the column is in an article in a merge replication.
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 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
Contact Microsoft Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.
Back to the top
