Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Incremental Article Additions to an Existing Merge Publica..

 
   Database Forums (Home) -> Replication RSS
Next:  Can get ragged hierarchies to work  
Author Message
"Venketash

External


Since: Feb 05, 2008
Posts: 7



(Msg. 1) Posted: Tue Feb 05, 2008 12:01 pm
Post subject: Incremental Article Additions to an Existing Merge Publication
Archived from groups: microsoft>public>sqlserver>replication (more info?)

Hi there,

We are running Merge Replication for SSL between SQL Server 2005 Standard
Edition SP2 Server and SQL Server 2005 Express Edition SP2 (With Advanced
Services) Subscribers. We actually have 3 publications per SUBSCRIBER, one
for tables, one for SPs and one for Views. The application that uses this is
a Recruitment Solution and we have had numerous issues with having to
re-initiliase subscribers either when changes have been made to the
publication or just with other various errors, so the multiple publications
seemed a good way to go in terms of limiting risk.

The problem we are having each time we add an article however looks to be
exactly the same as...

http://support.microsoft.com/kb/320600

....i.e.:

2008-02-02 15:10:20.220 The schema script 'viewEntityClien6d9b4807_24.sch'
could not be propagated to the subscriber.
2008-02-02 15:10:20.230 OLE DB Subscriber 'PSR-DEV2007\PeopleSource': {call
sys.sp_MSadd_merge_history90
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2008-02-02 15:10:20.250 Percent Complete: 0
2008-02-02 15:10:20.250 The schema script 'viewEntityClien6d9b4807_24.sch'
could not be propagated to the subscriber.
2008-02-02 15:10:20.330 Percent Complete: 0
2008-02-02 15:10:20.330 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'viewEntityClien6d9b4807_24.sch' could not be
propagated to the subscriber.
2008-02-02 15:10:20.330 Percent Complete: 0
2008-02-02 15:10:20.330 Category:AGENT
Source: PSR-DEV2007\PeopleSource
Number: 0
Message: The process could not read file 'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\ReplData\unc\TITANIUM_PSRDEVELOPMENT_PSRDEVELOPMENT_PUBLICA8e4e4ccd\20080202154959\viewEntityClien6d9b4807_24.sch'
due to OS error 3.

This file does however exist in that directory on the server with matching
permissions to the other files in the snapshot directory, but it is simply
not picked up. That link mentions that this was a bug in SQL 2000 and for
when using FTP, surely it has been addressed by now?

The only thing that seems to help is re-initialising all the suscribers,
which in some cases is GBs worth of data. It is so strange to me that it
works after the re-initialisation as nothing is different really? The same
files etc are still there, but suddenly it is able to find the new ones?

Has anyone else had this problem or know how to fix it? It is quite urgent
as we need to roll out an update with additional articles.

Your help would be much appreciated.

Kind regards,

-Venketash (Pat) Ramadass
emediaIT

 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
"Venketash

External


Since: Feb 05, 2008
Posts: 7



(Msg. 2) Posted: Wed Feb 06, 2008 3:00 am
Post subject: Re: Incremental Article Additions to an Existing Merge Publication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi there,

Has anyone had this issue or similar? Any known fixes?

To clraify we are using SSL to perform the replication and not FTP etc?

Thanks,

-Venketash (Pat) Ramadass
emediaIT

"Venketash (Pat) Ramadass" wrote in message

> Hi there,
>
> We are running Merge Replication for SSL between SQL Server 2005 Standard
> Edition SP2 Server and SQL Server 2005 Express Edition SP2 (With Advanced
> Services) Subscribers. We actually have 3 publications per SUBSCRIBER, one
> for tables, one for SPs and one for Views. The application that uses this
> is a Recruitment Solution and we have had numerous issues with having to
> re-initiliase subscribers either when changes have been made to the
> publication or just with other various errors, so the multiple
> publications seemed a good way to go in terms of limiting risk.
>
> The problem we are having each time we add an article however looks to be
> exactly the same as...
>
> http://support.microsoft.com/kb/320600
>
> ...i.e.:
>
> 2008-02-02 15:10:20.220 The schema script 'viewEntityClien6d9b4807_24.sch'
> could not be propagated to the subscriber.
> 2008-02-02 15:10:20.230 OLE DB Subscriber 'PSR-DEV2007\PeopleSource':
> {call sys.sp_MSadd_merge_history90
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> 2008-02-02 15:10:20.250 Percent Complete: 0
> 2008-02-02 15:10:20.250 The schema script 'viewEntityClien6d9b4807_24.sch'
> could not be propagated to the subscriber.
> 2008-02-02 15:10:20.330 Percent Complete: 0
> 2008-02-02 15:10:20.330 Category:NULL
> Source: Merge Replication Provider
> Number: -2147201001
> Message: The schema script 'viewEntityClien6d9b4807_24.sch' could not be
> propagated to the subscriber.
> 2008-02-02 15:10:20.330 Percent Complete: 0
> 2008-02-02 15:10:20.330 Category:AGENT
> Source: PSR-DEV2007\PeopleSource
> Number: 0
> Message: The process could not read file 'C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\ReplData\unc\TITANIUM_PSRDEVELOPMENT_PSRDEVELOPMENT_PUBLICA8e4e4ccd\20080202154959\viewEntityClien6d9b4807_24.sch'
> due to OS error 3.
>
> This file does however exist in that directory on the server with matching
> permissions to the other files in the snapshot directory, but it is simply
> not picked up. That link mentions that this was a bug in SQL 2000 and for
> when using FTP, surely it has been addressed by now?
>
> The only thing that seems to help is re-initialising all the suscribers,
> which in some cases is GBs worth of data. It is so strange to me that it
> works after the re-initialisation as nothing is different really? The same
> files etc are still there, but suddenly it is able to find the new ones?
>
> Has anyone else had this problem or know how to fix it? It is quite urgent
> as we need to roll out an update with additional articles.
>
> Your help would be much appreciated.
>
> Kind regards,
>
> -Venketash (Pat) Ramadass
> emediaIT

 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
Hilary Cotter

External


Since: Oct 09, 2005
Posts: 78



(Msg. 3) Posted: Thu Feb 07, 2008 6:00 am
Post subject: Re: Incremental Article Additions to an Existing Merge Publication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

This problem might be a timeout issue. Set OutputVerboseLevle to 3
and HistoryVerboseLevel to 3. Pipe the results to an output file
(using Output). Post it here.

You might want to put your subscriber database into bulk logged
recovery model, and kick all users off the subscriber. Set
QueryTimeOut to 600, use -InProcLoader, and set MaxBCPThreads to 7.

See if this doesn't solve your issue.
On Feb 6, 1:27 am, "Venketash \(Pat\) Ramadass"
wrote:
> Hi there,
>
> Has anyone had this issue or similar? Any known fixes?
>
> To clraify we are using SSL to perform the replication and not FTP etc?
>
> Thanks,
>
> -Venketash (Pat) Ramadass
> emediaIT
>
> "Venketash (Pat) Ramadass" wrote in messagenews:7350B189-42D4-4E87-B1C6-D754C330A94A@microsoft.com...
>
>
>
> > Hi there,
>
> > We are running Merge Replication for SSL between SQL Server 2005 Standard
> > Edition SP2 Server and SQL Server 2005 Express Edition SP2 (With Advanced
> > Services) Subscribers. We actually have 3 publications per SUBSCRIBER, one
> > for tables, one for SPs and one for Views. The application that uses this
> > is a Recruitment Solution and we have had numerous issues with having to
> > re-initiliase subscribers either when changes have been made to the
> > publication or just with other various errors, so the multiple
> > publications seemed a good way to go in terms of limiting risk.
>
> > The problem we are having each time we add an article however looks to be
> > exactly the same as...
>
> >http://support.microsoft.com/kb/320600
>
> > ...i.e.:
>
> > 2008-02-02 15:10:20.220 The schema script 'viewEntityClien6d9b4807_24.sch'
> > could not be propagated to the subscriber.
> > 2008-02-02 15:10:20.230 OLE DB Subscriber 'PSR-DEV2007\PeopleSource':
> > {call sys.sp_MSadd_merge_history90
> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,­?,?,?,?,?,?,?,?)}
> > 2008-02-02 15:10:20.250 Percent Complete: 0
> > 2008-02-02 15:10:20.250 The schema script 'viewEntityClien6d9b4807_24.sch'
> > could not be propagated to the subscriber.
> > 2008-02-02 15:10:20.330 Percent Complete: 0
> > 2008-02-02 15:10:20.330 Category:NULL
> > Source:  Merge Replication Provider
> > Number:  -2147201001
> > Message: The schema script 'viewEntityClien6d9b4807_24.sch' could not be
> > propagated to the subscriber.
> > 2008-02-02 15:10:20.330 Percent Complete: 0
> > 2008-02-02 15:10:20.330 Category:AGENT
> > Source:  PSR-DEV2007\PeopleSource
> > Number:  0
> > Message: The process could not read file 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\ReplData\unc\TITANIUM_PSRDEVELOPMENT_PSRDEVELOPMENT_PU­BLICA8e4e4ccd\20080202154959\viewEntityClien6d9b4807_24.sch'
> > due to OS error 3.
>
> > This file does however exist in that directory on the server with matching
> > permissions to the other files in the snapshot directory, but it is simply
> > not picked up. That link mentions that this was a bug in SQL 2000 and for
> > when using FTP, surely it has been addressed by now?
>
> > The only thing that seems to help is re-initialising all the suscribers,
> > which in some cases is GBs worth of data. It is so strange to me that it
> > works after the re-initialisation as nothing is different really? The same
> > files etc are still there, but suddenly it is able to find the new ones?
>
> > Has anyone else had this problem or know how to fix it? It is quite urgent
> > as we need to roll out an update with additional articles.
>
> > Your help would be much appreciated.
>
> > Kind regards,
>
> > -Venketash (Pat) Ramadass
> > emediaIT- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
"Venketash

External


Since: Feb 05, 2008
Posts: 7



(Msg. 4) Posted: Sun Feb 10, 2008 5:01 pm
Post subject: Re: Incremental Article Additions to an Existing Merge Publication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi there,

Thanks for the response.

The output that I pasted in my original post is from the replmerg.exe
running with OuputVerboveLevel 3 when run on the subscrieber.

I am going to set the -UseInprocLoader, and set MaxBCPThreads to 7 as
parameters on replmerg.exe on the subcribers, we are currently using...

2008-02-10 17:59:30.484 User-specified agent parameter values:
-Publication PSRDevelopment_publication
-Publisher
-PublisherDB
-PublisherSecurityMode 0
-PublisherLogin
-PublisherPassword **********
-Distributor
-DistributorSecurityMode 0
-DistributorLogin
-DistributorPassword **********
-Subscriber PSR-DEV2007\PeopleSource
-SubscriberDB PSRecruitment
-SubscriberSecurityMode 0
-SubscriberLogin sa
-SubscriberPassword **********
-OutputVerboseLevel 3
-SubscriptionType 2
-ParallelUploadDownload 0
-InternetURL
-InternetLogin
-InternetPassword **********
-DownloadGenerationsPerBatch 10
-DownloadReadChangesPerBatch 10
-DownloadWriteChangesPerBatch 10
-UploadGenerationsPerBatch 5
-UploadReadChangesPerBatch 10
-UploadWriteChangesPerBatch 10
-QueryTimeOut 600

....I have removed some settings above for security reasons. Are there any
other changes that should be made to improve performance over slow
connections and also with subscribers that have limited CPU and RAM?

With the recovery model I was planning to include scripts to set it to
bulk/full via the "Run additional scripts" on the publications in question,
is this the correct way to do this?

Thanks for all your help.

Kind regards,

-Pat Ramadass
emediaIT

"Hilary Cotter" wrote in message

This problem might be a timeout issue. Set OutputVerboseLevle to 3
and HistoryVerboseLevel to 3. Pipe the results to an output file
(using Output). Post it here.

You might want to put your subscriber database into bulk logged
recovery model, and kick all users off the subscriber. Set
QueryTimeOut to 600, use -InProcLoader, and set MaxBCPThreads to 7.

See if this doesn't solve your issue.
On Feb 6, 1:27 am, "Venketash \(Pat\) Ramadass"
wrote:
> Hi there,
>
> Has anyone had this issue or similar? Any known fixes?
>
> To clraify we are using SSL to perform the replication and not FTP etc?
>
> Thanks,
>
> -Venketash (Pat) Ramadass
> emediaIT
>
> "Venketash (Pat) Ramadass" wrote in
> messagenews:7350B189-42D4-4E87-B1C6-D754C330A94A@microsoft.com...
>
>
>
> > Hi there,
>
> > We are running Merge Replication for SSL between SQL Server 2005
> > Standard
> > Edition SP2 Server and SQL Server 2005 Express Edition SP2 (With
> > Advanced
> > Services) Subscribers. We actually have 3 publications per SUBSCRIBER,
> > one
> > for tables, one for SPs and one for Views. The application that uses
> > this
> > is a Recruitment Solution and we have had numerous issues with having to
> > re-initiliase subscribers either when changes have been made to the
> > publication or just with other various errors, so the multiple
> > publications seemed a good way to go in terms of limiting risk.
>
> > The problem we are having each time we add an article however looks to
> > be
> > exactly the same as...
>
> >http://support.microsoft.com/kb/320600
>
> > ...i.e.:
>
> > 2008-02-02 15:10:20.220 The schema script
> > 'viewEntityClien6d9b4807_24.sch'
> > could not be propagated to the subscriber.
> > 2008-02-02 15:10:20.230 OLE DB Subscriber 'PSR-DEV2007\PeopleSource':
> > {call sys.sp_MSadd_merge_history90
> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,­?,?,?,?,?,?,?,?)}
> > 2008-02-02 15:10:20.250 Percent Complete: 0
> > 2008-02-02 15:10:20.250 The schema script
> > 'viewEntityClien6d9b4807_24.sch'
> > could not be propagated to the subscriber.
> > 2008-02-02 15:10:20.330 Percent Complete: 0
> > 2008-02-02 15:10:20.330 Category:NULL
> > Source: Merge Replication Provider
> > Number: -2147201001
> > Message: The schema script 'viewEntityClien6d9b4807_24.sch' could not be
> > propagated to the subscriber.
> > 2008-02-02 15:10:20.330 Percent Complete: 0
> > 2008-02-02 15:10:20.330 Category:AGENT
> > Source: PSR-DEV2007\PeopleSource
> > Number: 0
> > Message: The process could not read file 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\ReplData\unc\TITANIUM_PSRDEVELOPMENT_PSRDEVELOPMENT_PU­BLICA8e4e4ccd\20080202154959\viewEntityClien6d9b4807_24.sch'
> > due to OS error 3.
>
> > This file does however exist in that directory on the server with
> > matching
> > permissions to the other files in the snapshot directory, but it is
> > simply
> > not picked up. That link mentions that this was a bug in SQL 2000 and
> > for
> > when using FTP, surely it has been addressed by now?
>
> > The only thing that seems to help is re-initialising all the suscribers,
> > which in some cases is GBs worth of data. It is so strange to me that it
> > works after the re-initialisation as nothing is different really? The
> > same
> > files etc are still there, but suddenly it is able to find the new ones?
>
> > Has anyone else had this problem or know how to fix it? It is quite
> > urgent
> > as we need to roll out an update with additional articles.
>
> > Your help would be much appreciated.
>
> > Kind regards,
>
> > -Venketash (Pat) Ramadass
> > emediaIT- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
"Venketash

