New publication error 3930

Question

Hello,

Im new to SQL world and im learning how to establish replication. I\ve searched alot for a solution but no use.

I've two boxes running W2K8 32bit and MS SQL 2008 R@ running on them, i\ve joined the machines to domain after the instalation of MS SQL and creating some testing Databases.

I've createed a domain accout for the SQL Server Agent and i gave it the right permissions in the local group policy (according to the tutorials, six policies), then i''ve created multiple domain accounts for replication purposes

I logon to SQL studio using a domain admin account that has sysadmin permission on sql server

When creating the publication and entering the snapshot and the log reader accounts i get the following error

TITLE: New Publication Wizard
------------------------------

SQL Server could not create publication 'test'.

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.
Changed database context to 'veronicas'.
SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 3930)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=3930&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

I can't even delete that publication to create a new one, it says something related to the old machine name and the local administrator, i've changed the name of the machine after the installation of sql the ran a small script to correct the name for  the sql server and everything ran fine, but not for replication.

I hope you'd help me.

Thank you!

---

MCITP: Server Administrator 2008, MCP

Answer 1

Hey i want to add smething, i've logged on to the server using the local admin account, then i've created the publication very successfully using the domain accounts for snapshot and log-reading, so what's the problem with the domain account?!

---

MCITP: Server Administrator 2008, MCP

Answer 2

Hi Mohamed Roushdy,

>> I've createed a domain accout for the SQL Server Agent and i gave it the right permissions in the local group policy

Regarding to your description, please verify the domain\account you added which is a member of Local Administrators group of the SQL Server.

>> SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 3930)

If you receive this error message, first make sure that the SQL Server Agent service is running. To do this, follow these steps:
1. Click Start, click Run, type Services.msc, and then click OK.
2. In the Services window, locate the SQL Server Agent service.
3. Make sure that the value of the Status column of the SQL Server Agent service is Running.
If the SQL Server Agent service is running, this problem occurs because the SQL Server Agent service cannot interpret the dot mark (.) that represents the local computer in the ObjectName
registry entry under the following registry subkey.

For a default instance, the registry subkey is as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\
For a named instance, the registry subkey is as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL$InstanceName\

>> i've logged on to the server using the local admin account, then i've created the publication very successfully using the domain accounts for snapshot and log-reading, so what's the problem with the domain account?!

Based on my test, SQL services were configured to run under local Administrator account. I was trying to execute sp_addpublication_snapshot by specifying the DOMAIN\Administrator account but I got the error. After configuring SQL services to run under DOMAIN\Administrator account and rebooting the server, that works.

Meanwhile this issue also might be appears to be an owner issue on the snapshot agent job.

If you create the snapshot agent without changing the job account, e.g. using the SQL Server Agent service account, please try to change publication snapshot agent job owner as below:

EXEC sp_changepublication_snapshot @publication='publication', @job_login='domain\account', @job_password='xxxxx'

Now you can be able to successfully assign a different job account to the snapshot agent.

---

Regards, Amber zhang