SRM Service, He's dead Jim.

SRM service, He's dead Jim.

Ever had your SRM server randomly through an error like this?

The server 'server.domain' could not interpret the client's request (the remove server returned and error: (503) Server Unavailable.)

Well I might just have a fix for ya!

This was a pretty simple one. Cracked open the logs (C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\vmware-dr-###) and saw this gem:

DBManager error: Could not initialize Vdb connection: ODBC error: (08001) - [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].

In this case, the issue was that the SQL server was dead due to an expired password but this message in the logs could point to SQL being down for any reason or being unreachable (if say you had a remote SQL server instead of a local one). Always remember to crack open those logs!

**********************************************Disclaimer**********************************************

This blog is in no way sponsored, supported or endorsed by VMware. Any configuration or environmental changes are to be made at your own risk. Casey, VMware, and any other company and/or persons mentioned in this blog take no responsibility for anything.