When I click deploy, I get an error that says “Failed to install Epicor Data Discovery”. The event log does not provide any useful info, it just says Epicor Data Discovery failed
I have tried to deploy EDD a couple of times, using also the last screen shot that sanjeev sent but the same message is still coming up. Here is the last portion of the EDD logfile. I can’t see why its failing to install. Maybe someone can…
MSI (s) (0C:8C) [15:20:41:787]: Windows Installer installed the product. Product Name: Epicor Data Discovery. Product Version: 2.1.28.8377. Product Language: 1033. Manufacturer: Epicor Software. Installation success or error status: 1603.
MSI (s) (0C:8C) [15:20:41:793]: Deferring clean up of packages/files, if any exist
MSI (s) (0C:8C) [15:20:41:793]: MainEngineThread is returning 1603
MSI (s) (0C:6C) [15:20:41:796]: RESTART MANAGER: Session closed.
MSI (s) (0C:6C) [15:20:41:796]: No System Restore sequence number for this installation.
=== Logging stopped: 2/19/2019 15:20:41 ===
MSI (s) (0C:6C) [15:20:41:820]: User policy value ‘DisableRollback’ is 0
MSI (s) (0C:6C) [15:20:41:820]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (0C:6C) [15:20:41:820]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (0C:6C) [15:20:41:820]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (0C:6C) [15:20:41:820]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (0C:6C) [15:20:41:821]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (0C:6C) [15:20:41:822]: Destroying RemoteAPI object.
MSI (s) (0C:A8) [15:20:41:822]: Custom Action Manager thread ending.
MSI (c) (40:50) [15:20:41:823]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (40:50) [15:20:41:824]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2/19/2019 15:20:41 ===
Mine ended up saying something about the authentication since we’re SSO.
I had to change the following from “None” to “Windows” in the app server’s web.config file. Always make a backup of your web.config if you decide to change something
I just recently went through several unsuccessful attempts at deploying EDD until I worked with Epicor and finally got a successful install. Here are some instructions that I hope might be helpful to you to get this working. Please note these are things that worked for us in our environment. Yours may be somewhat different but hopefully this will help give you some things to test and try in order to get it working. Otherwise I would suggest entering a help ticket with Epicor cause they helped me to finally get EDD working.
Thank you for your help, but I’ve actually done some of those steps before and did them again in the same sequence as demonstrated in the PDF, it generated the same result.
even though everything checks out according to the steps in the PDF.
Just to add to @tomdomurat comments. If you are running a version with an update applied to it then the log file will be in the ERP10\ERP10.2.xxx.0\Updates\ERP10.2.xxx.xx\SupplementalInstalls\Data Discovery directory.
I’m actually suffering from a the following warning
EDD installer identified (and bypassed) potential security vulnerabiliy.
Unable to discover current default SSL/TLS certificate protocol. Please verify this server uses tls1.2.
The server is windows 2016 which tls1.2 is supposed to be enabled by default.
So I was suffering from problems during the Validation phase of the deployment with a “Installer has detected SSL/TLS vulnerability.” And messages mentioned in the last post.
I ended up creating a new Self signed certificate, and set it up in the binding of the website in IIS. as below
Once I had done that and made sure the SSL Domain Name matched the Subject Alternative Name in the certificate that I applied to the website. Ideally I want to use our wildcard certificate, but testing that will have to wait.
Once all that was fixed it worked. One thing during my troubleshooting, I noticed if I used the same application pool as the app server it would fail as well. I suspect because the app pool gets shut down during the install process (this gave me token errors).