Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
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="<SqlInstance>" SERVICE_USER_DOMAIN="<Domain>" SERVICE_USER_NAME="<User>" SERVICE_USER_PASSWORD="<Password>" SECURITY_STORE="Sql" SQL_SECURITY_INSTANCE="<SQLInstance>" SQL_SECURITY_DATABASE="<SqlDatabase>" SQL_SECURITY_STORENAME="DynamicsGPWebServices"
>>Verify the path to the Microsoft_DynamicsGP18_WebServices_x64_en-us.msi file is correct.>>Replace <Domain> with the actual domain name>>Replace <User> and <Password> with the actual domain\userid and password of the account you want to have setup to run Web Services.>>Replace <SQLInstance> with the actual SQL Server instance name where the Dynamics GP databases exist.>>Replace <SqlDatabase> with the name of the new or existing Web Services security store database you want to use/create. **Note: The Web Services security store database need not exist prior to the install. Everything will be created for you if necessary.
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: For Web Services on the new Microsoft Dynamics GP / 18.2.xxxx version, you MUST slip-stream the service pack during the install/upgrade of Web Services, otherwise the Web Services Configuration Wizard will give an error and not allow you to continue the process on the GP databases.
Applying the patch for Web Services onto an existing install also will not work, the patch must be slip-streamed with the install.
To do this, you'll 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.
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:
Business Applications communities