Share this PostAny Cox | Microsoft Premier Field Engineer We recently encounter the a problem where Replication Distribution Agent failed with error below while trying to replicate the “execution” of a stored procedure. Msg 0, Level 20, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be
Read More »
Share this PostProblem Customer observes high latency in SQL Server 2005 Merge replication. In sysprocesses you see that Merge agents are being blocked by another Merge agent & the blocker Merge agent SPID is sleeping with “AWAITING COMMAND”. Root Cause If you take output of “select open_transaction_count from sys.dm_exec_requests where session_id = <blocker SPID>” &
Read More »
Share this PostDoing Replication demonstrations on my laptop I’ll notice a Distribution Agent is not running. I’ll start the Agent and Refresh, but it still shows as Not Running. Looking at the Agent Details it appears it was running then stopped. Yet when I start synchronizing the status never changes and the DETAILS don’t update.
Read More »
Share this PostEric Lucht | Microsoft SQL Server Escalation Services Centralized troubleshooting refers to the ability to generate detailed Merge agent log files on both client and Web server (for Web Synchronization), and gather the log files into a central location on the publisher as part of the sync process, no matter where the reconciler
Read More »
Share this PostEric Lucht | Microsoft SQL Server Escalation Services Logging Options When the Merge subsystem is initialized, agent logging is automatically enabled using default values. The Agent will begin logging in the replmerg.log being created in the 100\COM (90\COM for SQL 2005) folder. This blog posting covers registry keys used to override the logging
Read More »