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

Aug 16, 2018 The remote server returned an error: (503) Server Unavailable. Some parts of the Admin Portal Split from this thread. Session times out on Firefox, and I get the Error 503 as described in the OP using Chrome.

Problems 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:

Sep 09, 2017 The remote server returned an error: (403) Forbidden. Exception using Google.GData.Apps: The remote server returned an error: (503) Server Unavailable c# webClient (503) Server Unavailable. Nov 14, 2017 Connecting to SRM server fails with the error: The remote server returned an error: (503) Server Unavailable (2012112) Symptoms 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.

To get round this I manually uninstalled the product however I received the same issue when I began to install it again.
Cause
The issue was down to a registry entry that was point to a different Security Admin Service.
HKLMSOFTWAREMicrosoftBusiness SolutionsWorkflow for Dynamics GP1033SETUP

Srm The Remote Server Returned An Error (503) Error

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.

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

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
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:

• 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).