It *was* a vbscript.dll registration issue.  I followed the instructions
here http://blogs.msdn.com/b/astebner/archive/2007/06/07/3151752.aspx
(following the 64-bit bits) to fix the problem.  I have no idea how the
script engine got registered at the user level, but the key was there.
Once I removed the 2 user-level script-engine keys, things started
working again.

I wasn't having trouble until I patched my computer with the latest
round of critical patches from Microsoft.  One of the patches was in the
critical list but wasn't checked by default.  I went ahead and installed
it too.  That patch changes the way updates are installed, so it's
possible it messed with these registry keys.  This isn't verified, but
I'm including the information in case anyone else starts having issues.

Thanks for the help Blair.

-----Original Message-----
From: Blair [mailto:os...@live.com] 
Sent: Thursday, January 20, 2011 11:46 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] First build gives ICE errors;subsequent builds
don't

Some of the MSFT-supplied ICE tests use VBScript (most use C/C++ native
code).

2738
 Could not access VBScript run time for custom action [2].

http://blogs.msdn.com/b/heaths/archive/2007/05/31/windows-installer-erro
rs-2
738-and-2739-with-script-custom-actions.aspx

Could also be related to an anti-virus product. Be sure to exclude
runtime scanning of your %TEMP% directory of your build machine(s) (at
least during builds).

-Blair

-----Original Message-----
From: Brownfield, Cory [mailto:cbrownfi...@aeci.org]
Sent: Tuesday, January 18, 2011 12:18 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] First build gives ICE errors; subsequent builds
don't

Setup:

Windows 7 64-bit (fully patched)

Visual Studio 2010 Ultimate

WiX 3.5 build 2430 (latest weekly)

 

I've recently noticed a problem with all my WiX projects.  Trying to
build after a change or after a clean, I get a set of ICE errors.  So
rebuilding always gives me these errors and following up with a build
always fixes them.  Here is an example set of errors:

 

--------------

Error executing ICE action 'ICE08'. The most common cause of this kind
of ICE failure is an incorrectly registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The installer has encountered an unexpected
error installing this package. This may indicate a problem with this
package. The error code is 2738. ".

 

Error executing ICE action 'ICE09'. The most common cause of this kind
of ICE failure is an incorrectly registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The installer has encountered an unexpected
error installing this package. This may indicate a problem with this
package. The error code is 2738. ".

 

Error executing ICE action 'ICE32'. The most common cause of this kind
of ICE failure is an incorrectly registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The installer has encountered an unexpected
error installing this package. This may indicate a problem with this
package. The error code is 2738. ".

 

Error executing ICE action 'ICE61'. The most common cause of this kind
of ICE failure is an incorrectly registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to
solve this problem. The following string format was not expected by the
external UI message logger: "The installer has encountered an unexpected
error installing this package. This may indicate a problem with this
package. The error code is 2738. ".

--------------

 

After getting these errors, I can 'build' again and the errors go away
and the MSI is built.  It's pretty annoying.  I've tried re-installing
WiX.  I've also tried re-registering the scripting engines (although I
don't think that is a problem-I'm not doing any scripting).  So any
ideas?

------------------------------------------------------------------------
----
--
Protect Your Site and Customers from Malware Attacks Learn about various
malware tactics and how to avoid them. Understand malware threats, the
impact they can have on your business, and how you can protect your
company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------
------
Protect Your Site and Customers from Malware Attacks Learn about various
malware tactics and how to avoid them. Understand malware threats, the
impact they can have on your business, and how you can protect your
company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to