Friday, 26 August 2011

The remote server returned an error (503) server unavailable Dynamics GP Workflow

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:

“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. 

Cause
The issue was down to a registry entry that was point to a different Security Admin Service. 

HKLM\SOFTWARE\Microsoft\Business Solutions\Workflow for Dynamics GP\1033\SETUP\

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:


HKLM\SOFTWARE\Microsoft\Business Solutions\Workflow for Dynamics GP\1033\SETUP\

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


1 comment:

  1. That's a very interesting case, I would never know how to fix it. Well done! Everytime something goes wrong with my erp software, anegis consulting is always there to help.

    ReplyDelete