TX replication issue (Network Steve Forum)

TX replication issue

Hello,

This morning I noticed that transactionalreplication distrubtion agent crashed on my SQL Server 2012 SE production. I was looking at the distribution history and I was seeing the below:

Messages:
The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. The step failed.

Executed as user: <username> . String or binary data would be truncated. [SQLSTATE 22001] (Error 8152). The step failed.

A replication agent encountered a fatal error and was shut down. A mini-dump has been generated at the following location:

C:\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps\ReplAgent20150713043222_0.mdmp

So I started the distribution agent and commands are getting replicated now. due to the volume of transaction it says unditribution commands 200000 and time to distribute based on past performance as 1:10:00

I am trying to look at the minicrash dump. However what could have caused this problem is a mystery for now as it has been running for the past 3 years without issue?

Expers I need your valuable inputs.

Thanks a ton.

July 13th, 2015 11:24am

The dump file says:

C:\Program Files\Microsoft SQL Server\110\COM\rdistcom.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 0

interestingly nothing has changed till date and not sure why this error.

Also is there a way to identify how long will it actually take for distribtuion agent to deliver commands to the subsciption ?

Free Windows Admin Tool Kit Click here and download it now

July 13th, 2015 11:32am

Hi SQLSPUser,

Firstly, to track the root cause of this issue , dump analysis is required. And it is recommended that you open a case on Microsoft Customer Support (http://support.microsoft.com/ ). There will be a technical support engineer assigned to analysis the dump files and give you a solution to this issue.

Secondly, according to my knowledge, we are not able to identify the exact time that Distribution Agent takes to deliver commands to the Subscriber. We can only estimate the time by using the sp_replmonitorsubscriptionpendingcmds stored procedure or the Undistributed Commands tab in Replication Monitor.

Reference:
https://msdn.microsoft.com/en-us/library/ms151740.aspx?f=255&MSPPError=-2147217396

Thanks,
Lydia Zhang

If you have any feedback on our support, please click here.

July 13th, 2015 10:55pm

This topic is archived. No further replies will be accepted.