vendredi 17 avril 2015

MSI Error 1719. The Windows Installer Service could not be accessed

Situation: We have an auto-update machanism in place which downloads and installs new MSI packages of our product. We call msiexec with full logging. Our MSI package has a impersonated and deferred custom action that registers our product as add-in in Windows Registry. Same goes for de-registration.


Problem: In about <1% of the cases the upgrade fails with the following error:



MSI (s) (5C:CC) [19:05:26:055]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3D95.tmp, Entrypoint: SchedXmlConfig
MSI (s) (5C:CC) [19:05:26:055]: Lost connection to custom action server process. Attempting to regenerate.
MSI (s) (5C:FC) [19:05:26:055]: Generating random cookie.
MSI (s) (5C:FC) [19:05:26:058]: Created Custom Action Server with PID 4464 (0x1170).
MSI (s) (5C:FC) [19:05:26:109]: CA Server Process has terminated.
MSI (s) (5C:CC) [19:05:26:110]: Closing MSIHANDLE (133) of type 790542 for thread 716
MSI (s) (5C:CC) [19:05:26:118]: Note: 1: 1719
MSI (s) (5C:CC) [19:05:26:119]: Product: XYZ -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.


Running the same installation again on the same machine and user works fine. We habe two log files from the same machine, one working and one failing.


Question Has anybody experienced similar errors? What has it caused?


Resources



Aucun commentaire:

Enregistrer un commentaire