SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Transactional replication fails with no meaningful error message


Transactional replication fails with no meaningful error message

Author
Message
Roust_m
Roust_m
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3486 Visits: 1981
Hi,

I am trying to setup replication between two clustered instances belonging to the same 3 node cluster. The distributor is a separate instance from publisher and subscriber.

When I re-initialise a publication I get this error message:
The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. The step failed.

Neither job history nor SQL Server logs provide any other meaningful messages.

When I try to run the snapshot from command prompt it just works fine:
"C:\Program Files\Microsoft SQL Server\100\COM\SNAPSHOT.EXE" -Publisher [sqlcluster1\publisher] -PublisherDB [MyDB] -Distributor [sqlcluster2\distributor] -Publication [MyPublication] -DistributorSecurityMode 1

Log reader and distributor agent fail with the same generic message.

SQL Server agent account is a local admin on each cluster node and a member of sysadmin role on each instance.

I am running SQL Server 2008R2 SP2.

Any ideas?

Thanks.



Andrew G
Andrew G
Hall of Fame
Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)

Group: General Forum Members
Points: 3965 Visits: 2279
Did you check replication monitor? Seems like you did but didnt specifically mention it.
That or
select * from distribution.dbo.msrepl_errors order by time desc



Also regarding permissions, is the service account different for each instance? The snapshot should be in a full unc path (\\server\drive\) accessible by the subscriber's service account.
Roust_m
Roust_m
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3486 Visits: 1981
Yep, I did check the replication monitor. And this query returns errors which happened two days ago and had been fixed.

Amazingly, the snapshot agent works fine when run from command prompt using the same service account.

All instances are using the same service account. The snapshot folder looks like this:
\\SQLCluster8\SQLRepl



WolfgangE
WolfgangE
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1251 Visits: 798
Roust_m (6/20/2013)
The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.


Locate the SQL-Job in management studio (not within the replication monitor) belonging to the snapshot agent. Have a look at the history of this sql job. There you mostly find the mentioned "previous step" with some (more or less) useful error messages.
Roust_m
Roust_m
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3486 Visits: 1981
WolfgangE (6/22/2013)
Roust_m (6/20/2013)
The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.


Locate the SQL-Job in management studio (not within the replication monitor) belonging to the snapshot agent. Have a look at the history of this sql job. There you mostly find the mentioned "previous step" with some (more or less) useful error messages.



Did this already, no useful message there.



Roust_m
Roust_m
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3486 Visits: 1981
This turned out to be the problem:
http://connect.microsoft.com/SQLServer/feedback/details/273892/replication-agents-hang-when-a-host-has-a-large-number-of-agents-running-on-it

Just migrated to the new cluster, did not change the replication architecture. Everything worked on the old one.



Andrew G
Andrew G
Hall of Fame
Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)

Group: General Forum Members
Points: 3965 Visits: 2279
Interesting, so it's a load issue with the distributor? Did you change to a pull subscription or update the jobs to use cmdexec?
free_mascot
free_mascot
SSCertifiable
SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)SSCertifiable (7.3K reputation)

Group: General Forum Members
Points: 7285 Visits: 2250
Try to capture error through profile.

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Roust_m
Roust_m
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3486 Visits: 1981
Andrew G (6/26/2013)
Interesting, so it's a load issue with the distributor? Did you change to a pull subscription or update the jobs to use cmdexec?


I did cmdexec. Very weird, as our replication is not that big.



Roust_m
Roust_m
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3486 Visits: 1981
free_mascot (6/26/2013)
Try to capture error through profile.


Which profile?



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search