|
|
|
Tyson Stolarski
Posts: 38
Joined: 2006-12-01
|
One of the customers who have my add-in product installed is getting the following error message every time they try to start Excel:
ADX Loader Error
The loader is trying to run the following assembly:
'MyAddInProduct, PublicKeyToken=XXX...XXX'.
The operation fails with HRESULT = -2146234105'.
I am using the latest version of Add-in Express, with the latest version of the adxloader.dll.
I have had this issue on my development machine before, but it was back when the dll association was version dependent. The error message would then state a different version to the one referenced in the registry.
However, since you changed it to be version independent, no version is listed in the error message. I checked the registry on the deployment machine, and it seems fine, no version is referenced their either. To be on the safe side, I deleted all the add-in express generated registry entries and installed again. Still the same problem.
The registry entries I deleted was everything under the HKEY_CLASSES_ROOT\CLSID\{MyAddinsCLSID}\ key.
Is there any other keys I should check for an invalid reference???
Are there any other causes of this error apart from the registry pointing to an invalid dll???
Any other ideas to solve this issue? Its only occurring on the one machine currently. It works fine on my development machine and many other machines its deployed on.
Cheers.
Tyson. |
|
|
Posted 07 May, 2007 22:22:57
|
|
Top
|
|
|
Todd Carlson
Posts: 29
Joined: 2006-05-07
|
Tyson,
We had a similar problem. Several machines would work fine, then 1 or two would fail with the error 80131107 (-2146234105) "The format of the classlibrary.dll is invalid.".
I our case, we were using our own custom installer & that installer was not installing the "Shared Add-in Support Update for Microsoft .NET Framework 2.0 (KB908002)". Once we added that to our installer the problem machines were fixed.
HTH,
Todd
|
|
|
Posted 08 May, 2007 08:54:27
|
|
Top
|
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hi Tyson.
What version of Excel do you use?
Could you please send me the adxloader.log file with the information about the error (.\My Documents\Add-in Express\adxloader.log)?
P.S. Note that we take up your forum requests in the order we receive them.
Besides, it may take us some time to investigate your issue. Please be sure we will let you know as soon as the best possible solution is found.
|
|
|
Posted 08 May, 2007 09:08:20
|
|
Top
|
|
|
Apolon Ivankovic
Posts: 4
Joined: 2006-11-25
|
Sergey,
Finally got the adxloader.log file from the customer machine where the load problem was occurring (see below). It seems to have something to do with a .NET V1.x VM interaction. The customer's Excel version is Excel 2003.
14:41:00 960 Start.
14:41:00 960 Reading the registry key 'HKEY_CLASSES_ROOT\CLSID\{FA4A5804-FA31-40E1-B379-ACBBA63FDDF8}'
14:41:00 960 Success. The registry key 'HKEY_CLASSES_ROOT\CLSID\{FA4A5804-FA31-40E1-B379-ACBBA63FDDF8}' is closed.
14:41:00 960 Converting the '{4BA250A6-8BCA-46A6-982A-F340081187C3}' CLSID from string.
14:41:00 960 Success.
14:41:00 960 Attempting to get the class object by the '{4BA250A6-8BCA-46A6-982A-F340081187C3}' CLSID.
14:41:00 960 Success.
14:41:00 960 Creating a new instance of the add-in loader.
14:41:00 960 Success.
14:41:00 960 Loading the configuration from the system registry.
14:41:00 960 The configuration has been loaded successfully.
14:41:00 960 Runtime version: v2.0.50727.
14:41:00 960 Assembly name: ExcelAddin, PublicKeyToken=C5A0D53497499135.
14:41:00 960 Class name: MacroView.ExcelAddin.AddinModule.
14:41:00 960 Attempting to create a new instance of the managed add-in class: CLR - v1.1.4322
14:41:00 960 Loading CLR: v1.1.4322.
14:41:01 960 The CLR (v1.1.4322) has been initialized successfully.
14:41:02 960 Creating a new domain setup.
14:41:02 960 Success.
14:41:02 960 Getting the add-in directory.
14:41:02 960 Success. The directory is 'C:\Program Files\MacroView\ExcelAddin\'
14:41:02 960 The 'shadow copy' is enabled.
14:41:02 960 Creating a new application domain.
14:41:02 960 Success.
14:41:03 960 The loader failed creating an instance of the managed add-in class. HResult = -2146234105.
14:41:03 960 Attempting to create a new instance of the managed add-in class: CLR - v2.0.50727
14:41:03 960 The managed add-in class has been created successfully.
14:41:03 960 The loader failed creating an instance of the managed add-in class. HResult = -2146234105. |
|
|
Posted 12 Jun, 2007 06:18:49
|
|
Top
|
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hi Apolon.
Please include the 'Shared Add-in Support Update for Microsoft .NET Framework 2.0 (KB908002)' prerequisite in the setup project of your add-in.
You also need to run the setup.exe file to install the add-in corectly on the user's PC.
|
|
|
Posted 12 Jun, 2007 09:19:20
|
|
Top
|
|
|
Tyson Stolarski
Posts: 38
Joined: 2006-12-01
|
Sergey,
The above error was resolved by removing the .NET framework v1.1 from the machine in question. It had both v1.1 and v2.0 installed, and this must of caused some conflict. As you can see within the log, it was loading the addin class within the .NET v1.1 CLR.
However, the same machine now has a new problem. The add-in still intalls fine, but again fails to load when Excel starts. And we are using the setup.exe file, with the 'Shared Add-in Support Update for Microsoft .NET Framework 2.0 (KB908002)' prerequisite included. This is the new error log:
Add-in Express Loader Log File: 07/05/2007 11:41:02
Startup directory: C:\Program Files\MacroView\ExcelAddin\
------------------
11:41:02 932 Start.
11:41:02 932 Reading the registry key 'HKEY_CLASSES_ROOT\CLSID\{FA4A5804-FA31-40E1-B379-ACBBA63FDDF8}'
11:41:02 932 Success. The registry key 'HKEY_CLASSES_ROOT\CLSID\{FA4A5804-FA31-40E1-B379-ACBBA63FDDF8}' is closed.
11:41:02 932 Converting the '{4BA250A6-8BCA-46A6-982A-F340081187C3}' CLSID from string.
11:41:02 932 Success.
11:41:02 932 Attempting to get the class object by the '{4BA250A6-8BCA-46A6-982A-F340081187C3}' CLSID.
11:41:02 932 Success.
11:41:02 932 Creating a new instance of the add-in loader.
11:41:02 932 Success.
11:41:02 932 Loading the configuration from the system registry.
11:41:02 932 The loader failed creating an instance of the managed add-in class. HResult = -2146232576. |
|
|
Posted 05 Jul, 2007 01:19:31
|
|
Top
|
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hi Tyson.
The above error was resolved by removing the .NET framework v1.1 from the machine in question. It had both v1.1 and v2.0 installed, and this must of caused some conflict. As you can see within the log, it was loading the addin class within the .NET v1.1 CLR.
You just needed to install the 'Shared Add-in Support Update for .NET Framework v2.0' update.
Do you run the setup.exe file to install the add-in? |
|
|
Posted 05 Jul, 2007 07:38:50
|
|
Top
|
|
|
Tyson Stolarski
Posts: 38
Joined: 2006-12-01
|
|
Tyson Stolarski wrote:
And we are using the setup.exe file, with the 'Shared Add-in Support Update for Microsoft .NET Framework 2.0 (KB908002)' prerequisite included.
Yes Sergey, in both instances we were using the setup.exe file. The first error was resolved by removing the .NET v1.1 framework. Using the setup.exe file and installing the Shared Add-in Support as you stated did not resolve the issue.
The second issue I'm still stuck on, and this time around the log doesn't have much useful information in it.
The Add-in was deployed on around 10 machines in this company. They all have a similar setup, yet it is only this 1 machine that is causing any problems. It seems unusual that the one machine had 2 unrelated deployment issues, so although the log has changed I'm inclined to think the problem is still related. Any ideas? |
|
|
Posted 05 Jul, 2007 22:25:47
|
|
Top
|
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hi Tyson.
Please download a new version of the ADX loader here:
http://www.add-in-express.com/projects/adxloader.zip
You need to replace the existing loader with a new one in the Loader subdirectory of your add-in and rebuild the project.
If the error still appears, please send me the latest log. |
|
|
Posted 06 Jul, 2007 07:03:31
|
|
Top
|
|
Forums
Topics
Search
Help
Login
Register