External


Since: Feb 05, 2008
Posts: 7



(Msg. 5) Posted: Sun Feb 10, 2008 5:01 pm
Post subject: Re: Incremental Article Additions to an Existing Merge Publication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi there again,

Further to this I used the settings below and also a compressed snapshot and
then added a test view to the existing publication. It now gives...

2008-02-10 20:25:49.908 A failure occurred when accessing
'viewTestView_53.sch' due to an operating system error [2=''] during Web
synchronization. Ensure that the -InternetLogin user when using basic
authentication and the user running the merge when using Windows integrated
authentication has been granted access to the snapshot share.
2008-02-10 20:25:49.918 Percent Complete: 0 2008-02-10 20:25:49.918
Category:NULL
Source: Merge Process
Number: -2147467259
Message: A failure occurred when accessing 'viewTestView_53.sch' due to an
operating system error [2=''] during Web synchronization. Ensure that
the -InternetLogin user when using basic authentication and the user running
the merge when using Windows integrated authentication has been granted
access to the snapshot share.
2008-02-10 20:25:49.918 Percent Complete: 0 2008-02-10 20:25:49.918
Category:NULL
Source: Merge Process
Number: -2147467259
Message: The processing of the response message failed.

....which is similar to...

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=417870&SiteID=17

....it looks to me like it must be an issue on the subscriber if this does
not even work with a compressed snapshot unless the publication is
re-initialised?

