search

liulee / gurtle

Automatically exported from code.google.com/p/gurtle
0 stars 0 forks source link

MSI build fails with ICE errors under non-admin #31

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Check out the sources (r121 at the time of this reporting)
2. Run build.cmd in the root of the working/export copy

What is the expected output? What do you see instead?

The build show succeed entirely. Instead it fails during the build of the
MSI with the following errors:

light.exe : error LGHT0217 : 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. ".
light.exe : error LGHT0217 : 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. ".
light.exe : error LGHT0217 : 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. ".
light.exe : error LGHT0217 : 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. ".

Additional information:

Building on Microsoft Windows 32-bit Vista Business, 6.0.6001, SP 1
Building with non-administrator account with following privileges:

Privilege Name                Description                          State   
============================= ==================================== ========
SeMachineAccountPrivilege     Add workstations to domain           Disabled
SeShutdownPrivilege           Shut down the system                 Disabled
SeChangeNotifyPrivilege       Bypass traverse checking             Enabled 
SeUndockPrivilege             Remove computer from docking station Disabled
SeIncreaseWorkingSetPrivilege Increase a process working set       Disabled
SeTimeZonePrivilege           Change the time zone                 Disabled

Original issue reported on code.google.com by azizatif on 27 Apr 2009 at 9:27

GoogleCodeExporter commented 9 years ago 
I should that the FAQ link in the error messages did not help.

Original comment by azizatif on 27 Apr 2009 at 9:30

GoogleCodeExporter commented 9 years ago 
Running the setup part of the build script with an administrator account works
without the ICE errors. Changed the issue summary accordingly.

Original comment by azizatif on 27 Apr 2009 at 9:34

GoogleCodeExporter commented 9 years ago

Original comment by azizatif on 27 Apr 2009 at 9:34

GoogleCodeExporter commented 9 years ago 
I've applied an interim fix in r123. The MSI build is broken out into a separate
script that only runs if the user has admin privileges.

Original comment by azizatif on 27 Apr 2009 at 10:50

GoogleCodeExporter commented 9 years ago 
Sorry about that. I'm running with Admin privileges on Vista and never had 
problems
building msi's with WiX (UAC turned ON).

But now, the check for admin doesn't seem to work. The script tells me that I'm 
not
an admin and fails to build the msi.

Original comment by tortoisesvn on 28 Apr 2009 at 4:05

GoogleCodeExporter commented 9 years ago 
The posts linked to from the FAQ all relate to scripted custom actions, but we 
don't
use those in the Gurtle installer. So there must be another reason why it fails 
for you.

Did you (or your virus scanner/firewall) deactivate the scripting engine?

Found some possible solutions:
http://weblogs.asp.net/felipeferreira/archive/2008/03/03/light-exe-error-lght021
7-an-unexpected-external-ui-message-was-received-the-installer-has-encountered-a
n-unexpected-error-installing-this-package-this-may-indicate-a-problem-with-this
-package-the-error-code-is-2738.aspx

http://blogs.msdn.com/astebner/archive/2008/04/01/8349448.aspx

Original comment by tortoisesvn on 28 Apr 2009 at 4:12

GoogleCodeExporter commented 9 years ago 
> Did you (or your virus scanner/firewall) deactivate the scripting engine?

Nope. I don't run any anti-virus software. :O

> but we don't use those in the Gurtle installer

No we don't but I think it's to do with ICE. Perhaps a workaround could be to 
try and
use the "sice" switch on light to those suppress ICE 217 errors?

> heck for admin doesn't seem to work.

I guess if you run tools\amadmin then it prints, "You are NOT a system
administrator"? It could be your administrator account is running in 
unprivileged
mode. What does WHOAMI /PRIV display for you?

Original comment by azizatif on 28 Apr 2009 at 4:20

GoogleCodeExporter commented 9 years ago 
>> Did you (or your virus scanner/firewall) deactivate the scripting engine?
>Nope. I don't run any anti-virus software. :O

Me neither :)

>> but we don't use those in the Gurtle installer

>No we don't but I think it's to do with ICE. Perhaps a workaround could be to 
try 
>and use the "sice" switch on light to those suppress ICE 217 errors?

