FIX: Error message when you create a merge replication for tables that have computed columns or columns of the timestamp data type in SQL Server 2000 Service Pack 4: "The process could not log conflict information"
Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release.
If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.
In Microsoft SQL Server 2000 Service Pack 4 (SP4), you create a merge replication for tables that have computed columns or columns of the timestamp data type. When you try to synchronize the subscriptions, you receive the following error message during the snapshot process in the Replication Merge Agent:
The process could not log conflict information. (Source: Merge Replication Provider (Agent); Error number: -2147200992) --------------------------------------------------------------------------------------------------------------- Error converting data type varchar to datetime.
If you ignore the error message, and you then continue the synchronization, the Replication Merge Agent soon fails when the Replication Merge Agent connects to the subscriber to enumerate changes. The following error message is logged in the Mergelog.txt file:
Processing article 'TableName' The process could not enumerate changes at the 'Subscriber'. Percent Complete: 0 The process could not enumerate changes at the 'Subscriber'. Percent Complete: 0 Category:NULL Source: Merge Replication Provider Number: -2147200999 Message: The process could not enumerate changes at the 'Subscriber'. Percent Complete: 0 Category: SQLSERVER Source: Servername Number: 0 Message: Restricted data type attribute violation Disconnecting from Subscriber 'Servername'
Note The "Restricted data type attribute violation" error message is an ODBC error message.
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.
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 Customer Service and Support to obtain the hotfix.
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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
How to obtain the latest SQL Server 2000 service pack
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.