Thanks a lot,

-Venketash (Pat) Ramadass
emediaIT

"Venketash (Pat) Ramadass" wrote in message

> Hi there,
>
> Thanks for the response.
>
> The output that I pasted in my original post is from the replmerg.exe
> running with OuputVerboveLevel 3 when run on the subscrieber.
>
> I am going to set the -UseInprocLoader, and set MaxBCPThreads to 7 as
> parameters on replmerg.exe on the subcribers, we are currently using...
>
> 2008-02-10 17:59:30.484 User-specified agent parameter values:
> -Publication PSRDevelopment_publication
> -Publisher
> -PublisherDB
> -PublisherSecurityMode 0
> -PublisherLogin
> -PublisherPassword **********
> -Distributor
> -DistributorSecurityMode 0
> -DistributorLogin
> -DistributorPassword **********
> -Subscriber PSR-DEV2007\PeopleSource
> -SubscriberDB PSRecruitment
> -SubscriberSecurityMode 0
> -SubscriberLogin sa
> -SubscriberPassword **********
> -OutputVerboseLevel 3
> -SubscriptionType 2
> -ParallelUploadDownload 0
> -InternetURL
> -InternetLogin
> -InternetPassword **********
> -DownloadGenerationsPerBatch 10
> -DownloadReadChangesPerBatch 10
> -DownloadWriteChangesPerBatch 10
> -UploadGenerationsPerBatch 5
> -UploadReadChangesPerBatch 10
> -UploadWriteChangesPerBatch 10
> -QueryTimeOut 600
>
> ...I have removed some settings above for security reasons. Are there any
> other changes that should be made to improve performance over slow
> connections and also with subscribers that have limited CPU and RAM?
>
> With the recovery model I was planning to include scripts to set it to
> bulk/full via the "Run additional scripts" on the publications in
> question, is this the correct way to do this?
>
> Thanks for all your help.
>
> Kind regards,
>
> -Pat Ramadass
> emediaIT
>
> "Hilary Cotter" wrote in message
>
> This problem might be a timeout issue. Set OutputVerboseLevle to 3
> and HistoryVerboseLevel to 3. Pipe the results to an output file
> (using Output). Post it here.
>
> You might want to put your subscriber database into bulk logged
> recovery model, and kick all users off the subscriber. Set
> QueryTimeOut to 600, use -InProcLoader, and set MaxBCPThreads to 7.
>
> See if this doesn't solve your issue.
> On Feb 6, 1:27 am, "Venketash \(Pat\) Ramadass"
> wrote:
>> Hi there,
>>
>> Has anyone had this issue or similar? Any known fixes?
>>
>> To clraify we are using SSL to perform the replication and not FTP etc?
>>
>> Thanks,
>>
>> -Venketash (Pat) Ramadass
>> emediaIT
>>
>> "Venketash (Pat) Ramadass" wrote in
>> messagenews:7350B189-42D4-4E87-B1C6-D754C330A94A@microsoft.com...
>>
>>
>>
>> > Hi there,
>>
>> > We are running Merge Replication for SSL between SQL Server 2005
>> > Standard
>> > Edition SP2 Server and SQL Server 2005 Express Edition SP2 (With
>> > Advanced
>> > Services) Subscribers. We actually have 3 publications per SUBSCRIBER,
>> > one
>> > for tables, one for SPs and one for Views. The application that uses
>> > this
>> > is a Recruitment Solution and we have had numerous issues with having
>> > to
>> > re-initiliase subscribers either when changes have been made to the
>> > publication or just with other various errors, so the multiple
>> > publications seemed a good way to go in terms of limiting risk.
>>
>> > The problem we are having each time we add an article however looks to
>> > be
>> > exactly the same as...
>>
>> >http://support.microsoft.com/kb/320600
>>
>> > ...i.e.:
>>
>> > 2008-02-02 15:10:20.220 The schema script
>> > 'viewEntityClien6d9b4807_24.sch'
>> > could not be propagated to the subscriber.
>> > 2008-02-02 15:10:20.230 OLE DB Subscriber 'PSR-DEV2007\PeopleSource':
>> > {call sys.sp_MSadd_merge_history90
>> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,­?,?,?,?,?,?,?,?)}
>> > 2008-02-02 15:10:20.250 Percent Complete: 0
>> > 2008-02-02 15:10:20.250 The schema script
>> > 'viewEntityClien6d9b4807_24.sch'
>> > could not be propagated to the subscriber.
>> > 2008-02-02 15:10:20.330 Percent Complete: 0
>> > 2008-02-02 15:10:20.330 Category:NULL
>> > Source: Merge Replication Provider
>> > Number: -2147201001
>> > Message: The schema script 'viewEntityClien6d9b4807_24.sch' could not
>> > be
>> > propagated to the subscriber.
>> > 2008-02-02 15:10:20.330 Percent Complete: 0
>> > 2008-02-02 15:10:20.330 Category:AGENT
>> > Source: PSR-DEV2007\PeopleSource
>> > Number: 0
>> > Message: The process could not read file 'C:\Program Files\Microsoft
>> > SQL
>> > Server\MSSQL.1\MSSQL\ReplData\unc\TITANIUM_PSRDEVELOPMENT_PSRDEVELOPMENT_PU­BLICA8e4e4ccd\20080202154959\viewEntityClien6d9b4807_24.sch'
>> > due to OS error 3.
>>
>> > This file does however exist in that directory on the server with
>> > matching
>> > permissions to the other files in the snapshot directory, but it is
>> > simply
>> > not picked up. That link mentions that this was a bug in SQL 2000 and
>> > for
>> > when using FTP, surely it has been addressed by now?
>>
>> > The only thing that seems to help is re-initialising all the
>> > suscribers,
>> > which in some cases is GBs worth of data. It is so strange to me that
>> > it
>> > works after the re-initialisation as nothing is different really? The
>> > same
>> > files etc are still there, but suddenly it is able to find the new
>> > ones?
>>
>> > Has anyone else had this problem or know how to fix it? It is quite
>> > urgent
>> > as we need to roll out an update with additional articles.
>>
>> > Your help would be much appreciated.
>>
>> > Kind regards,
>>
>> > -Venketash (Pat) Ramadass
>> > emediaIT- Hide quoted text -
>>
>> - Show quoted text -
>
 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
