E1: PKG: CD Package Deployment And Incorrect LaunchPath Setting / Package Install Error - Could Not Locate Client Install Executable (setup.exe)
(Doc ID 626428.1)
Last updated on NOVEMBER 15, 2017
JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later Information in this document applies to any platform.
Scenario 1 - CD Package Deployment And Incorrect LaunchPath Setting
This document describes an issue scene with the LaunchPath registry setting being incorrect after a CD deployment of a package is completed on a workstation. There is known issue with the package deployment from a CD that sets the registry value for the LaunchPath to the setup.exe from the CD drive and not from the deployment server's OneWorld Client Install directory.
This is actually a known issue that was reported under <Bug 12446154> UNABLE TO LOCATE SETUP.EXE - SAR: 2544829 and was closed with consideration for a future release. The LaunchPath value can be found under registry key HKEY_LOCAL_MACHINE\Software\JDEdwards\OneWorld\Install.ini\B733x depending on your release. The symptom of the issue is first seen after the full package is deployed from the CD and the next update package is attempted. This document shows the error screen shots and offers a resolution to the issue.
In addition, we have a known issue described in Scenario 2 related to "LaunchPath" registry setting as well.
Scenario 2 - Package Install Error - Could not locate Client Install Executable (setup.exe).
A Package was built and package deployment record created. Now, when client logs into EnterpriseOne to receive the package, an error message occurs. When accepting the package, this error message is displayed:
"Could not locate client install executable (setup.exe). Would you like to find it yourself?"
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!