Distribution agent error when replicating data 1

[TonyOz26]

I have a SQL 2000 server that replicates a db to another server which works fine. I recently wanted this db to be replicaed to another server and have set it up the same way..
Snapshot publication being pushed from the one server to the others.
For some reason the process doesn't work for the new server.
I fails due to a distribution Agent Error
Error message: The process could not connect to subscriber "new server name"
Error Details: Login failed for user null. Reason Not associated with a tristed SQL server connection
(source "new server name" (data source) Error number 18452)

I have checked the accounts that created the publication is a sysadmin on the new server and that the mssqlserver service has the same account as the other sql servers.
Any ideas on what I am doing wrong?

 

[mrdenny]

When you pushed the subscription to the new machine what option did you select for the authentication? (Keep in mind that I'm trying to remember what the SQL 2000 screens look like.)

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[TonyOz26]

HI MrDenny
The SQL server is set up with "SQL server and Windows" Authentication
The Start up service account is a newtwork account with local admin rights.
Is this the info you are after?

 

[mrdenny]

When you setup replication and push a subscription there should be a screen that asks you what account you want the replication job to run under. What did you select for that screen?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[TonyOz26]

The problem is that I have come on-board half way through and been asked to get it working. The person that originally set it up as left.
I can get into the properties of the publication but I can't find the account it has been setup with.
How do you find out the account name?

 

[mrdenny]

I don't have replication running on SQL 2000, so I can't use the Enterprise Manager to see where the field is. We are using SQL 2005 for our replication.

When I look at the properties of the publication I have an Agent Security tab which tells me how that's all setup.

You may find that it's easier to remove the replication and reset it up from scratch. If you do this, don't forget to document everything for the next guy.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com