February 9, 2010 at 11:56 pm
Hi Friends,
We have a production server(SQL 2005) which has configured Snapshot Replication to run once in a week.There is an open transaction which is initiated by "NT Authority\System user" after very few seconds the server started, which is trying to execute a SP called "sp_MSget_last_transaction" against the Distribution database.
I have tried giving the "db_owner" permissions to the NT Authority\System user,but it did not work.
Last eve,we have restarted the server,luckily the open transaction closed.
But to my surprise,the same transaction is started with a different SPID exactly as above mentioned.
The transaction is still open,and repeatedly(once in a minute) trying to execute the SP and a login failure occurs and the error written to the Error log.
Due to this the error log unnecessarily growing.
Any ideas../ Suggestions..?
Thanks in advance.
~Dhayanithy
February 10, 2010 at 1:55 pm
Set up replication to run under same account as SQL server account, If you want to set up different account assign SA role to that Login, this should fix your problem.
February 11, 2010 at 2:35 am
Hi,
Thanks for the reply.
The replication related jobs(Snapshot & Copy) are owned by "SA" account already.
~Dhayanithy
May 28, 2010 at 11:31 am
I had a similar issue with the Mail Delivery service not sending emails and the Maintenance Cleanup task not deleting old BAK files on one of my servers. I noticed in the Application log that the NT Authority account kept failing for each of those jobs.
The solution was to go through the SQL Server Configuration Manager and on the properties of the SQL Server (MSSQLSERVER) service I changed the account from NT Authority to an account I created that had Local Admin rights on both the local server as well as the other servers it touched.
I hope that helps!
Edit: Please note - this will restart that service!!! So, prepare accordingly.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply