Pem Agent installation on Windows Node fails with error code 1157:
Invoking remote custom action. DLL: C:\Windows\Installer\MSIFD07.tmp, Entrypoint: getCredentials Action start 7:26:23: getCredentials. Note: 1: 1723 2: getCredentials 3: getCredentials 4: C:\Windows\Installer\MSIFD07.tmp CustomAction getCredentials returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox) Product: POA Agent -- Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action getCredentials, entry: getCredentials, library: C:\Windows\Installer\MSIFD07.tmp Action ended 7:26:23: getCredentials. Return value 3. Action ended 7:26:23: INSTALL. Return value 3.
Coldfusion is installed prior Pem Agent installation. Coldfusion variable (
C:\ColdFusion9\verity\k2\_nti40\bin) prevents Pem agent installation.
Check Coldfusion variables as below:
C:\Users\Administrator>set |findstr /i cold Path=C:\ColdFusion9\verity\k2\_nti40\bin
When you install Pem agent, system unpack PAgent package to special directory and tries to use libraries from this directory. But as you have system variables, system tries to find libraries in system variables first. In our case, ACE.dll exists in C:\ColdFusion9\verity\k2_nti40\bin and in Pem agent installation directory as well. So system tries to load ACE.dll from C:\ColdFusion9\verity\k2_nti40\bin.
To solve the issue:
- Remove Coldfusion variables path in system variables.
- Reboot Windows Service Node.
- Launch task for Pem agent installation once again.