Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replication

Status
Not open for further replies.

jgoodman00

Programmer
Jan 23, 2001
1,510
I am trying to setup replication for our SQL 2000 db.

When I goto the first part of setup (Configuring Replication), I am asked to select a Distributor. I select this & I am then given the following error: "SQL Server Agent on 'SERVER1' currently uses the system account, which causes replication between servers to fail. In the following dialog box, specify another account for the Service Startup Account." I then tried providing a different login name/password combination for the Service startup account fields. I then get the message: "One or more of the changes you have made will not take effect until SQL Server Agent is restarted. Do you want to stop & restart SQL Server Agent now?" I then select Yes, & get the following message: "The SQL Enterprise Manager does not have sufficient permissions to verify the SQL Server Agent start-up account. Are you sure the new SQL Server Agent start-up account is valid?" Again I answer yes to this. I then get an error message stating: "The new service startup account name you have supplied is invalid or does not exist."

No matter what login I provide, it can seemingly never start-up correctly.

Are the first three messages I receive normal?
If so, have I answered them correctly?
Are they any alternatives?

Any other suggestions? James Goodman
 
Sounds to me like your SQL server agent service is starting up with an account that doesnt have the correct priveleges. Go to your services and look what user id it is using to logon.
Change to a domain admin account and see if this makes any difference.

 
The server which hosts SQL Server was recently converted to a domain, & it has since been removed. I think this problem might be related to this procedure, but I am not certain. James Goodman
 
I have now solved this problem. Under the username/password combination, I was merely entering a username, rather than fully qualifying it (e.g. SERVERNAME\USERNAME)

Simply Really!! :) James Goodman
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top