Sp_MSpub_adjust_identity

May 4, 2007

Twice in 2 days I have had a log_reader agent fail because of this proc. The error is "The process could not execute 'sp_MSpub_adjust_identity' on <Publisher Server Name>".



The publisher is SQL2000 SP4.

The distributor is SQL 2005 SP2 x64.

The subscriber is the same instance as the distributor, SQL 2005 SP4 x64.



Transactional Replication has been setup for more than a month with no problems, then this week 2 different log reader agents failed with the same error. I restarted the log readers and everything has been fine, so far. I have found very little useful information about this stored proc and nothing about why it would fail.





The full error message is:



Message
2007-05-04 00:48:34.928 Status: 0, code: 20011, text: 'The process could not execute 'sp_MSpub_adjust_identity' on '<Publisher Server Name>.'.
2007-05-04 00:48:34.928 The process could not execute 'sp_MSpub_adjust_identity' on '<Publisher Server Name>'.
2007-05-04 00:48:34.928 Status: 0, code: 7399, text: 'OLE DB provider 'SQLOLEDB' reported an error. '.



Any help would be appreciated.

View 8 Replies


ADVERTISEMENT

Agent Failure - Sp_MSpub_adjust_identity Error

Apr 25, 2007

Hi,

I am running transactional replication between a pair of SQL Server 2005 machines using a remote distributor. Occasionally the log reader agent fails with the error

"Replication-Replication Transaction-Log Reader Subsystem: agent * failed. The process could not execute 'sp_MSpub_adjust_identity' on '*'."

The agent starts back up again almost immediately on its own with seemingly no problems. I haven't been able to find any documentation on this error from Microsoft. Any ideas?

It is not a permissions issue as the log reader agent (and all of the other agents at that) are running under windows accounts with domain admin access for the domain that both the publisher and the distributor SQL Servers are on. (I know, I know, that's horrible. I've only been here a week and a half and I just found out about this today, so I didn't have anything to do with such a glaring security issue.) All of the SQL Servers involved with the replication are still granting sysadmin access to the windows administrators group.

View 1 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved