asked on

SQL Mirroring

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, https://www.experts-exchange.com/questions/22896060/Trying-to-mirror-database-sql-server-2005-port-blocked.html?sfQueryTermInfo=1+1418+2005+cannot+doe+error+exist+mirror+reach+sql, 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?

ASKER CERTIFIED SOLUTION

Jim P.

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ncalcaterra

ASKER

We created a domain user and gave that user admin rights on the SQL server through AD. When trying to change the SQL services to run under this user, the second server throws up the second 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.) when trying to restart the SQL service.

The only way the SQL service can be restarted is to change the account user back to the local admin (non-domain) user.

Jim P.

Server2 is not a member of the domain? If not then there is no really good way to do this.

>> user admin rights on the SQL server through AD...

Go to the Computer Management console (Start --> Run --> compmgmt.msc) on the SQL Server. Drill down Computer Management --> Local Users and Groups --> Groups and select the Administrators Group. Add or verify the MyDomain\MyDBAdmin user id is in there.

Then drill down to the Services and Applications --> Services and scroll down to SQL Server (MSSQLSERVER). Change the Log On and password as shown, then restart the services. Repeat for the other services.
SQL-Server-Service-Logon.jpg

ncalcaterra

ASKER

Both SQL servers are on the same domain (mka.compute-1.internal). The MKA domainu user, mossadmin, was given Administrative rights in AD to both of the servers. Therefore, it should not be necessary to add the user to the local administrators group on each of the machines.
I can logon to both of the sql machines with the admin user, mossadmin, and gain full rights to all folders, etc. When I try to change the user the SQL service runs under (just as your pic shows), it allows me to hit OK and gives me a prompt to reset the service.
But when I click "Re-start", it then gives the above error.

Jim P.

Try going into the SQL Management Studio, and adding the user mossadmin user from the domain to securtiy and make him a SysAdmin user.

Then reset the services.

ncalcaterra

ASKER

The service needed to be run under a domain account with local admin rights. The experienced problem was with the instance (server), not the methodology.