WiX 3.0 throws error 217, while being executed by continuous integration

前端 未结 12 1741
醉酒成梦
醉酒成梦 2020-12-07 14:23

This is the error that is thrown by our automated build suite on Windows 2008, while running ICEs (after migrating from WiX 2.0 to WiX 3.0):

LGHT0217:

12条回答
  •  孤街浪徒
    2020-12-07 15:18

    None of the above suggestions worked for me, for me the anti-virus (mcafee) came into the picture and looks like it updated the vbscript.dll registry entry to a wrong DLL location. These are the things to keep in mind:

    1. Some of the WiX ICE validations are implemented using VBSCRIPT.
    2. So while compiling the MSI, the build server would need access to the c:\windows\system32\vbscript.dll.
    3. Chances are that somehow the user that runs your build lost access to this DLL.
    4. As mentioned in the above answers do look for the admin access/registry access and make sure your user has it.

    Here are the steps that I took to fix the issue:

    1. Open cmd (run as admin) on the build agent machine.
    2. Run RegEdit
    3. Select the root, then click ctrl + f and Search for the following registry entry : {B54F3741-5B07-11cf-A4B0-00AA004A55E8}
    4. Look for the InprocServer32\Default Key

    1. On my build agent, the path was replaced with a mcafee DLL location. I updated the path back to c:\windows\system32\vbscript.dll
    2. Editing the registry entry was not easy, as it was a protected registry entry. I used the below link to get access permissions changed before I could edit the property: Edit protected registry entry

    Once I updated the path, everything started working as usual.

提交回复
热议问题