Prev: Merge Replication Setup Issue
Next: SQL Agent terminates, then replication can't restart.
From: John Luo on 1 Jun 2007 10:58
I got the following error:

The suscription could not be created.
Verify that a valid username and password were provided

Additional Infomation:
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 whitin retention period, or because of one of the
replicas being restored to a backup older than retention period, or becauseof
the publisher performing more aggressive cleanup on articles of type
download-only and articles with partion_option =3. (merger replication
Provider)

Publisher SQL 2005 STD SP1
Subscriber: SQL Express SP2

I checked there is no partion_option =3
Every subscriber is synced.
Ran exec sys.sp_mergemetadataretentioncleanup. The problem is not fixed.
Thank you for help,
John
From: Peter Yang [MSFT] on 3 Jun 2007 22:59
Hello John,

To understand the issue better, I'd like to know the following information:

1. What is the Retention Period?
2. Datatime of last successful synchronization of this Subscriber.
3. Did by any chance we restored Subscriber DB? Was Publisher DB restored
from backup?
4. What is the -ExchangeType of Merge Agent? Is it download-only?
5. Did you try to re-initialize the subscribers to test?

If the issue persists, you may want to try the following steps to
troubleshoot the issue


1. Tempoarily remove/disable the cleanup SP job.
2. Rebuild indexes on Meta Data tables so that synchronization & cleanup is
fast.

/*********************************/
DBCC DBREINDEX ('MSmerge_contents')
DBCC DBREINDEX ('MSmerge_genhistory')
DBCC DBREINDEX ('MSmerge_tombstone')
/*********************************/

3. Since Merge Agent will clean the meta data tables it will keep the size
of these tables will be within limit.
4. Reinitialize Subscriber.

As I know, there is a known issue that if an existing subscriber to a
publication recreates their subscription to a database, they are able to
perform the initial snapshot application and synchronization, but
subsequent replications may fail due to some metadata cleanup issues.

To find out the root cause of this issue we may need to analyze memory
dumps, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. I recommend that you open a Support incident with
Microsoft Product Support Services so that a dedicated Support Professional
can assist with this case. If you need any help in this regard, please let
me know.

For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 | 
Pages: 1
Prev: Merge Replication Setup Issue
Next: SQL Agent terminates, then replication can't restart.