locked
The schema script 'Course_2.sch' could not be propagated to the subscriber. RRS feed

  • Question

  • hi,

    I made a merge replication and used a pull subscription , i always got the following error:

    The schema script 'Course_2.sch' could not be propagated to the subscriber.

    -in Articles option at publication side i put the property (Copy XML Index to false)

    Please any idea to solve that ?

    I am using the final release of sql server 2005.

    Thanks,

    Tarek
    Monday, December 12, 2005 5:57 PM

Answers

  • I assume this is a remote subscriber, meaning it's on a different machine than the publisher.  If this is the case, then your snapshot folder needs to be a UNC path/share that's available to all the subscribers.
    Tuesday, December 13, 2005 4:06 PM

All replies

  • Is there any additional error that you can post?  If not, can you locate this file "Course_2.sch" in your snapshot folder, and manually run it at the subscriber to see what the error is?
    Tuesday, December 13, 2005 5:54 AM
  • Error messages:

    The schema script 'Course_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
    Get help: http://help/MSSQL_REPL-2147201001

    The process could not read file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\ReplData\unc\myserver_mydb_MYPUBLICATION\20051213015929\Course_2.sch' due to OS error 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL0)
    Get help: http://help/MSSQL_REPL0

    The system cannot find the path specified.
    (Source: MSSQL_REPL, Error number: MSSQL_REPL3)
    Get help: http://help/MSSQL_REPL3



    Thanks,

    Tuesday, December 13, 2005 8:02 AM
  • I assume this is a remote subscriber, meaning it's on a different machine than the publisher.  If this is the case, then your snapshot folder needs to be a UNC path/share that's available to all the subscribers.
    Tuesday, December 13, 2005 4:06 PM
  • I have same problem too. How can we set the snapshot folder into UNC path/share ? I have this problems when I try to add subscriber on SQL Mobile and the publisher is SQL Server 2005 Enterprise.
    I've got the following error like this :

    Error messages:
    The schema script 'C:\Program Files\Microsoft SQL        
    Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
    Get help: http://help/MSSQL_REPL-2147024891
    The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
    Get help: http://help/MSSQL_REPL-2147201001

    Can you help me to resolve this problem, this urgent.

    Thank you.
    Friday, March 3, 2006 11:22 AM
  • My problem is similar, except that the full text of the constraint is shown in the message:

     

    The schema script 'if object_id(N'[dbo].[ProposalDocs]') is not null exec('ALTER TABLE [dbo].[ProposalDocs] ADD CONSTRAINT
    FK_ProposalDocs_Proposal FOREIGN KEY
    (
    ProposalID
    ) REFERENCES dbo.Proposal
    (
    ProposalID
    ) ON UPDATE NO ACTION
    ON DELETE CASCADE

    ')' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
    Get help: http://help/MSSQL_REPL-2147201001

     

    The link to MS help, of course, provides no assistance.

     

    I cannot find the above piece of script anywhere in the snapshot folder. This is a pull subscription to a merge replication -- between a laptop running a C# .NET app under SQL Express 2005 on Windows XP and a Windows 2003 Server running SQL Server 2005. All are on the latest service packs.

     

    What happens is that one of the 15 or so laptops that replicate with the server will take more than just a minute or so to replicate, the user gets impatient and kills the process, which somehow puts a monkey-wrench in the gears and replication will not work after that. However, they'll have data (proposals) on the laptop that they need to replicate to the server. Now, I can educate the users not to kill these processes, but once the machinery is stuck, I don't know how to get it unstuck. We've tried reinitializing the subscription, checking the box that makes it try to upload changes from the subscriber to the publisher before doing so, but that's when

    Friday, June 1, 2007 7:16 PM
  • Im having similar problems as above,

     

    Running a merge replication between two 05 machines on a network, can get the replication to work WITHOUT enabling the 'View' articles, but everytime I add Views to the replication I get;

     

    The schema script 'gh0E42DB81D08F195ba480c_30.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
    Get help: http://help/MSSQL_REPL-2147201001

     

    Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL20164)
    Get help: http://help/MSSQL_REPL20164

     

    Invalid column name 'guidlocal'. (Source: MSSQLServer, Error number: 207)
    Get help: http://help/207

     

    Will adding the schemas to the replication allow me to make tables changes; adding columns etc?

     

    I have made by UNC folder on the publisher a share, this does not fix the problem.

    Friday, June 15, 2007 12:55 AM
  •  Greg Y wrote:
    I assume this is a remote subscriber, meaning it's on a different machine than the publisher.  If this is the case, then your snapshot folder needs to be a UNC path/share that's available to all the subscribers.

     

    Is this also the case with a Push subscription??

     

    I have a similar problem. I have set up a merge replication with a push subscription on 2 different servers, both running Win2000 and SQL 20000 SP4, and the merge agent fails with a similar error message:

     

    The schema script '\\SERVER\D$\Microsoft SQL Server\Data Files\MSSQL\ReplData\unc\SERVER_TEST_TEST\20071009235511\TABLETYPE_92.sch' could not be propagated to the subscriber.

     

    The UNC is not available to the subscribing server. I'm farly sure this used to work when we were running SQL2000 SP3 but since moving to SP4, we get the problem.

     

    I'm only publishing tables, no views or stored procedures. Also, I have checked the script and have set up the replication again but without the article the specific script refers to. You get the same error as above but just with a different script.

     

    I have searched the web high and dry for this to no avail. I'd be very grateful for any help anyone could offer.

     

    Thanks.

    Wednesday, October 10, 2007 10:42 AM
  • Has anyone found a solution to this issue?  I am having the same problem!
    Wednesday, August 5, 2009 2:02 PM
  • I have the same problem, I have changed the default snapshot location (http://msdn2.microsoft.com/en-us/library/ms151258.aspx) and the remote server has access to that folder that is in this format: \\serverip\snapshot_folder

    The error again: The schema script 'tablename_2.sch' could not be propagated to the subscriber.

    The publication server is in sql server 2008, the suscription server is in sql server 2005.

    Any help would be great.

    Thanks.
    Wednesday, November 18, 2009 2:26 PM
  • The problem was that the files in the snapshot with .sch are script files that creates the schema of a table and for some reason generates an error. In my case was a relationship to another table that was not in the snapshot to the subscriber database. What I have to do was to remove that relationships and then the snapshot executes succesfully. It could be many other reasons, for check the reason of the error, go to snapshot physical files locate and open the .sch file and execute this code in the subscriber database and see the errors.

    I hope this could be a help for someone.

    Thanks

    PD: (Sorry for my english)
    Saturday, December 5, 2009 11:40 PM
  • Reading this gives me the impression that another consideration for unc path has to do with the distributor being on a different server. At least that's what I see. Same error: The schema script 'Member_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001) But in this case Publisher and Subscriber on the same server while the Distributor lies on a different server (different IP).
    R, J
    Monday, June 6, 2011 3:18 PM
  • Tarek,

    The way I have gotten around this in the past is to create the identical folder on the sub.  This works great if you are using FTP to fetch the snapshot.  So say the snapshot location on the publisher is C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\ReplData\unc\myserver_mydb_MYPUBLICATION\20051213015929 then I would create the following folder on the subscriber:


    c:\repldata\ftp\myserver_mydb_MYPUBLICATION\20051213015929


    Otherwise its as the pros say.  You must have a user on the sub that has full permissions to the snapshot folder on the server.

    Tuesday, June 7, 2011 3:01 PM
  • Thanks Gery, this was really helpful.... was struggling for this issue from last 2 days...
    Thursday, August 9, 2012 3:21 AM