Srm The Remote Server Returned An Error (503)

Posted on
After installing a Windows update on a Windows 2008 R2 Server with both vCenter Server and Site Recovery Manager(SRM) installed on the same server, you experience these symptoms:
  1. Srm The Remote Server Returned An Error (503) Error
  2. Srm The Remote Server Returned An Error (503) Windows 10
Server
  1. The remote server returned an error: (503) Server Unavailable I would assume both are related and likely something with SSO. Post vCenter installation on each vCenter server, at the vCenter level I added the AD 'Domain Admins' group with full permissions and then successfully logged in and built the cluster with that credential set.
  2. Exception Details: System.Net.WebException: The remote server returned an error: (503) Server Unavailable. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
  3. The remote server returned an error: (503) Server Unavailable In the vmware-dr-.log file, you see panic events similar to: Panic: Timed out while waiting for 'DrReplicationProviderInterface' (300 seconds).

The remote server returned an error: (503) Server Unavailable. Version 9 Workflow Forms. Updated May 16, 2016. Subscribe Subscribed. Flower, deco. Asked on November 2, 2015 hi all.

  • You cannot log in to SRM using the vSphere client plug-in.
  • You see this error in the vSphere Client:
    Lost connection to SRM Server 10.10.10.12:8095
    The server '10.10.10.12' could not interpret the client's request. (The remote server returned an error: (503) Server Unavailable.)
    Connecting ..

  • The SRM vmware-dr.log file contains an error similar to:
    YYYY-MM-DDT09:1:16:16.425-05:00 [06012 warning 'LocalVC'] Failed to connect: (vim.fault.InvalidLogin) {
    --> dynamicType = <unset>,
    --> faultCause = (vmodl.MethodFault) null,
    --> msg = 'Cannot complete login due to an incorrect user name or password.'

    Note: For more information, see Location of Site Recovery Manager log files (1021802).
Srm the remote server returned an error (503) errorProblems encountered with Dynamics GP Workflow meant that I had to rebuild the product and in the end uninstalling and then reinstalling. The problem with the rebuild or uninstall of the product was that we receive the error:
Srm the remote server returned an error (503) windows 10
“The remote server returned an error (503) server unavailable”.
To get round this I manually uninstalled the product however I received the same issue when I began to install it again.

Srm The Remote Server Returned An Error (503) Error

Windows

Srm The Remote Server Returned An Error (503) Windows 10

Srm The Remote Server Returned An Error (503)Cause
The issue was down to a registry entry that was point to a different Security Admin Service.
HKLMSOFTWAREMicrosoftBusiness SolutionsWorkflow for Dynamics GP1033SETUP
Resolution
Manually removed Dynamics GP workflow and cleaning up the registry especially removing the above key
Manually removing Dynamics GP Workflow
1. Verify the Dynamics GP Workflow 10.0 record in the WSInstallStatus table is removed by running the follow SQL command in SQL Management Studio:
select * from DYNAMICS.WSInstallStatus where InstallStep = ‘350DF9B1-F1A1-4859-BBD3-776021116F69’

2. Search the Windows Registry on the server to make sure there isn't any mention of 'Workflow for Microsoft Dynamics GP', 'Workflow for Microsoft Dynamics GP 10.0' or 'Workflow'. Also remove the registry key:

HKLMSOFTWAREMicrosoftBusiness SolutionsWorkflow for Dynamics GP1033SETUP
IMPORTANT: Please ensure that you do not remove reference to other products (sharepoint and office) who may be reference the word Workflow. The blog author can not be held responsible for any damage caused by editing the registry directly.

3. If the Dynamics GP Workflow 10.0 site is still available, please run these command from the sharepoint program filder and verify they are successful:
• stsadm -o deactivatefeature -name DynamicsApproval -url -force
• stsadm -o deactivatefeature -name DynamicsWorkflowForms -url -force
• stsadm -o deactivatefeature -name DynamicsWorkflow -url -force
• stsadm -o uninstallfeature -name DynamicsApproval -force
• stsadm -o uninstallfeature -name DynamicsWorkflowForms -force
• stsadm -o uninstallfeature -name DynamicsWorkflow -force

4. Remove the web application through SharePoint that Dynamics GP Workflow 10.0 was installed onto, marking the option to remove the web site in IIS Manager and the content database in SQL Server. Run an IISRESET to complete the changes.

Dynamics GP Workflow New Install
1. Create a new web application in SharePoint again to install Dynamics GP Workflow onto. No need to create a site collection as the Workflow install will create the relevant /sites/DynamicsGPWorkflow site collection.

2. Perform new Dynamics GP Workflow install again