Hello, we are having troubles with a client, who is installing DXL+Tie client for VSE on all their computers.
They have 1000 computers to install, and only in 300 it was possible.
In the problematic ones, they show an "Unknown Error" displayer on the Agent log and Client Task Log:
In the log I see the next messages:
[17:36:11:258] Log: Launching command cmd.exe /c ""C:\Program Files\McAfee\TIEM\\mfehidin.exe" -installcab:TieVSCore.cab -log:%TEMP%\McAfeeLogs\TIEm\TIESyscoreInstall.log >> %TEMP%\McAfeeLogs\TIEm\TIEMSetupHelper.log && exit %ERRORLEVEL%"
[17:36:11:289] Log: InstallJTIContentFilter> Exit code: 1
[17:36:11:289] Log: Unlocking registry key [SOFTWARE\McAfee\TIEM]
MSI (s) (F8:34) [17:36:11:726]: Executing op: ActionStart(Name=RB_InstallJTIPlugin,,)
[17:36:11:726] Log: Reboot required key set
MSI (s) (F8:34) [17:36:11:726]: Executing op: CustomActionSchedule(Action=RB_InstallJTIPlugin,ActionType=3329,Source=BinaryData,Target=UninstallJTIPlugin,CustomActionData=C:\Program Files\McAfee\TIEM\)
MSI (s) (F8:34) [17:36:11:726]: Executing op: ActionStart(Name=InstallJtiPlugin,,)
MSI (s) (F8:34) [17:36:11:726]: Executing op: CustomActionSchedule(Action=InstallJtiPlugin,ActionType=3073,Source=BinaryData,Target=InstallJTIPlugin,CustomActionData=C:\Program Files\McAfee\TIEM\)
MSI (s) (F8:FC) [17:36:11:757]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIA1A8.tmp, Entrypoint: InstallJTIPlugin
[17:36:11:835] Log: Launching command cmd.exe /c ""C:\Program Files\McAfee\TIEM\TIEService.exe" -install >> %TEMP%\McAfeeLogs\TIEm\TIEMSetupHelper.log && exit %ERRORLEVEL%"
[17:36:11:851] Log: Failed to (un)install TIE service, process exited with 1
CustomAction InstallJtiPlugin returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
This two log files: "\McAfeeLogs\TIEm\TIESyscoreInstall.log >> %TEMP%\McAfeeLogs\TIEm\TIEMSetupHelper.log" are NOT created, only the attached TIESETUP.
They have the agent, VSE Version, and all the dependences fully compatible. I have opened a case with support, but after two months we haven´t received an answer to solve it.
Maybe someone have something to add and help us, Thanks to all.
So, the error code 1603 is a generic MSI error, and basically tells you nothing. If you install manually on one of these systems (not through ePO), do you run into the same issue?
That article can help you generate a verbose MSI log, where you can look for "return value 3", which may give you a better idea of what's going on.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center