Hello Group,
(I have posted this query in Microsoft Newsgroup also, but I did not get any response. Please respond. Thanx)
I have setup a Merge Replication between two
servers. (SERVER_PUBLISH is the Publisher and
SERVER_SUBSCRIBE is the Subscriber).
I was periodically getting Network errors, I tried looping
step 3 (both on success and failure) of the job back to
step 1. I have also given a higher number of retry
attempts and interval, but still at times I get this error
(mentioned below) and my replication stops. Is there a
way to automatically resume replication after such errors
occurs.
Please Help. This is very urgent.
Thanks in advance
Anand
Part of the error log is mentioned below =>
Downloading data changes to the Subscriber
Percent Complete: 4
No data needed to be merged.
Percent Complete: 4
Uploading data changes to the Publisher
Percent Complete: 4
No data needed to be merged.
Percent Complete: 4
Downloading data changes to the Subscriber
Percent Complete: 4
No data needed to be merged.
Percent Complete: 4
Uploading data changes to the Publisher
The merge process could not apply the replication metadata.
The process could not enumerate changes at
the 'Subscriber'.
The process could not enumerate changes at
the 'Subscriber'.
The merge process encountered an unexpected network error.
The connection to Subscriber 'SERVER_SUBSCRIBE' is no
longer available.
Percent Complete: 0
The merge process could not apply the replication metadata.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147200968
Message: The merge process could not apply the replication
metadata.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSproxiedmetadata(?,?,?,?)}{call
sp_MSproxiedmetadata(?,?,?,?)}{call sp_MSproxiedmetadata
(?,?,?,?)}{call sp_MSproxiedmetadata(?,?,?,?)}{call
sp_MSproxiedmetadata(?,?,?,?)}{call sp_MSproxiedmetadata
(?,?,?,?)}{call sp_MSproxiedmetadata(?,?,?,?)}
Percent Complete: 0
Category:SQLSERVER
Source: SERVER_SUBSCRIBE
Number: 11
Message: General network error. Check your network
documentation.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147199469
Message: The process was successfully stopped.
Disconnecting from Subscriber 'SERVER_SUBSCRIBE'
Disconnecting from Publisher 'SERVER_PUBLISH'
Disconnecting from Subscriber 'SERVER_SUBSCRIBE'
Disconnecting from Subscriber 'SERVER_SUBSCRIBE'
Disconnecting from Subscriber 'SERVER_SUBSCRIBE'
Disconnecting from Subscriber 'SERVER_SUBSCRIBE'
Disconnecting from Publisher 'SERVER_PUBLISH'
Disconnecting from Publisher 'SERVER_PUBLISH'
Disconnecting from Publisher 'SERVER_PUBLISH'
Disconnecting from Publisher 'SERVER_PUBLISH'
Disconnecting from Publisher 'SERVER_PUBLISH'
Disconnecting from Distributor 'SERVER_PUBLISH'Try setting up the Merge Agent to run on a schedule of every one minute. That way, it will start up again even if it has failed. Also, please do not say your request is "urgent". All of us that ask for help feel our requests are "urgent".
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Wednesday, March 21, 2012
Monday, March 19, 2012
Merge Replication over internet Problem: Couldn't propagate schema to the subscriber.
Yesterday I posted my problem on the group I would like to explain it
a bit so that I be able to make things more clear.
1. I have set up a Sql server as publisher/Distributor.
2. Setup MSDE as subscriber
3. Login mode to publisher/subscriber/Distributor is Sql Server
Authentication
and Login Name is SUPERVISOR.
4. Setup a merge pull replication over internet, using FTP snapshot to
be
downloaded from my FTP site 61.11.103.3
5. After all this setting I ran merge agent at the subscriber site
(owner of
the agent is SUPERVISOR)using sp_start_job stored procedure.
6. Following is the list of message that I can see in Job history of
merge
agent.
A. Connecting to Subscriber.
B. Connecting to Distributor.
C. Initializing.
D. Connecting to Publisher.
E. Retrieving publication information.
F. retrieving subscription information.
G. Snapshot files will be downloaded via FTP.
H. connecting to FTP site '61'11.103.3'
I. The subscription has been marked for reinitialization,
reinitialization
will occur next time you synchronize this subscription.
J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
\FTPDB_1.sch'could not be propagated to the subscriber.
K.Process could not retrieve file
'IM19_FTP_REPL_FTPREPL\20050110104749
\FTPDB_1.sch' from FTP site 61.11.103.3
L. The schema script could not be propagated to the
subscriber,Access denied:
File not Found.
M. The job failed. The job invoked by supervisor,the last step was
step 1.
Plz help me out, Hilary has mentioned in reply to my last mail to
change owner of the merge agent to 'Sa' but this is not working out
still I m getting the same problem.
Its very urgent and important too..
Ruchir,
Based on the error message it seems ftp login doesn't have the permission to
access the snapshot folder share on your distributor box. Please make sure
that ftp login has read permission to your snapshot folder. You can verify
it by using the ftp get cmd for your ftpdb_1.sch file.
thanks - Deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501102129.51fa8110@.posting.google.c om...
> Yesterday I posted my problem on the group I would like to explain it
> a bit so that I be able to make things more clear.
> 1. I have set up a Sql server as publisher/Distributor.
> 2. Setup MSDE as subscriber
> 3. Login mode to publisher/subscriber/Distributor is Sql Server
> Authentication
> and Login Name is SUPERVISOR.
> 4. Setup a merge pull replication over internet, using FTP snapshot to
> be
> downloaded from my FTP site 61.11.103.3
> 5. After all this setting I ran merge agent at the subscriber site
> (owner of
> the agent is SUPERVISOR)using sp_start_job stored procedure.
> 6. Following is the list of message that I can see in Job history of
> merge
> agent.
> A. Connecting to Subscriber.
> B. Connecting to Distributor.
> C. Initializing.
> D. Connecting to Publisher.
> E. Retrieving publication information.
> F. retrieving subscription information.
> G. Snapshot files will be downloaded via FTP.
> H. connecting to FTP site '61'11.103.3'
> I. The subscription has been marked for reinitialization,
> reinitialization
> will occur next time you synchronize this subscription.
> J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
> Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
> \FTPDB_1.sch'could not be propagated to the subscriber.
> K.Process could not retrieve file
> 'IM19_FTP_REPL_FTPREPL\20050110104749
> \FTPDB_1.sch' from FTP site 61.11.103.3
> L. The schema script could not be propagated to the
> subscriber,Access denied:
> File not Found.
> M. The job failed. The job invoked by supervisor,the last step was
> step 1.
>
> Plz help me out, Hilary has mentioned in reply to my last mail to
> change owner of the merge agent to 'Sa' but this is not working out
> still I m getting the same problem.
> Its very urgent and important too..
a bit so that I be able to make things more clear.
1. I have set up a Sql server as publisher/Distributor.
2. Setup MSDE as subscriber
3. Login mode to publisher/subscriber/Distributor is Sql Server
Authentication
and Login Name is SUPERVISOR.
4. Setup a merge pull replication over internet, using FTP snapshot to
be
downloaded from my FTP site 61.11.103.3
5. After all this setting I ran merge agent at the subscriber site
(owner of
the agent is SUPERVISOR)using sp_start_job stored procedure.
6. Following is the list of message that I can see in Job history of
merge
agent.
A. Connecting to Subscriber.
B. Connecting to Distributor.
C. Initializing.
D. Connecting to Publisher.
E. Retrieving publication information.
F. retrieving subscription information.
G. Snapshot files will be downloaded via FTP.
H. connecting to FTP site '61'11.103.3'
I. The subscription has been marked for reinitialization,
reinitialization
will occur next time you synchronize this subscription.
J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
\FTPDB_1.sch'could not be propagated to the subscriber.
K.Process could not retrieve file
'IM19_FTP_REPL_FTPREPL\20050110104749
\FTPDB_1.sch' from FTP site 61.11.103.3
L. The schema script could not be propagated to the
subscriber,Access denied:
File not Found.
M. The job failed. The job invoked by supervisor,the last step was
step 1.
Plz help me out, Hilary has mentioned in reply to my last mail to
change owner of the merge agent to 'Sa' but this is not working out
still I m getting the same problem.
Its very urgent and important too..
Ruchir,
Based on the error message it seems ftp login doesn't have the permission to
access the snapshot folder share on your distributor box. Please make sure
that ftp login has read permission to your snapshot folder. You can verify
it by using the ftp get cmd for your ftpdb_1.sch file.
thanks - Deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501102129.51fa8110@.posting.google.c om...
> Yesterday I posted my problem on the group I would like to explain it
> a bit so that I be able to make things more clear.
> 1. I have set up a Sql server as publisher/Distributor.
> 2. Setup MSDE as subscriber
> 3. Login mode to publisher/subscriber/Distributor is Sql Server
> Authentication
> and Login Name is SUPERVISOR.
> 4. Setup a merge pull replication over internet, using FTP snapshot to
> be
> downloaded from my FTP site 61.11.103.3
> 5. After all this setting I ran merge agent at the subscriber site
> (owner of
> the agent is SUPERVISOR)using sp_start_job stored procedure.
> 6. Following is the list of message that I can see in Job history of
> merge
> agent.
> A. Connecting to Subscriber.
> B. Connecting to Distributor.
> C. Initializing.
> D. Connecting to Publisher.
> E. Retrieving publication information.
> F. retrieving subscription information.
> G. Snapshot files will be downloaded via FTP.
> H. connecting to FTP site '61'11.103.3'
> I. The subscription has been marked for reinitialization,
> reinitialization
> will occur next time you synchronize this subscription.
> J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
> Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
> \FTPDB_1.sch'could not be propagated to the subscriber.
> K.Process could not retrieve file
> 'IM19_FTP_REPL_FTPREPL\20050110104749
> \FTPDB_1.sch' from FTP site 61.11.103.3
> L. The schema script could not be propagated to the
> subscriber,Access denied:
> File not Found.
> M. The job failed. The job invoked by supervisor,the last step was
> step 1.
>
> Plz help me out, Hilary has mentioned in reply to my last mail to
> change owner of the merge agent to 'Sa' but this is not working out
> still I m getting the same problem.
> Its very urgent and important too..
Saturday, February 25, 2012
Merge replication and spids left behind
I posted this message under the comp.databases.ms-sqlserver group and
someone mentioned I should post it here:
We are using Merge replication with clients from remote offices (SQL
2000, sp3). Recently, I have had a problem with users who are
replicating, and they shut down their laptops. The connection never
dies, and I end up with major blocking issues related to the
"orphaned" spid. The tables that are blocked are used to filter data
on each client. Since the orphaned spid is blocking, backups will run
forever, and have to be killed, and a SQL management job that
inserts/updates data in these tables has to be killed.
If I kill the spid, it shows a rollback at 0% and the status never
changes. The user has disconnected, and there is really nothing to
roll back. How can I get rid of this spid with out restarting SQL
server, or rebooting my server?
Any help would be greatly appreciated.
Thanks,
Amy M
I wish I could help you Amy. I have run into similar problems like this (but
not with replication), and I would have to power off my server to fix it. I
was unable to shut down the server using the shutdown command.
I suggest you open a support incident with PSS on this one.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Amy M" <amarshall@.rhtc.net> wrote in message
news:119d3885.0408120229.3e585a78@.posting.google.c om...
> I posted this message under the comp.databases.ms-sqlserver group and
> someone mentioned I should post it here:
> We are using Merge replication with clients from remote offices (SQL
> 2000, sp3). Recently, I have had a problem with users who are
> replicating, and they shut down their laptops. The connection never
> dies, and I end up with major blocking issues related to the
> "orphaned" spid. The tables that are blocked are used to filter data
> on each client. Since the orphaned spid is blocking, backups will run
> forever, and have to be killed, and a SQL management job that
> inserts/updates data in these tables has to be killed.
> If I kill the spid, it shows a rollback at 0% and the status never
> changes. The user has disconnected, and there is really nothing to
> roll back. How can I get rid of this spid with out restarting SQL
> server, or rebooting my server?
> Any help would be greatly appreciated.
> Thanks,
> Amy M
someone mentioned I should post it here:
We are using Merge replication with clients from remote offices (SQL
2000, sp3). Recently, I have had a problem with users who are
replicating, and they shut down their laptops. The connection never
dies, and I end up with major blocking issues related to the
"orphaned" spid. The tables that are blocked are used to filter data
on each client. Since the orphaned spid is blocking, backups will run
forever, and have to be killed, and a SQL management job that
inserts/updates data in these tables has to be killed.
If I kill the spid, it shows a rollback at 0% and the status never
changes. The user has disconnected, and there is really nothing to
roll back. How can I get rid of this spid with out restarting SQL
server, or rebooting my server?
Any help would be greatly appreciated.
Thanks,
Amy M
I wish I could help you Amy. I have run into similar problems like this (but
not with replication), and I would have to power off my server to fix it. I
was unable to shut down the server using the shutdown command.
I suggest you open a support incident with PSS on this one.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Amy M" <amarshall@.rhtc.net> wrote in message
news:119d3885.0408120229.3e585a78@.posting.google.c om...
> I posted this message under the comp.databases.ms-sqlserver group and
> someone mentioned I should post it here:
> We are using Merge replication with clients from remote offices (SQL
> 2000, sp3). Recently, I have had a problem with users who are
> replicating, and they shut down their laptops. The connection never
> dies, and I end up with major blocking issues related to the
> "orphaned" spid. The tables that are blocked are used to filter data
> on each client. Since the orphaned spid is blocking, backups will run
> forever, and have to be killed, and a SQL management job that
> inserts/updates data in these tables has to be killed.
> If I kill the spid, it shows a rollback at 0% and the status never
> changes. The user has disconnected, and there is really nothing to
> roll back. How can I get rid of this spid with out restarting SQL
> server, or rebooting my server?
> Any help would be greatly appreciated.
> Thanks,
> Amy M
Monday, February 20, 2012
Merge replication and Clustered Indexes
Group,
I am getting the following error during replication of Database to a client:
The schema script 'Statutes_6.dri' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
Invalid locale ID was specified. Please verify that the locale ID is correct and corresponding language resource has been installed. (Source: MSSQLServer, Error number: 7696)
Get help: http://help/7696
Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. (Source: MSSQLServer, Error number: 319)
The database is relatively small, only about 5 tables but there is a clustered Full-text Index.
Any ideas?
Thanks,
Frank
Frank,
Can you figure out which statement in Statutes_6.dri is causing the error? We have some known issue of Full text index when invalid LCID is used. (You can find the problemetic statement by running profiler trace, or just open up Statutes_6.dri and try to execute statements in that file one by one, of course, some other snapshot files may need to be run so proper required schemas are present at subscriber db).
Also can you provide more info about your environment, like version of SQL Server (2005, rtm, or sp1?), same collation settings at publisher and subscriber db/table?
Thanks,
Zhiqiang Feng
Subscribe to:
Posts (Atom)