Select the product you need help with
FIX: "The merge process could not access row data" error occurs when the Merge Agent stops, and rows are set to 4 in the genstatus column in the msmerge_genhistory system tableArticle ID: 2478514 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 or SQL 2008 R2 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 2008 or SQL 2008 R2 fix release. SYMPTOMSYou create a merge replication that uses web synchronization in Microsoft SQL Server 2008 or SQL Server 2008 R2. You notice the Merge Agent does not apply the download changes or the upload changes to the database. When this problem occurs, an error message that resembles the following pattern is logged in the Merge Agent verbose log file: OLE DB Subscriber 'subscriber': {call sp_MSgetonerow (?, ?, ?) } OLE DB Subscriber 'subscriber': {call sp_MSenumcolumns (?,?)} The merge process could not access row data at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to write to, or run the SQL Profiler utility to identify the source of the failure. RESOLUTIONThe fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: 2498535 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2498535/
)
Cumulative update package 3 for SQL Server 2008 Service Pack 2956909
(http://support.microsoft.com/kb/956909)
The SQL Server 2008 builds that were released after SQL Server 2008 was releasedSQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2544793 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2544793/
)
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:2507770 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2507770/
)
Cumulative Update package 7 for SQL Server 2008 R2 981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedSTATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about web synchronization for merge replication, visit the following Microsoft Developer Network (MSDN) website: Web Synchronization for Merge Replication For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
(http://msdn.microsoft.com/en-us/library/ms151763(v=SQL.100).aspx)
2498535
(http://support.microsoft.com/kb/2498535/
)
Cumulative update package 3 for SQL Server 2008 Service Pack 2REFERENCESFor more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: 956909
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released935897
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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems822499
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesProperties | Article Translations |
Back to the top
