BUG: Incremental Article Additions to an Existing Merge Publication Do Not Work When You Use FTP (320600)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q320600
BUG #: 356693 (SHILOH_BUGS)
SYMPTOMS
If all the following conditions are true, the Merge Agent fails with an error message when it tries to apply snapshot files:
- Articles are being added incrementally to an existing merge publication.
- The merge publication has already been published and subscribed.
- The mechanism for the distribution of snapshot is configured to use FTP.
If the outputverboselevel option is set to 3, the following error messages are in the Merge Agent Log file:
UNC Path
If the default snapshot location is a UNC path, the following error messages are in the Merge Agent Log file:
[1/29/2002 6:57:23 PM]REPL42\RTM.pubs: exec sp_datatype_info 0, 3
The schema script '\\REPL42\D$\Program Files\Microsoft SQL Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.sch' could not be propagated to the subscriber.
Percent Complete: 0
The schema script '\\REPL42\D$\Program Files\Microsoft SQL Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.sch' could not be propagated to the subscriber.
Repl Agent Status: 6
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script '\\REPL42\D$\Program Files\Microsoft SQL Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.sch' could not be propagated to the subscriber.
Repl Agent Status: 3
Percent Complete: 0
Category:AGENT
Source: REPL43\SQL2K
Number: 0
Message: The process could not read file '\\REPL42\D$\Program Files\Microsoft SQL Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.sch' due to OS error 5.
Repl Agent Status: 3
Percent Complete: 0
Category:OS
Source:
Number: 5
Message: Access is denied.
If the default snapshot location is a Local Folder, the following error messages are in the Merge Agent Log file:
[10/23/01 4:20:20 PM]LCL2B17B.TestDb: exec sp_datatype_info 0, 3
The schema script 'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sch' could not be propagated to the subscriber.
Percent Complete: 0
The schema script 'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sch' could not be propagated to the subscriber.
Repl Agent Status: 6
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sch' could not be propagated to the subscriber.
Repl Agent Status: 3
Percent Complete: 0
Category:AGENT
Source: LCL2B22C
Number: 0
Message: The process could not read file 'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sch' due to OS error 3.
Repl Agent Status: 3
Percent Complete: 0
Category:OS
Source:
Number: 3
Message: The system cannot find the path specified.
WORKAROUND
Incremental article additions to a merge publication cannot be handled if you use FTP. Hence, no practical workaround exists other than performing a REINIT of the whole publication.
If you must make incremental article additions, then you must use the UNC mechanism to move the snapshot files instead of relying on FTP. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
320499 HOW TO: Manually Synchronize Replication Subscriptions by Using Backup or Restore
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Major | Last Reviewed: | 10/3/2003 |
|---|
| Keywords: | kbbug kbpending KB320600 |
|---|
|