Sure, it that works for you, then that switch should be ok.

>> heck for admin doesn't seem to work.

>I guess if you run tools\amadmin then it prints, "You are NOT a system
>administrator"? It could be your administrator account is running in 
unprivileged
>mode. What does WHOAMI /PRIV display for you? 

tools\amadmin.cmd returns "You are NOT a system administrator".
WHOAMI /ALL shows:

BENUTZERINFORMATIONEN
---------------------

Benutzername      SID                                           
================= ==============================================
kueng-win32\kueng S-1-5-21-3276022382-4081104617-3697081200-1000

GRUPPENINFORMATIONEN
--------------------

Gruppenname                                              Typ                 
SID    
     Attribute                                                      
======================================================== ===================
============ ===============================================================
Jeder                                                    Bekannte Gruppe     
S-1-1-0
     Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe
VORDEFINIERT\Administratoren                             Alias              
S-1-5-32-544 Gruppen, die nur zum Ablehnen verwendet wird                   
VORDEFINIERT\Benutzer                                    Alias              
S-1-5-32-545 Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe
NT-AUTORITŽT\INTERAKTIV                                  Bekannte Gruppe     
S-1-5-4
     Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe
NT-AUTORITŽT\Authentifizierte Benutzer                   Bekannte Gruppe     
S-1-5-11
    Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe
NT-AUTORITŽT\Diese Organisation                          Bekannte Gruppe     
S-1-5-15
    Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe
LOKAL                                                    Bekannte Gruppe     
S-1-2-0
     Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe
NT-AUTORITŽT\NTLM-Authentifizierung                      Bekannte Gruppe    
S-1-5-64-10  Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe
Verbindliche Beschriftung\Mittlere Verbindlichkeitsstufe Unbekannter SID-Typ
S-1-16-8192  Verbindliche Gruppe, Standardm„áig aktiviert, Aktivierte Gruppe

BERECHTIGUNGSINFORMATIONEN
--------------------------

Berechtigungsname             Beschreibung                                   
Status     
============================= ============================================== 
===========
SeShutdownPrivilege           Herunterfahren des Systems                     
Deaktiviert
SeChangeNotifyPrivilege       Auslassen der durchsuchenden šberprfung       
Aktiviert  
SeUndockPrivilege             Entfernen des Computers von der Dockingstation 
Deaktiviert
SeIncreaseWorkingSetPrivilege Arbeitssatz eines Prozesses vergrӇern         
Deaktiviert
SeTimeZonePrivilege           Žndern der Zeitzone                            
Deaktiviert

(sorry it's in German, but I think since you're working in Switzerland you 
should be
able to understand it?)

Original comment by tortoisesvn on 28 Apr 2009 at 4:27

GoogleCodeExporter commented 9 years ago 
> Found some possible solutions:

Neither of those seem to be my case. I checked and neither JScript nor VBScript
engines are in my HKCU hive. Only HKLM.

Here's me looking for VBScript in HKCU:

C:\>reg query HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
ERROR: The system was unable to find the specified registry key or value.

Here's me looking for VBScript in HKLM:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
    (Default)    REG_SZ    VB Script Language

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
\Implemented
Categories
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
\OLEScript
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
\ProgID

Ditto for JScript.

Original comment by azizatif on 28 Apr 2009 at 4:31

GoogleCodeExporter commented 9 years ago 
Same on my machine. They're also only registered under HKLM.

Original comment by tortoisesvn on 28 Apr 2009 at 4:36

GoogleCodeExporter commented 9 years ago

Original comment by azizatif on 28 Apr 2009 at 4:38

GoogleCodeExporter commented 9 years ago 
Looks like MSI is built anyhow irrespective of ICE errors. Will suppress those.

Original comment by azizatif on 28 Apr 2009 at 4:40

GoogleCodeExporter commented 9 years ago 
Fixed in r128.

Original comment by azizatif on 28 Apr 2009 at 4:42

GoogleCodeExporter commented 9 years ago 
Yep, works perfectly now.

Original comment by tortoisesvn on 28 Apr 2009 at 4:47