Hi all,
Upon removing and re-adding replication from a production system at the weekend, we encountered the following error when executing sp_addpullsubscription_agent:
Msg 3930, Level 16, State 1, Procedure sp_grant_login_to_proxy, Line 70
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
Msg 3931, Level 16, State 1, Procedure sp_MSrepladdproxyaccount, Line 129
The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.
The specifics of our configuration are:
- SQL Server 2012, SP3
- Transactional replication
- Pull subscription
- Dedicated Distribution SQL Server
- Log Reader Agent and Distribution Agent to run as a dedicated domain user account which is a local Admin on the Distribution server and Subscriber server (which is where DISTRIB.EXE is running)
The only way we could get around this error was to create the pull subscription specifying that it runs under the SQL Server Agent account.
However, this is not our standard or preferred configuration. It is not how we run in other domains where everything is the same as this one where we've just experienced this new problem. And we successfully did the equivalent replication removal and re-creation work in those other domains the previous week.
We have installed SP3 of sql server 2012 since the last replication removal and re-creation in the affected domain. However, the same is true of the other domains where the error isn't prevalent.
Has anybody else experienced this please? Is it perhaps a bug manifested in very specific circumstances but something that can be worked around by changing the properties of the Distribution Agent job step in place?
Many thanks.
J