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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Mirroring

Status
Not open for further replies.

ncalcaterra

Programmer
Nov 11, 2004
27
US
While attempting to mirror two sql servers without a witness server, the following error kept coming through right at the end:

The server network address "TCP://MOSSSQL-B.mka.compute-1.internal:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error:1418)

I checked that both endpoints were created and on/started. I can ping both servers from the other server. Both servers are running SQL Standard 2005 ver 9.0.3077. All servers are in Amazon's cloud and apart of the "local" domain: MKA (mka.compute-1.internal).

In trying to fix this issue, a forum, suggested to run the SQL processes under a domain admin account rather than the local admin account. The first server switched over fine, but the second server now gives this error:

Windows could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -2146885628.

1. Does the SQL server need to be run by a Domain admin for cloning to be successful?

2. What else should be done to get these two machines cloning successfully?
 
1) No. I am doing it with a regular domain user (albeit an admin on both boxes)

2) The biggest hang up people have is they forget to take the log backup in addition to a full backup and apply that to the target database. Error 1418 is a catch-all error. hopefully in 2008, it will get a little more descriptive.
 
1.) I user I was referring to was a domain user with admin rights on the local server, ie NOT the domain admin as I originally posted.

2.) After successfully running the SQL service under this user account on a new instance AND using a log backup as well as a full backup, everything worked.

Thanks for the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top