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.
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.