'Clr Method Invocation Failed' error message when attempting to install Web Services for Microsoft Dynamics GP

From time to time we see the following .NET Framework error message when attempting to install Web Services for Microsoft Dynamics GP:

“Clr method invocation failed. / EC(31) HR(-2146232828) OP(16) / Unknown error 0x80131604 / Microsoft.Dynamics.GP.Deployment.UI::Microsoft.Dynamics.GP.WebServices.Deployment.UI.EntryPoint.Main()  [v4.0.30319]”

When we experience this error, we usually are required to install Web Services for Microsoft Dynamics GP using a script via the Command Prompt: Administrator window.

**NOTE: First, if you do not already have eConnect for Microsoft Dynamics GP installed on the server you’re attempting to install Web Services onto, manually install eConnect at the same version as your Microsoft Dynamics GP is currently on and the same version as you plan to install Web Services, otherwise the Web Services install via the script will fail.

The script to use to install Web Services manually is here (This example is for Web Services/Dynamics GP 2018) :

msiexec /i "C:\............\Microsoft_DynamicsGP18_WebServices_x64_en-us.msi" /qn+ /l*v C:\install.log SQLSERVER="SQLSERVERNAME" SERVICE_USER_DOMAIN="CONTOSO" SERVICE_USER_NAME="GPWSService" SERVICE_USER_PASSWORD="PASS123!" SECURITY_STORE="Sql" SQL_SECURITY_INSTANCE="SQLSERVERNAME" SQL_SECURITY_DATABASE="GPWSSECURITY" SQL_SECURITY_STORENAME="DynamicsGPWebServices"

Verify the path to the Microsoft_DynamicsGP18_WebServices_x64_en-us.msi file is correct.

Replace CONTOSO with the actual domain name, for the SERVICE_USER_DOMAIN value.

Replace GPWSService and PASS123! in the SERVICE_USER_NAME and SERVICE_USER_PASSWORD values, with the actual user ID and password of the account you want to have setup to run the 'Microsoft Dynamics GP Service Host' service, for Web Services.

Replace SQLSERVERNAME with the actual SQL Server instance name where the Dynamics GP databases exist for the SQLSERVER value and also for the SQL_SECURITY_INSTANCE value, if that is where you want the security store database for Web Services to be created.

Replace GPWSSECURITY with the name of the new or existing Web Services security store database you want to use/create, for the SQL_SECURITY_DATABASE value.

       **Note: The Web Services security store database need not exist prior to the install. Everything will be created for you if necessary.

The SQL_SECURITY_STORENAME of "DynamicsGPWebServices" can be left as is, in the script.

The SECURITY_STORE value of "Sql" can also be left as is, in the above script.

The recommendation is to put the above script in a text editor, get it setup to how it needs to be with the correct information, then copy and paste it into the Command Prompt: Administrator window to run the script. **NOTE: If you’re familiar with the Command Prompt window, you can also change directory to where the Web Services .msi file is located, then you wouldn’t need the full path to the .msi file in the script, i.e. msiexec /I “Microsoft_Dynamics18_WebServices_x64_en-us.msi”….   Either way should work. This script is also generating an install.log file at the root of the C:\ drive, should the script fail to install Web Services. You can change the location of this install.log file as needed.

Once the silent installation of Web Services for Microsoft Dynamics GP completes successfully, you can then click on Start | All Programs | Microsoft Dynamics | Web Services for Microsoft Dynamics GP  | GP Web Services Configuration Wizard to complete the installation of Web Services on the GP databases.

**NOTE: If you are currently on, or upgrading to Dynamics GP 18.4 Web Services, you must be installing Web Services from the MDGPFALL2021_DVD_ENUS.zip media, which has a different, required service pack patch, KB4576800 built into it. This also is mentioned in our 'Upgrading Web Services' blog here >> (+) Microsoft Dynamics GP Upgrade - Upgrading Microsoft Dynamics Web Services - Microsoft Dynamics GP Community

**NOTE: If you are currently on, or upgrading to Dynamics GP 18.3 Web Services, you must be installing Web Services from the MDGPFALL2020_DVD_ENUS.zip media, which also has the required KB4527536 MSP patch in it for Web Services. Because of changes that were made to Web Services, we require installing from this specific DVD media and not just the MSP patch, unlike the GP 18.2 version. This is also mentioned in our 'Upgrading Web Services' blog here >> (+) Microsoft Dynamics GP Upgrade - Upgrading Microsoft Dynamics Web Services - Microsoft Dynamics GP Community

**NOTE: For Web Services on the new Microsoft Dynamics GP / 18.2.xxxx version, we found that the command prompt script will not slip-stream the service pack during the install/upgrade of Web Services, which is what we need to do otherwise the Web Services Configuration Wizard will give an error and not allow you to continue the process on the GP databases.

With a 'normal' install of Web Services using the Setup.exe, we'd need to install the KB4527536 patch for Web Services 18.2 from the CustomerSource or PartnerSource page, then, in the MDGP_DVD_ENUS for Microsoft Dynamics GP /18.2, go into the 'AdProd' directory, then 'WebServices', choose either x64 or x86, then in the 'Updates' folder for Web Services, remove the existing MSP file and replace it with this KB4527536 patch. Use the Setup.exe under MDGP_DVD_ENUS > GreatPlains > AdProd > WebServices > x64 to launch the Web Services install/upgrade to 18.2.xxxx version.

However, we've found that after installing Web Services via the command prompt script mentioned above, the Web Services Configuration Wizard shows a blue '?' for the functional currency check and it will fail the install stating no company databases are configured to install Web Services onto. This is even after a successful Web Services install via the command prompt script with the KB4527536 patch for Web Services 18.2. 

To get past this issue, you have to manually apply the KB4527536 patch for Web Services, then re-launch the Web Services Configuration Wizard again, which will get past the functional currency check, and allow you to complete the installation on the GP databases. This is only for the 18.2 version of Web Services for Dynamics GP. <updated 8/19/2020>

At this point, you can confirm that Web Services for Microsoft Dynamics GP is installed and working correctly by using the information in this KB article:

https://support.microsoft.com/en-us/help/950844/how-to-verify-if-microsoft-dynamics-gp-web-services-is-functioning-cor

We're currently working to verify another command line script to install Web Services using an Active Directory security store, which is required if TLS protocol is disabled on the server. We hope to have that tested and added to this blog soon.

Thank you!!