March 12, 2008 at 2:51 pm
Dear Concern,
I am using SQL Server 2000 and need to replicate heavy running databases to my secondary server which is at DRP location on 4MB WAN link.
I have configured Snapshot Replication and I am running the distributor where the publication is. I receive error in push subscription that
Subscriptions were created successfully at the following Subscribers:
PKKHIWS1007
SQL Server Enterprise Manager could not start the service 'SQLSERVERAGENT' on server 'PKKHIWS1003'.
5 - (Access is denied)
SQL Server Enterprise Manager could not start the Distribution Agent.
Error 14262: The specified @job_id ('00000000-0000-0000-0000-000000000000') does not exist.
I am unable to understand that why it is saying SQL Server agent not starting.
I have checked on SQL Server Service Manager it is running.
I will highly appreciate if your please help me out.
March 12, 2008 at 8:15 pm
When you are configuring replication, Enterprise Manager checks whether SQL Server Agent is running because it is used to run each of the replication agents.
The user who is running Enterprise Manager needs to have sufficient rights on the server to start services for this to work. I think that your user is not allowed to start the SQL Agent Service on your server.
You can test this by logging on to the server using your windows account and trying to start the SQL Agent Service.
You will need to arrange for someone with sufficient privileges to start the service AND ALSO to configure the service so that it starts whenever Windows starts.
Once this is done, you should be OK to create publications and subscriptions
March 12, 2008 at 8:54 pm
Hi,
Thanks for the reply.
After doing that now service is running. But i am receiving this error now.
Please help.
Subscriptions were created successfully at the following Subscribers:
PKKHIWS1007
SQL Server Enterprise Manager could not start the Distribution Agent.
Error 14262: The specified @job_id ('00000000-0000-0000-0000-000000000000') does not exist.
March 13, 2008 at 12:07 pm
After creating your publisher, related jobs are created. Check msdb..sysjobs and see whether or not the job exists.
If not, it may be renamed, removed, modified, ...
If you cannot restore it, you may have to reconfigure your replication.
March 13, 2008 at 4:20 pm
Hi,
All jobs are viewable there but it gives an error in job history.
What to do?
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
This error is in Subscription Job history.
March 13, 2008 at 4:38 pm
in the job properties, who owns the job.? If it is not sa or the service account, change the job owner to one of them
---------------------------------------------------------------------
March 13, 2008 at 5:47 pm
Hi,
I have selected at both side the option "Impersonate the SQL Server Agent Account on xxxxxxxx (trusted connection).
March 13, 2008 at 5:53 pm
The usual reason for the message
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
is because the server you are trying to connect to is configured to accept to accept "Windows Only" connections, not connections using SQL Server defined logins.
What is probably happening is that the replication agent is attempting to connect to the other server using a sql login. You will need to change the remote server so that it accepts "SQL Server and Windows" authentication. This is done using Enterprise Manager. Right click on the server name, select properties and then go to the Security tab.
March 13, 2008 at 6:00 pm
Hi,
I have checked in Security Tab my both servers are configured as SQL Server and Windows option.
March 13, 2008 at 6:03 pm
Has this setting changed recently ? For it to take affect, a restart of the SQL Server service is required
March 13, 2008 at 6:10 pm
No there is no change made now. It was configured before.
March 13, 2008 at 6:17 pm
Hi,
Let me define job history
Connecting to Subscriber 'PKKHIWS1007'
Connecting to Distributor 'PKKHIWS1003'
Login failed for user 'KUL-DC\PKKHIWS1007$'.
The process could not connect to Distributor 'PKKHIWS1003'. The step failed.
The job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).
Here I am unable to understand that i have logged in at both side with local administrator then why it is picking up the Domain (KUL-DC) it should be PKKHIWS1007\Administrator where PKKHIWS1007 is the name of subscription server.
March 13, 2008 at 6:23 pm
It is not you that is connecting to the remote server - it is SQL Server Agent. SQL Server Agent is running as account "localsystem" (you can see this if you select the properties of SQL Server Agent). The you will need to add the account "'KUL-DC\PKKHIWS1007$" to the remote server. Off the top of my head, I can't remember what privileges it needs but it will probably be something like dbo in the database you are replicating to
March 13, 2008 at 7:04 pm
After adding account the error changed.
Job history is as below
1. Connecting to Subscriber 'PKKHIWS1007'
2. Connecting to Distributor 'PKKHIWS1003'
3. Initializing
4. Category:OS
Source:
Number: 5
Message: Access is denied.
5. The process could not read file '\\PKKHIWS1003\E$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\PKKHIWS1003_Northwind_Northwind\20080313093517\CustomerCustomerDemo_1.sch' due to OS error 5. The step failed.
The job failed. The Job was invoked by User sa. The last step to run was step 1 (Run agent.).
March 13, 2008 at 7:13 pm
I have logged in with local administrator and has already set the same passwords.
I can open that folder through admin share in Windows explorer why SQL server is not getting that?
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply