Snapshot agent: The process could not connect to Distributor 'SERVER1'

[Michael]

I have used Enterprise Manager to configure replication on SERVER1.
SERVER1 is the Distributor and the Publisher. SERVER1 is a SQL Server
2000 that runs in mixed mode (SQL and Windows Authentication). The
SQL Server and SQL Server Agent startup accounts are the same which is
also a local user account that has administrative privileges.

I am completely stumped why I am having these permissions issues when
everything is being done on the local machine.

Any advice would be greatly appreciated.

Thank you.

[Paul Ibison]

This may be the case if the server has been renamed.
Try:
Use Master
go
Select @@Servername

This should return your current server name but if it
returns NULL then try:
Use Master
go
Sp_DropServer 'Server1'
GO
Use Master
go
Sp_Addserver 'Server1', 'local'
GO
Stop and Start SQL Services

If this works or isn't the solution, please post back to
let me know.
Regards,
Paul Ibison

[Michael Crofut]

Paul,

Thank you for your advice.

Use Master
go
Select @@Servername

returns SERVER1 (the current server name).

Any other advice is greatly appreciated.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Hilary Cotter]

on your publisher go to Tools - Replication - configure Publishers,
Distributors, and Subscribers, click on your subscribers tab, then click on
the browse button to the right of your server name. Ensure you are using the
Impersonate SQL Server agent option on your publisher.

"Michael" <mi...@fivestardvd.com> wrote in message
news:433966d7.04021...@posting.google.com...

[Michael Crofut]

Hillary,

Thank you for the advice.

The Publisher and Distributor are both on SERVER1. I can't even publish
a Snapshot for the Subscriber. The message displayed in the Snapshot
Agent History is 'The process could not connect to Distributor
'SERVER1''.

Any further advice or tips are greatly appreciated.

Michael Crofut
Web Developer

[Shirley Kelly [MS]]

Hi Mike,

Here's another suggestion related to Paul's. Connect to Server1 with Query
Analyzer and run "sp_helpserver". You should see Server1 listed with ID =
0. If the name is correct, but the ID is not equal to 0, you should use
sp_dropserver and sp_addserver to correct the problem. The change won't
take effect until the SQL Server service is restarted.

Regards,
Shirley
SQL Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

[Michael Crofut]

Shirley,

Thank you for your advice.

The ID for SERVER1 is 0 when executing the sp_helpserver stored proc.

I appreciate everyone's help. I finally was able to successfully
configure transactional replication yesterday evening. It was not quite
the solution I was hoping to implement, but it is working none the less
:) I ended up joining SERVER1 to the Windows domain (single domain
controller environment). Added the administrator account as a Windows
user SQL login and gave it access to the necessary databases. Then I
made that domain account the startup account for the SQL Server Agent,
and voila, no more permissions issue with connecting to the Distributor
or server upon running the Snapshot Agent or Log Reader.

Thank you all again for your advice.