Hilary Cotter

External


Since: Oct 09, 2005
Posts: 78



(Msg. 6) Posted: Mon Feb 11, 2008 7:23 am
Post subject: Re: Incremental Article Additions to an Existing Merge Publication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Make sure the InternetLogin and the PublisherLogin have rights to to
read the snapshot share.

How large is your snapshot?

Hilary
On Feb 10, 3:56 pm, "Venketash \(Pat\) Ramadass"
wrote:
> Hi there again,
>
> Further to this I used the settings below and also a compressed snapshot and
> then added a test view to the existing publication. It now gives...
>
> 2008-02-10 20:25:49.908 A failure occurred when accessing
> 'viewTestView_53.sch' due to an operating system error [2=''] during Web
> synchronization. Ensure that the -InternetLogin user when using basic
> authentication and the user running the merge when using Windows integrated
> authentication has been granted access to the snapshot share.
> 2008-02-10 20:25:49.918 Percent Complete: 0 2008-02-10 20:25:49.918
> Category:NULL
> Source:  Merge Process
> Number:  -2147467259
> Message: A failure occurred when accessing 'viewTestView_53.sch' due to an
> operating system error [2=''] during Web synchronization. Ensure that
> the -InternetLogin user when using basic authentication and the user running
> the merge when using Windows integrated authentication has been granted
> access to the snapshot share.
> 2008-02-10 20:25:49.918 Percent Complete: 0 2008-02-10 20:25:49.918
> Category:NULL
> Source:  Merge Process
> Number:  -2147467259
> Message: The processing of the response message failed.
>
> ...which is similar to...
>
> http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=417870&SiteI...
>
> ...it looks to me like it must be an issue on the subscriber if this does
> not even work with a compressed snapshot unless the publication is
> re-initialised?
>
> Thanks a lot,
>
> -Venketash (Pat) Ramadass
> emediaIT
>
> "Venketash (Pat) Ramadass" wrote in messagenews:9A7F9C17-B653-4EA7-9102-33F809C414F3@microsoft.com...
>
>
>
> > Hi there,
>
> > Thanks for the response.
>
> > The output that I pasted in my original post is from the replmerg.exe
> > running with OuputVerboveLevel 3 when run on the subscrieber.
>
> > I am going to set the -UseInprocLoader, and set MaxBCPThreads to 7 as
> > parameters on replmerg.exe on the subcribers, we are currently using...
>
> > 2008-02-10 17:59:30.484 User-specified agent parameter values:
> >   -Publication PSRDevelopment_publication
> >   -Publisher
> >   -PublisherDB
> >   -PublisherSecurityMode 0
> >   -PublisherLogin
> >   -PublisherPassword **********
> >   -Distributor
> >   -DistributorSecurityMode 0
> >   -DistributorLogin
> >   -DistributorPassword **********
> >   -Subscriber PSR-DEV2007\PeopleSource
> >   -SubscriberDB PSRecruitment
> >   -SubscriberSecurityMode 0
> >   -SubscriberLogin sa
> >   -SubscriberPassword **********
> >   -OutputVerboseLevel 3
> >   -SubscriptionType 2
> >   -ParallelUploadDownload 0
> >   -InternetURL
> >   -InternetLogin
> >   -InternetPassword **********
> >   -DownloadGenerationsPerBatch 10
> >   -DownloadReadChangesPerBatch 10
> >   -DownloadWriteChangesPerBatch 10
> >   -UploadGenerationsPerBatch 5
> >   -UploadReadChangesPerBatch 10
> >   -UploadWriteChangesPerBatch 10
> >   -QueryTimeOut 600
>
> > ...I have removed some settings above for security reasons. Are there any
> > other changes that should be made to improve performance over slow
> > connections and also with subscribers that have limited CPU and RAM?
>
> > With the recovery model I was planning to include scripts to set it to
> > bulk/full via the "Run additional scripts" on the publications in
> > question, is this the correct way to do this?
>
> > Thanks for all your help.
>
> > Kind regards,
>
> > -Pat Ramadass
> > emediaIT
>
> > "Hilary Cotter" wrote in message
> >
> > This problem might be a timeout issue. Set OutputVerboseLevle to 3
> > and HistoryVerboseLevel to 3. Pipe the results to an output file
> > (using Output). Post it here.
>
> > You might want to put your subscriber database into bulk logged
> > recovery model, and kick all users off the subscriber. Set
> > QueryTimeOut to 600, use  -InProcLoader, and set MaxBCPThreads to 7.
>
> > See if this doesn't solve your issue.
> > On Feb 6, 1:27 am, "Venketash \(Pat\) Ramadass"
> > wrote:
> >> Hi there,
>
> >> Has anyone had this issue or similar? Any known fixes?
>
> >> To clraify we are using SSL to perform the replication and not FTP etc?
>
> >> Thanks,
>
> >> -Venketash (Pat) Ramadass
> >> emediaIT
>
> >> "Venketash (Pat) Ramadass" wrote in
> >> messagenews:7350B189-42D4-4E87-B1C6-D754C330A94A@microsoft.com...
>
> >> > Hi there,
>
> >> > We are running Merge Replication for SSL between SQL Server 2005
> >> > Standard
> >> > Edition SP2 Server and SQL Server 2005 Express Edition SP2 (With
> >> > Advanced
> >> > Services) Subscribers. We actually have 3 publications per SUBSCRIBER,
> >> > one
> >> > for tables, one for SPs and one for Views. The application that uses
> >> > this
> >> > is a Recruitment Solution and we have had numerous issues with having
> >> > to
> >> > re-initiliase subscribers either when changes have been made to the
> >> > publication or just with other various errors, so the multiple
> >> > publications seemed a good way to go in terms of limiting risk.
>
> >> > The problem we are having each time we add an article however looks to
> >> > be
> >> > exactly the same as...
>
> >> >http://support.microsoft.com/kb/320600
>
> >> > ...i.e.:
>
> >> > 2008-02-02 15:10:20.220 The schema script
> >> > 'viewEntityClien6d9b4807_24.sch'
> >> > could not be propagated to the subscriber.
> >> > 2008-02-02 15:10:20.230 OLE DB Subscriber 'PSR-DEV2007\PeopleSource':
> >> > {call sys.sp_MSadd_merge_history90
> >> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,­­?,?,?,?,?,?,?,?)}
> >> > 2008-02-02 15:10:20.250 Percent Complete: 0
> >> > 2008-02-02 15:10:20.250 The schema script
> >> > 'viewEntityClien6d9b4807_24.sch'
> >> > could not be propagated to the subscriber.
> >> > 2008-02-02 15:10:20.330 Percent Complete: 0
> >> > 2008-02-02 15:10:20.330 Category:NULL
> >> > Source: Merge Replication Provider
> >> > Number: -2147201001
> >> > Message: The schema script 'viewEntityClien6d9b4807_24.sch' could not
> >> > be
> >> > propagated to the subscriber.
> >> > 2008-02-02 15:10:20.330 Percent Complete: 0
> >> > 2008-02-02 15:10:20.330 Category:AGENT
> >> > Source: PSR-DEV2007\PeopleSource
> >> > Number: 0
> >> > Message: The process could not read file 'C:\Program Files\Microsoft
> >> > SQL
> >> > Server\MSSQL.1\MSSQL\ReplData\unc\TITANIUM_PSRDEVELOPMENT_PSRDEVELOPMENT_PU­­BLICA8e4e4ccd\20080202154959\viewEntityClien6d9b4807_24.sch'
> >> > due to OS error 3.
>
> >> > This file does however exist in that directory on the server with
> >> > matching
> >> > permissions to the other files in the snapshot directory, but it is
> >> > simply
> >> > not picked up. That link mentions that this was a bug in SQL 2000 and
> >> > for
> >> > when using FTP, surely it has been addressed by now?
>
> >> > The only thing that seems to help is re-initialising all the
> >> > suscribers,
> >> > which in some cases is GBs worth of data. It is so strange to me that
> >> > it
> >> > works after the re-initialisation as nothing is different really? The
> >> > same
> >> > files etc are still there, but suddenly it is able to find the new
> >> > ones?
>
> >> > Has anyone else had this problem or know how to fix it? It is quite
> >> > urgent
> >> > as we need to roll out an update with additional articles.
>
> >> > Your help would be much appreciated.
>
> >> > Kind regards,
>
> >> > -Venketash (Pat) Ramadass
> >> > emediaIT- Hide quoted text -
>
> >> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
"Venketash

External


Since: Feb 05, 2008
Posts: 7



(Msg. 7) Posted: Mon Feb 18, 2008 3:01 pm
Post subject: Re: Incremental Article Additions to an Existing Merge Publication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi there again,

Some of the snapshots are pretty big, over 2GB in total for the entire
database. Can the size of the snapshot play a part in this?

Also are there any considerations for using a compressed snapshot?

Thanks,

-Pat

"Hilary Cotter" wrote in message

Make sure the InternetLogin and the PublisherLogin have rights to to
read the snapshot share.

How large is your snapshot?

Hilary
On Feb 10, 3:56 pm, "Venketash \(Pat\) Ramadass"
wrote:
> Hi there again,
>
> Further to this I used the settings below and also a compressed snapshot
> and
> then added a test view to the existing publication. It now gives...
>
> 2008-02-10 20:25:49.908 A failure occurred when accessing
> 'viewTestView_53.sch' due to an operating system error [2=''] during Web
> synchronization. Ensure that the -InternetLogin user when using basic
> authentication and the user running the merge when using Windows
> integrated
> authentication has been granted access to the snapshot share.
> 2008-02-10 20:25:49.918 Percent Complete: 0 2008-02-10 20:25:49.918
> Category:NULL
> Source: Merge Process
> Number: -2147467259
> Message: A failure occurred when accessing 'viewTestView_53.sch' due to an
> operating system error [2=''] during Web synchronization. Ensure that
> the -InternetLogin user when using basic authentication and the user
> running
> the merge when using Windows integrated authentication has been granted
> access to the snapshot share.
> 2008-02-10 20:25:49.918 Percent Complete: 0 2008-02-10 20:25:49.918
> Category:NULL
> Source: Merge Process
> Number: -2147467259
> Message: The processing of the response message failed.
>
> ...which is similar to...
>
> http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=417870&SiteI...
>
> ...it looks to me like it must be an issue on the subscriber if this does
> not even work with a compressed snapshot unless the publication is
> re-initialised?
>
> Thanks a lot,
>
> -Venketash (Pat) Ramadass
> emediaIT
>
> "Venketash (Pat) Ramadass" wrote in
> messagenews:9A7F9C17-B653-4EA7-9102-33F809C414F3@microsoft.com...
>
>
>
> > Hi there,
>
> > Thanks for the response.
>
> > The output that I pasted in my original post is from the replmerg.exe
> > running with OuputVerboveLevel 3 when run on the subscrieber.
>
> > I am going to set the -UseInprocLoader, and set MaxBCPThreads to 7 as
> > parameters on replmerg.exe on the subcribers, we are currently using...
>
> > 2008-02-10 17:59:30.484 User-specified agent parameter values:
> > -Publication PSRDevelopment_publication
> > -Publisher
> > -PublisherDB
> > -PublisherSecurityMode 0
> > -PublisherLogin
> > -PublisherPassword **********
> > -Distributor
> > -DistributorSecurityMode 0
> > -DistributorLogin
> > -DistributorPassword **********
> > -Subscriber PSR-DEV2007\PeopleSource
> > -SubscriberDB PSRecruitment
> > -SubscriberSecurityMode 0
> > -SubscriberLogin sa
> > -SubscriberPassword **********
> > -OutputVerboseLevel 3
> > -SubscriptionType 2
> > -ParallelUploadDownload 0
> > -InternetURL
> > -InternetLogin
> > -InternetPassword **********
> > -DownloadGenerationsPerBatch 10
> > -DownloadReadChangesPerBatch 10
> > -DownloadWriteChangesPerBatch 10
> > -UploadGenerationsPerBatch 5
> > -UploadReadChangesPerBatch 10
> > -UploadWriteChangesPerBatch 10
> > -QueryTimeOut 600
>
> > ...I have removed some settings above for security reasons. Are there
> > any
> > other changes that should be made to improve performance over slow
> > connections and also with subscribers that have limited CPU and RAM?
>
> > With the recovery model I was planning to include scripts to set it to
> > bulk/full via the "Run additional scripts" on the publications in
> > question, is this the correct way to do this?
>
> > Thanks for all your help.
>
> > Kind regards,
>
> > -Pat Ramadass
> > emediaIT
>
> > "Hilary Cotter" wrote in message
> >
> > This problem might be a timeout issue. Set OutputVerboseLevle to 3
> > and HistoryVerboseLevel to 3. Pipe the results to an output file
> > (using Output). Post it here.
>
> > You might want to put your subscriber database into bulk logged
> > recovery model, and kick all users off the subscriber. Set
> > QueryTimeOut to 600, use -InProcLoader, and set MaxBCPThreads to 7.
>
> > See if this doesn't solve your issue.
> > On Feb 6, 1:27 am, "Venketash \(Pat\) Ramadass"
> > wrote:
> >> Hi there,
>
> >> Has anyone had this issue or similar? Any known fixes?
>
> >> To clraify we are using SSL to perform the replication and not FTP etc?
>
> >> Thanks,
>
> >> -Venketash (Pat) Ramadass
> >> emediaIT
>
> >> "Venketash (Pat) Ramadass" wrote in
> >> messagenews:7350B189-42D4-4E87-B1C6-D754C330A94A@microsoft.com...
>
> >> > Hi there,
>
> >> > We are running Merge Replication for SSL between SQL Server 2005
> >> > Standard
> >> > Edition SP2 Server and SQL Server 2005 Express Edition SP2 (With
> >> > Advanced
> >> > Services) Subscribers. We actually have 3 publications per
> >> > SUBSCRIBER,
> >> > one
> >> > for tables, one for SPs and one for Views. The application that uses
> >> > this
> >> > is a Recruitment Solution and we have had numerous issues with having
> >> > to
> >> > re-initiliase subscribers either when changes have been made to the
> >> > publication or just with other various errors, so the multiple
> >> > publications seemed a good way to go in terms of limiting risk.
>
> >> > The problem we are having each time we add an article however looks
> >> > to
> >> > be
> >> > exactly the same as...
>
> >> >http://support.microsoft.com/kb/320600
>
> >> > ...i.e.:
>
> >> > 2008-02-02 15:10:20.220 The schema script
> >> > 'viewEntityClien6d9b4807_24.sch'
> >> > could not be propagated to the subscriber.
> >> > 2008-02-02 15:10:20.230 OLE DB Subscriber 'PSR-DEV2007\PeopleSource':
> >> > {call sys.sp_MSadd_merge_history90
> >> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,­­?,?,?,?,?,?,?,?)}
> >> > 2008-02-02 15:10:20.250 Percent Complete: 0
> >> > 2008-02-02 15:10:20.250 The schema script
> >> > 'viewEntityClien6d9b4807_24.sch'
> >> > could not be propagated to the subscriber.
> >> > 2008-02-02 15:10:20.330 Percent Complete: 0
> >> > 2008-02-02 15:10:20.330 Category:NULL
> >> > Source: Merge Replication Provider
> >> > Number: -2147201001
> >> > Message: The schema script 'viewEntityClien6d9b4807_24.sch' could not
> >> > be
> >> > propagated to the subscriber.
> >> > 2008-02-02 15:10:20.330 Percent Complete: 0
> >> > 2008-02-02 15:10:20.330 Category:AGENT
> >> > Source: PSR-DEV2007\PeopleSource
> >> > Number: 0
> >> > Message: The process could not read file 'C:\Program Files\Microsoft
> >> > SQL
> >> > Server\MSSQL.1\MSSQL\ReplData\unc\TITANIUM_PSRDEVELOPMENT_PSRDEVELOPMENT_PU­­BLICA8e4e4ccd\20080202154959\viewEntityClien6d9b4807_24.sch'
> >> > due to OS error 3.
>
> >> > This file does however exist in that directory on the server with
> >> > matching
> >> > permissions to the other files in the snapshot directory, but it is
> >> > simply
> >> > not picked up. That link mentions that this was a bug in SQL 2000 and
> >> > for
> >> > when using FTP, surely it has been addressed by now?
>
> >> > The only thing that seems to help is re-initialising all the
> >> > suscribers,
> >> > which in some cases is GBs worth of data. It is so strange to me that
> >> > it
> >> > works after the re-initialisation as nothing is different really? The
> >> > same
> >> > files etc are still there, but suddenly it is able to find the new
> >> > ones?
>
> >> > Has anyone else had this problem or know how to fix it? It is quite
> >> > urgent
> >> > as we need to roll out an update with additional articles.
>
> >> > Your help would be much appreciated.
>
> >> > Kind regards,
>
> >> > -Venketash (Pat) Ramadass
> >> > emediaIT- Hide quoted text -
>
> >> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
Paul Ibison1

