Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / February 2006

Tip: Looking for answers? Try searching our database.

Merge agent fails due to deadlock

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
yong - 27 Feb 2006 14:41 GMT
Hi:

 I met a problem this morning. the merge replication agen stopped, the
error message shows:

      The process could not enumerate changes at the 'Publisher'.
      (Source: Merge Replication Provider (Agent); Error number: -2147200999)
     
--------------------------------------------------------------------------------------
      Transaction (Process ID 79) was deadlocked on lock resources with
another process and has been chosen as the deadlock victim. Rerun the
transaction.
(Source: XXXXXX (Data source); Error number: 1205)
     
--------------------------------------------------------------------------------
     The process was successfully stopped.
     (Source: Merge Replication Provider (Agent); Error number: -2147200999)

  I never met this issue before, so please help
     1) What may cause this issue?
     2) How I could identify which process cause the deadlock issue?
     3) Is there any way to log more information to identify what resource
is deadlock, and by who.

  Thanks

                                        Yong
Paul Ibison - 27 Feb 2006 14:51 GMT
Yong,
have a look at enabling traceflags 1204, 1205, 3605 to get more info. Don't
forget to turn off afterwards. Alternatively if you have sql server 2005,
the profiler shows the deadlock tree graphically.
  Cheers,
         Paul Ibison SQL Server MVP, www.replicationanswers.com
           (recommended sql server 2000 replication book:
           http://www.nwsu.com/0974973602p.html)
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.