PRB: The Merge Agent Stops Responding and You Receive the Error "The Schema Script 'File Location Pointed to a DRI Script File' Could Not Be Propagated to the Subscriber" (318898)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions) SP1
- Microsoft SQL Server 2000 (all editions) SP2
This article was previously published under Q318898 SYMPTOMS
If you set up Merge Replication from a Microsoft SQL Server 2000 Publisher to a Microsoft SQL Server 7.0 Subscriber, by default, the replication setup process enables Include declared referential integrity (DRI). If cascading referential integrity is defined on the publishing tables, the Merge Agent does not deliver the snapshot, and you receive the following error message:
The schema script "file location pointed to a DRI script file" could not be propagated to the subscriber.
CAUSE
This issue occurs because the SQL Server 7.0 Subscriber does not recognize the cascading referential integrity feature in SQL Server 2000.
WORKAROUND
To work around this issue, modify the DRI script in the Snapshot folder before the Merge Agent delivers the snapshot to the Subscriber. You can locate the DRI script based on the error message. Example:
Message: The schema script The schema script
'\\CHANGQING\C$\Program Files\Microsoft SQL Server\MSSQL$INT\ReplData\unc\CHANGQING$INT_ReproDB_ReproDB\20020221113900\T2_13.dri' could not be propagated to the subscriber.
Remove "ON DELETE CASCADE ON UPDATE CASCADE" from the script in the path that the error message indicates. You must modify all of the DRI scripts that have cascading referential integrity constraints, and then start the Merge Agent to deliver the snapshot.
REFERENCES
For more information, see the "Replication Between Different Versions of SQL Server" topic in SQL Server Books Online.
| Modification Type: | Major | Last Reviewed: | 10/3/2003 |
|---|
| Keywords: | kbprb KB318898 kbAudDeveloper |
|---|
|