External


Since: Mar 01, 2004
Posts: 640



(Msg. 8) Posted: Mon Feb 18, 2008 9:39 pm
Post subject: Re: Incremental Article Additions to an Existing Merge Publication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Don't know it if't relevant here but CAB files have a 2GB limitation AFAIR.
Regardless, for such large sizes, I'd generally advise generating the
snapshot, zipping it up yourself, FTPing the zipped file, unzipping then
initialize using a nosync setting. It'll be a huge amount faster.
Rgds,
Paul Ibison (www.replicationanswers.com)
 >> Stay informed about: Incremental Article Additions to an Existing Merge Publica.. 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Need to add merge article - SQL 2000 sp4 - I have an existing merge publication, I want a new table. I assume I would do the following, however I have some questions: I assume I call sp_addmergearticle, for the @article param, specify the new table. I also assume I would need t...

Error adding an article to a merge publication - What is the best way to add an article to a merge replication? sp_addmergearticle 'PUB_1','test_tbl','test_tbl', @force_invalidate_snapshot=1 Line 470 Publication 'PUB_1' does not support the nosync type because it contains a table that does not have...

Problem Applying Schema Changes to Existing Merge Publicat.. - Publisher: - Windows 2000 SP4 - SQL Server 2005 Subscriber: - Tablet XP SP2 - SQLExpress SP1 - Merge Pull subscriptions with parameterized filters All, As brief as I can: We have 2 table articles and a trigger in our publication. The 2..

sp_dropsubscription of an article - Say i have a table that is replication a million rows and is slow.. Half way across I realize its taking a long time and want to stop replicating that table but have other tables in that publication carry on, will a sp_dropsubscription of that article...

Adding an Article to a Publication - Hi: I have a publication with larger sql table articles. I want to add another article (small table). To start replicating, I will need to reinitialize and rerun the snaphot. I don't want to run the snapshot during the day time because it may bloc...
   Database Forums (Home) -> Replication All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]