Add-in error on Vista 64 bit machine

Add-in Express™ Support Service
That's what is more important than anything else

Add-in error on Vista 64 bit machine
 
T Rolle




Posts: 32
Joined: 2006-07-23
Hi,

A customer is getting the following error:

Error 1001. An exception occurred during the Commit phase of the installation... The system cannot find the file specified.

However, no filename is specified.

The contents of adxloader is as follows:

Add-in Express Loader Log File: 05/04/2011 12:26:10

Startup directory: C:\Program Files (x86)\xxx\xxx\
Loader version: 6.3.3052.0
Operating System: Microsoft Windows Vista Enterprise Edition (build 6000), 64-bit
Process Owner: System
Command Line: C:\Windows\syswow64\MsiExec.exe -Embedding 7B12DE2CDCA4AA6EE1A1423919155894 M Global\MSI0000
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: System
UAC (User Account Control): On
------------------------------------------------------------------------
12:26:10 812 5756 Starting the add-in unregistration process.
12:26:10 812 5756 Getting the latest CLR version.
12:26:10 812 5756 The latest CLR version is 'v2.0.50727'.
12:26:10 812 5756 Loading CLR: v2.0.50727.
12:26:10 812 5756 Calling CLRCreateInstance method.
12:26:10 812 5756 Failed.
12:26:10 812 5756 The loader will try to use the old Framework API.
12:26:10 812 5756 The CLR v2.0.50727 has been initialized successfully.
12:26:10 812 5756 Creating a new domain setup.
12:26:10 812 5756 Success.
12:26:10 812 5756 Getting the add-in directory.
12:26:10 812 5756 Success. The directory is 'C:\Program Files (x86)\xxx\xxx\'
12:26:10 812 5756 The configuration file is 'C:\Program Files (x86)\xxx\xxx\app.config'
12:26:10 812 5756 The 'shadow copy' is disabled.
12:26:10 812 5756 Creating a new application domain.
12:26:10 812 5756 Success.
12:26:10 812 5756 Getting the base directory for the domain.
12:26:10 812 5756 Success. The directory is 'C:\Program Files (x86)\xxx\xxx\'.
12:26:10 812 5756 Searching for the Add-in Express core library.
12:26:10 812 5756 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
12:26:10 812 5756 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
12:26:10 812 5756 Assembly identity is 'AddinExpress.MSO.2005'.
12:26:13 812 5756 Success.
12:26:13 812 5756 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
12:26:13 812 5756 Success.
12:26:13 812 5756 Creating an instance of the XML parser class.
12:26:13 812 5756 Success.
12:26:13 812 5756 Loading the manifest file (C:\Program Files (x86)\xxx\xxx\adxloader.dll.manifest).
12:26:13 812 5756 Success.
12:26:13 812 5756 Getting the root element of the manifest (C:\Program Files (x86)\xxx\xxx\adxloader.dll.manifest).
12:26:13 812 5756 Success.
12:26:13 812 5756 Getting the 'assemblyIdentity' element of the manifest (C:\Program Files (x86)\xxx\xxx\adxloader.dll.manifest).
12:26:13 812 5756 Success.
12:26:13 812 5756 Searching for the 'name' attribute of the 'assemblyIdentity' element.
12:26:13 812 5756 Success. The name is xxx, PublicKeyToken=xxx'.
12:26:13 812 5756 Calling the managed procedure to unregister the 'xxx, PublicKeyToken=xxx' assembly.
12:26:13 1244 Connecting to the application domain of the Add-in Express loader.
12:26:13 1244 Success.
12:26:13 1244 Loading the 'xxx, PublicKeyToken=xxx' assembly.
12:26:13 1244 Success.
12:26:13 1244 Unregistering the 'xxx, PublicKeyToken=xxx' assembly (administrator).
12:26:14 1244 The ' xxx, PublicKeyToken=xxx' assembly has been unregistered successfully.
12:26:15 1244 The managed unregistration process is complete with HRESULT = 0.
12:26:15 812 5756 The add-in unregistration process is completed with HRESULT = 0.

So, there's a couple of things I don't understand here.

1. The first line of data indicates that the unregistration process is starting. I compared this log file to a successfull installation and the lines of data such as reading the registry key and attempting to get the class object are missing.

2. The CLRCreateInstance method has failed.

3. Why is the managed procedure to unregister the product being called.

The entire process then rollsback and the installation fails.

Not sure if this has anything to do with the customer using 64 bit. So I recompiled the project to target 64x and changed the installer to target that as well. Waiting to hear back from the client but in the meantime wanted to run this by you to see if there's potentially another problem.

Thanks.
Posted 04 May, 2011 23:20:44 Top
Eugene Astafiev


Add-in Express team


Posts: 8540
Joined: 2007-07-25
Hi Tonio,

Thank you for providing me with the adxloader.log file. I have noticed the following lines in the log:

1.
Loader version: 6.3.3052.0


First of all please note that you use an old build of Add-in Express 2010. You can download the latest build from our web site. Then please don't forget to replace the adxloader.dll in the Loader folder of your project with a new one (see the Redistributables folder).

2.
Operating System: Microsoft Windows Vista Enterprise Edition (build 6000), 64-bit


It looks like you didn't install the latest service packs for OS. Am I right?

3.
Process Owner: System


Please take a look at the How to allow users who are not administrators to install MSI packages article. It looks like somebody has changed the default value of the AlwaysInstallElevated key in windows registry. Please try to change it. Does it help?
.NET, Extended MAPI, Windows Phone & RT
Posted 05 May, 2011 04:37:57 Top