30
HI,
I am trying to install Microsoft Dynamics GP Odata when installing the finish part will rolling back error
The Odata for Microsoft Dynamics GP installation has ended prematurely.
Thanks
Regards
MK
Unless there is more information in the Event Viewer logs, we don't have enough to go on, as to why the OData installation is failing.
The installation of OData is pretty straight-forward, just accepting the EULA, entering your SQL Server information and name of the GP system database, an account to run the OData service and then the certificate/site in IIS you're installing onto.
In IIS, you need the site bound with the SSL certificate being used for OData.
On the server, besides IIS, you also need these features installed:
1. Install 'Web Server (IIS)' and click to add those features.
2. Under 'NET Framework 4.6' and 'WCF Services', mark to install 'HTTP Activation' and accept those added features.
3. Mark 'Windows Authentication' under 'Web Server (IIS)' > 'Web Server' > 'Security'
If you've verified all of the above, you can setup a Windows Installer log via these steps:
a. On the server/machine you're attempting to install OData, open the Registry Editor by clicking on Start > Run, type in REGEDIT and clicking OK.
b. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\ if a 64-bit machine or HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\ if 32-bit.
c. Verify that under \Windows\ that an ‘Installer’ key exists, if not, right-click on ‘Windows’ and choose to add a new key, naming it ‘Installer’.
d. Under \Installer\, we need to add, if it doesn’t exist, a string value by right-clicking on ‘Installer’ choose a new String Value and naming it ‘Logging’.
e. Double-click on the ‘Logging’ value and for the ‘Value Data’ field, enter ‘voicewarmupx’.
f. With the Windows Installer log setup in the Registry Editor, re-create the issue of OData for Dynamics GP failing to install on this machine.
g. Once the install fails again with the same error message, click Start > Run, type %temp% and click OK to get to the TEMP directory of the account you’re logged onto the machine as.
Look for a MSIxxxx.log file that was created at the date/time you just attempted the OData install. That is the Windows Installer log we’d want to look at for more information as to why the install is failing.
**NOTE: By default, it may take you to the TEMP/2/ directory, for example, so you may need to go up one level to find the MSIxxxx.log file.
Thanks,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (