FIX: You receive error 18815 when the Log Reader Agent runs for a transactional publication in SQL Server 2005
Bug: #50000909 (SQL Hotfix) Bug #: 50001100 (SQL Hotfix) NoticeMicrosoft 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 PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSWhen the Log Reader Agent runs for a transactional publication in SQL Server 2005, you receive error 18815. This issue occurs if the following conditions are true:
RESOLUTIONUpdate informationThis hotfix is included in the cumulative hotfix package (build 3175) for SQL Server 2005 Service Pack 2 (SP2). To resolve the problem that is described in this article, install SQL Server 2005 SP2. Then, install the cumulative hotfix package (build 3175) for SQL Server 2005 SP2. 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 (http://support.microsoft.com/kb/913089/)
How to obtain the latest service pack for SQL Server 2005
For more information about how to obtain the cumulative update package (build 3175) for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305 (http://support.microsoft.com/kb/936305/)
Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available
Hotfix informationA 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: http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451) 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: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) 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.PrerequisitesYou must have SQL Server 2005 Service Pack 1 installed to apply this hotfix. 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 informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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
SQL Server 2005 x64-based version
WORKAROUNDTo work around this issue, change the DELETE command type that is configured for the article from XCALL to CALL. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONWhen an article is configured to use the CALL command syntax for DELETE commands, only the primary key of the row that you want to delete is passed to the delete procedure. When an article is configured to use the XCALL command syntax for DELETE commands, the original values for all the columns that are defined in the article are passed to the delete procedure. For more information about the different syntax options that each Data Manipulation Language (DML) command type supports, see the "Specifying How Changes Are Propagated for Transactional Articles" topic in SQL Server 2005 Books Online. 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
APPLIES TO
| Article Translations
|
Back to the top
