I have been receiving the following errors from time to
time during my nightly processing. At this time we
replicate a large amount of commands. The funny thing is
after these errors occur once, the next run is successful.
General network error. Check your network documentation.
The error code is 11.
immediately followed by:
Communication link failure with an error code 08S01.
I have increased my querytimeout to 900 from 300 in my
distribution agent profile, based on a post I read, and no
luck.
We run the same process in our another environment without
any issues. The only difference in this environment is
that it is on clustered hardware.
Any advice where to look? How to troubleshoot?
This means your network has hicupped. QueryTimeout set the timeout for
internal queries it has no effect on your network and won't help to reduce
this error. You have to contact your network admin to help resolve this
error.
"Kartik" <anonymous@.discussions.microsoft.com> wrote in message
news:1625201c41bec$c2624b30$a601280a@.phx.gbl...
> I have been receiving the following errors from time to
> time during my nightly processing. At this time we
> replicate a large amount of commands. The funny thing is
> after these errors occur once, the next run is successful.
> General network error. Check your network documentation.
> The error code is 11.
> immediately followed by:
> Communication link failure with an error code 08S01.
> I have increased my querytimeout to 900 from 300 in my
> distribution agent profile, based on a post I read, and no
> luck.
> We run the same process in our another environment without
> any issues. The only difference in this environment is
> that it is on clustered hardware.
> Any advice where to look? How to troubleshoot?
>
Showing posts with label receiving. Show all posts
Showing posts with label receiving. Show all posts
Friday, February 24, 2012
Common Generation Watermark error for Merge Replication
Hello,
We have a sqlexpress subscriber that is receiving the error below. SQL Server 2005
We have tried:
Generate new snapshot.
Reinitialize the subscription.
Dropped the subscription.
Reboot the web server box.
Reboot the sql server box.
Yet we still get the errors for these specific subscribers. Any ideas?
Error in replication monitor....
Error messages:
The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363
The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800
Can you offer more details on how your merge topology is set up? How are the machines layed out and what version of SQL Server 2005 is on each, RTM or SP1? I am also interested in the publication, article, and subscription settings. Perhaps you could post the publication and subscription scripts. Any other info you can offer on repro steps would be helpful.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Did you manage to resolve this issue in the end? I'm getting the same error periodically here, so I'd be interested to know if you managed to get it fixed.
Cheers
Nick Hoggard
|||The same problems occurs in my situation. 9 identical notebooks, each of them synchronizing using filters with SUSER_SNAME() rule. 2 of them stops with the same message. Have no idea what to do.
|||
Same problem here!
Some subscriptions fail with this error.
I really need a way to resolve this at the server as the subscribers are in the field.
Some more Info:
We have about 200 subscriptions and at the moment this problem appears at two of them.
At the client the error is 29006, which is not helping.
|||Unfortunately these issues are very very difficult to debug on a forum, I highly suggest opening a support case so you can have an engineer dig deeper into the problem.|||Did anything ever get resolved for this? We are having same problem.
thx,
jg
|||Can you describe your problem scenario or the sequence of events that have led you to this failure please?|||I am receiving the same error. I have pretty much the same architecture in place. The error seems to center around the Upload changes first.|||Hi all,found this one in Microsoft site.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=256575&wa=wsignin1.0
Thank you.|||
Do these forums ever get checked? I experienced a similar problem, if not the same problem.
I have a publication that includes Views, SPs, and Functions only. The publication was running successfully on a SQL Express SP2 subscriber, but failed with the error message stated previously in this topic. I had to mark the subscriber as needing to reinitialize and then the publication got passed the error. No changes were made to the articles or publication to cause the error.
Thanks in advance,
Graham
|||As mentioned above, please create a case with Customer Support so you cna have an engineer debug your issue, especially if this is blocking or hindering your production system.
Common Generation Watermark error for Merge Replication
Hello,
We have a sqlexpress subscriber that is receiving the error below. SQL Server 2005
We have tried:
Generate new snapshot.
Reinitialize the subscription.
Dropped the subscription.
Reboot the web server box.
Reboot the sql server box.
Yet we still get the errors for these specific subscribers. Any ideas?
Error in replication monitor....
Error messages:
The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363
The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800
Can you offer more details on how your merge topology is set up? How are the machines layed out and what version of SQL Server 2005 is on each, RTM or SP1? I am also interested in the publication, article, and subscription settings. Perhaps you could post the publication and subscription scripts. Any other info you can offer on repro steps would be helpful.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Did you manage to resolve this issue in the end? I'm getting the same error periodically here, so I'd be interested to know if you managed to get it fixed.
Cheers
Nick Hoggard
|||The same problems occurs in my situation. 9 identical notebooks, each of them synchronizing using filters with SUSER_SNAME() rule. 2 of them stops with the same message. Have no idea what to do.
|||
Same problem here!
Some subscriptions fail with this error.
I really need a way to resolve this at the server as the subscribers are in the field.
Some more Info:
We have about 200 subscriptions and at the moment this problem appears at two of them.
At the client the error is 29006, which is not helping.
|||Unfortunately these issues are very very difficult to debug on a forum, I highly suggest opening a support case so you can have an engineer dig deeper into the problem.|||Did anything ever get resolved for this? We are having same problem.
thx,
jg
|||Can you describe your problem scenario or the sequence of events that have led you to this failure please?|||I am receiving the same error. I have pretty much the same architecture in place. The error seems to center around the Upload changes first.|||Hi all,found this one in Microsoft site.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=256575&wa=wsignin1.0
Thank you.|||
Do these forums ever get checked? I experienced a similar problem, if not the same problem.
I have a publication that includes Views, SPs, and Functions only. The publication was running successfully on a SQL Express SP2 subscriber, but failed with the error message stated previously in this topic. I had to mark the subscriber as needing to reinitialize and then the publication got passed the error. No changes were made to the articles or publication to cause the error.
Thanks in advance,
Graham
|||As mentioned above, please create a case with Customer Support so you cna have an engineer debug your issue, especially if this is blocking or hindering your production system.
Common Generation Watermark error for Merge Replication
Hello,
We have a sqlexpress subscriber that is receiving the error below. SQL Server 2005
We have tried:
- Generate new snapshot. Reinitialize the subscription. Dropped the subscription. Reboot the web server box. Reboot the sql server box.
Yet we still get the errors for these specific subscribers. Any ideas?
Error in replication monitor....
Error messages:
The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363
The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800
Can you offer more details on how your merge topology is set up? How are the machines layed out and what version of SQL Server 2005 is on each, RTM or SP1? I am also interested in the publication, article, and subscription settings. Perhaps you could post the publication and subscription scripts. Any other info you can offer on repro steps would be helpful.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Did you manage to resolve this issue in the end? I'm getting the same error periodically here, so I'd be interested to know if you managed to get it fixed.
Cheers
Nick Hoggard
|||The same problems occurs in my situation. 9 identical notebooks, each of them synchronizing using filters with SUSER_SNAME() rule. 2 of them stops with the same message. Have no idea what to do.
|||Same problem here!
Some subscriptions fail with this error.
I really need a way to resolve this at the server as the subscribers are in the field.
Some more Info:
We have about 200 subscriptions and at the moment this problem appears at two of them.
At the client the error is 29006, which is not helping.
|||Unfortunately these issues are very very difficult to debug on a forum, I highly suggest opening a support case so you can have an engineer dig deeper into the problem.|||Did anything ever get resolved for this? We are having same problem.
thx,
jg
|||Can you describe your problem scenario or the sequence of events that have led you to this failure please?|||I am receiving the same error. I have pretty much the same architecture in place. The error seems to center around the Upload changes first.|||Hi all,found this one in Microsoft site.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=256575&wa=wsignin1.0
Thank you.
|||
Do these forums ever get checked? I experienced a similar problem, if not the same problem.
I have a publication that includes Views, SPs, and Functions only. The publication was running successfully on a SQL Express SP2 subscriber, but failed with the error message stated previously in this topic. I had to mark the subscriber as needing to reinitialize and then the publication got passed the error. No changes were made to the articles or publication to cause the error.
Thanks in advance,
Graham
|||As mentioned above, please create a case with Customer Support so you cna have an engineer debug your issue, especially if this is blocking or hindering your production system.
Common Generation Watermark error for Merge Replication
Hello,
We have a sqlexpress subscriber that is receiving the error below. SQL Server 2005
We have tried:
Generate new snapshot.
Reinitialize the subscription.
Dropped the subscription.
Reboot the web server box.
Reboot the sql server box.
Yet we still get the errors for these specific subscribers. Any ideas?
Error in replication monitor....
Error messages:
The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363
The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800
Can you offer more details on how your merge topology is set up? How are the machines layed out and what version of SQL Server 2005 is on each, RTM or SP1? I am also interested in the publication, article, and subscription settings. Perhaps you could post the publication and subscription scripts. Any other info you can offer on repro steps would be helpful.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Did you manage to resolve this issue in the end? I'm getting the same error periodically here, so I'd be interested to know if you managed to get it fixed.
Cheers
Nick Hoggard
|||The same problems occurs in my situation. 9 identical notebooks, each of them synchronizing using filters with SUSER_SNAME() rule. 2 of them stops with the same message. Have no idea what to do.
|||
Same problem here!
Some subscriptions fail with this error.
I really need a way to resolve this at the server as the subscribers are in the field.
Some more Info:
We have about 200 subscriptions and at the moment this problem appears at two of them.
At the client the error is 29006, which is not helping.
|||Unfortunately these issues are very very difficult to debug on a forum, I highly suggest opening a support case so you can have an engineer dig deeper into the problem.|||Did anything ever get resolved for this? We are having same problem.
thx,
jg
|||Can you describe your problem scenario or the sequence of events that have led you to this failure please?|||I am receiving the same error. I have pretty much the same architecture in place. The error seems to center around the Upload changes first.|||Hi all,found this one in Microsoft site.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=256575&wa=wsignin1.0
Thank you.|||
Do these forums ever get checked? I experienced a similar problem, if not the same problem.
I have a publication that includes Views, SPs, and Functions only. The publication was running successfully on a SQL Express SP2 subscriber, but failed with the error message stated previously in this topic. I had to mark the subscriber as needing to reinitialize and then the publication got passed the error. No changes were made to the articles or publication to cause the error.
Thanks in advance,
Graham
|||As mentioned above, please create a case with Customer Support so you cna have an engineer debug your issue, especially if this is blocking or hindering your production system.
Common Generation Watermark error for Merge Replication
Hello,
We have a sqlexpress subscriber that is receiving the error below. SQL Server 2005
We have tried:
Generate new snapshot.
Reinitialize the subscription.
Dropped the subscription.
Reboot the web server box.
Reboot the sql server box.
Yet we still get the errors for these specific subscribers. Any ideas?
Error in replication monitor....
Error messages:
The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363
The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800
Can you offer more details on how your merge topology is set up? How are the machines layed out and what version of SQL Server 2005 is on each, RTM or SP1? I am also interested in the publication, article, and subscription settings. Perhaps you could post the publication and subscription scripts. Any other info you can offer on repro steps would be helpful.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Did you manage to resolve this issue in the end? I'm getting the same error periodically here, so I'd be interested to know if you managed to get it fixed.
Cheers
Nick Hoggard
|||The same problems occurs in my situation. 9 identical notebooks, each of them synchronizing using filters with SUSER_SNAME() rule. 2 of them stops with the same message. Have no idea what to do.
|||
Same problem here!
Some subscriptions fail with this error.
I really need a way to resolve this at the server as the subscribers are in the field.
Some more Info:
We have about 200 subscriptions and at the moment this problem appears at two of them.
At the client the error is 29006, which is not helping.
|||Unfortunately these issues are very very difficult to debug on a forum, I highly suggest opening a support case so you can have an engineer dig deeper into the problem.|||Did anything ever get resolved for this? We are having same problem.
thx,
jg
|||Can you describe your problem scenario or the sequence of events that have led you to this failure please?|||I am receiving the same error. I have pretty much the same architecture in place. The error seems to center around the Upload changes first.|||Hi all,found this one in Microsoft site.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=256575&wa=wsignin1.0
Thank you.|||
Do these forums ever get checked? I experienced a similar problem, if not the same problem.
I have a publication that includes Views, SPs, and Functions only. The publication was running successfully on a SQL Express SP2 subscriber, but failed with the error message stated previously in this topic. I had to mark the subscriber as needing to reinitialize and then the publication got passed the error. No changes were made to the articles or publication to cause the error.
Thanks in advance,
Graham
|||As mentioned above, please create a case with Customer Support so you cna have an engineer debug your issue, especially if this is blocking or hindering your production system.
Common Generation Watermark error for Merge Replication
Hello,
We have a sqlexpress subscriber that is receiving the error below. SQL Server 2005
We have tried:
- Generate new snapshot. Reinitialize the subscription. Dropped the subscription. Reboot the web server box. Reboot the sql server box.
Yet we still get the errors for these specific subscribers. Any ideas?
Error in replication monitor....
Error messages:
The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363
The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800
Can you offer more details on how your merge topology is set up? How are the machines layed out and what version of SQL Server 2005 is on each, RTM or SP1? I am also interested in the publication, article, and subscription settings. Perhaps you could post the publication and subscription scripts. Any other info you can offer on repro steps would be helpful.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Did you manage to resolve this issue in the end? I'm getting the same error periodically here, so I'd be interested to know if you managed to get it fixed.
Cheers
Nick Hoggard
|||The same problems occurs in my situation. 9 identical notebooks, each of them synchronizing using filters with SUSER_SNAME() rule. 2 of them stops with the same message. Have no idea what to do.
|||Same problem here!
Some subscriptions fail with this error.
I really need a way to resolve this at the server as the subscribers are in the field.
Some more Info:
We have about 200 subscriptions and at the moment this problem appears at two of them.
At the client the error is 29006, which is not helping.
|||Unfortunately these issues are very very difficult to debug on a forum, I highly suggest opening a support case so you can have an engineer dig deeper into the problem.|||Did anything ever get resolved for this? We are having same problem.
thx,
jg
|||Can you describe your problem scenario or the sequence of events that have led you to this failure please?|||I am receiving the same error. I have pretty much the same architecture in place. The error seems to center around the Upload changes first.|||Hi all,found this one in Microsoft site.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=256575&wa=wsignin1.0
Thank you.
|||
Do these forums ever get checked? I experienced a similar problem, if not the same problem.
I have a publication that includes Views, SPs, and Functions only. The publication was running successfully on a SQL Express SP2 subscriber, but failed with the error message stated previously in this topic. I had to mark the subscriber as needing to reinitialize and then the publication got passed the error. No changes were made to the articles or publication to cause the error.
Thanks in advance,
Graham
|||As mentioned above, please create a case with Customer Support so you cna have an engineer debug your issue, especially if this is blocking or hindering your production system.
Common Generation Watermark error for Merge Replication
Hello,
We have a sqlexpress subscriber that is receiving the error below. SQL Server 2005
We have tried:
- Generate new snapshot. Reinitialize the subscription. Dropped the subscription. Reboot the web server box. Reboot the sql server box.
Yet we still get the errors for these specific subscribers. Any ideas?
Error in replication monitor....
Error messages:
The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363
The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800
Can you offer more details on how your merge topology is set up? How are the machines layed out and what version of SQL Server 2005 is on each, RTM or SP1? I am also interested in the publication, article, and subscription settings. Perhaps you could post the publication and subscription scripts. Any other info you can offer on repro steps would be helpful.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Did you manage to resolve this issue in the end? I'm getting the same error periodically here, so I'd be interested to know if you managed to get it fixed.
Cheers
Nick Hoggard
|||The same problems occurs in my situation. 9 identical notebooks, each of them synchronizing using filters with SUSER_SNAME() rule. 2 of them stops with the same message. Have no idea what to do.
|||Same problem here!
Some subscriptions fail with this error.
I really need a way to resolve this at the server as the subscribers are in the field.
Some more Info:
We have about 200 subscriptions and at the moment this problem appears at two of them.
At the client the error is 29006, which is not helping.
|||Unfortunately these issues are very very difficult to debug on a forum, I highly suggest opening a support case so you can have an engineer dig deeper into the problem.|||Did anything ever get resolved for this? We are having same problem.
thx,
jg
|||Can you describe your problem scenario or the sequence of events that have led you to this failure please?|||I am receiving the same error. I have pretty much the same architecture in place. The error seems to center around the Upload changes first.|||Hi all,found this one in Microsoft site.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=256575&wa=wsignin1.0
Thank you.
|||
Do these forums ever get checked? I experienced a similar problem, if not the same problem.
I have a publication that includes Views, SPs, and Functions only. The publication was running successfully on a SQL Express SP2 subscriber, but failed with the error message stated previously in this topic. I had to mark the subscriber as needing to reinitialize and then the publication got passed the error. No changes were made to the articles or publication to cause the error.
Thanks in advance,
Graham
|||As mentioned above, please create a case with Customer Support so you cna have an engineer debug your issue, especially if this is blocking or hindering your production system.
Subscribe to:
Posts (Atom)