• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 721
  • Last Modified:

Dead Lock

Hi,

We have created the merge replication and we have some stored procedures and triggers in the database.

Application is developed in VB.NET.

There are 80 users working on our application system.

and merge replication is set to 1 minute.

we are getting dead lock error.

the error is as follows.

The process could not emuerate changes at the 'Publisher'.
(Source: Merge Replication proveider (Agent) ; Error number: - 2147200999)
-------------------------------------------------------------------------------------------------------------------------------------------
Transaction (Process ID 102) was deadlocked on lock resources with another process and has been chosen as deadlock victim. Rerun the transaction.
(Source: Merge Replication proveider (Agent) ; Error number: - 2147200900)
-------------------------------------------------------------------------------------------------------------------------------------------
The Process was successfully stopped.
(Source: Merge Replication proveider (Agent) ; Error number: - 2147200990)
-------------------------------------------------------------------------------------------------------------------------------------------

Please let me know how to handle this situations



0
simonrimmington
Asked:
simonrimmington
1 Solution
 
Einstine98Commented:
look at increasing the replication interval
0
 
simonrimmingtonAuthor Commented:
We are trying the same thing,
Please can you confirm what will be the best interval for Merge Replication.

Is there are any other way? to keep the transaction in QUE and after completion of Replication we can process que?

Thanks & Regards
G.S.S. Ravikanth
0
 
csachdevaCommented:
Hello,

run your agents so when the job step fails it loops back to the first job step.

This error is often transitory. If you have large numbers of subscribers you might want to limit concurrent
processing or perhaps schedule your merge agents as opposed to running them
simultaneously or continuously.

This is a generic , high-level error message simply indicating that the merge agent ran into a problem moving changes from the subscriber to the publisher. It can be caused by several different problems, and is not necessarily a bug. you could enable logging on the merge agent (-output c:\somefile.log -outputverboselevel 3). Alternatively, most of these merge errors are solved by simply restarting the merge agent.

regards,
Chetan Sachdeva
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now