|
brian
Posts: 31
Joined: 2008-09-02
|
We've got a strange (to me) issue with a client trying to install our add-in. Client is running on XP SP3, Outlook 2007. Add-in is compiled with VS2010 but targeting .NET 2.0.
When the client tries to install the add-in, everything appears to go as normal. adxloader.log looks normal as well. However, no buttons show up and our add-in is nowhere to be found in Trust Center/COM add-ins. Trying to manually add our adxloader.dll in the COM Add-ins throws no errors but accomplishes nothing.
However, this user has some other Outlook add-in installed called ACT which seems to be loading mscoree.dll directly? I'm wondering if this is causing a conflict if it's loading the mscoree.dll from another version of the CLR than I'm targeting and so my add-in is getting clobbered? http://i.imgur.com/wBsCV.png of the add-in (disabled, which didn't help).
We did not take the step of uninstalling ACT all the way - other users in her environment are using my add-in successfully without ACT.
I'm wondering if this is something you've seen before and if I'm correct in telling her that the ACT plugin is the culprit. |
|
|
brian
Posts: 31
Joined: 2008-09-02
|
Here is the adxloader.log:
Add-in Express Loader Log File: 02/03/2011 14:30:14
Startup directory: C:Program FilesBDRQ
Loader version: 6.3.3052.0
Operating System: Microsoft Windows XP Professional Service Pack 3 (build 2600)
Process Owner: Administrator
Command Line: regsvr32 adxloader.dll
Run 'As Administrator': Yes
Process Elevated: No
Integrity Level: Untrusted
UAC (User Account Control): Off
------------------------------------------------------------------------
14:30:14 1860 7000 Starting the add-in registration process.
14:30:14 1860 7000 Getting the latest CLR version.
14:30:14 1860 7000 The latest CLR version is 'v2.0.50727'.
14:30:14 1860 7000 Loading CLR: v2.0.50727.
14:30:14 1860 7000 The CLR v2.0.50727 has been initialized successfully.
14:30:14 1860 7000 Creating a new domain setup.
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Getting the add-in directory.
14:30:14 1860 7000 Success. The directory is 'C:Program FilesBDRQ'
14:30:14 1860 7000 The configuration file is 'C:Program FilesBDRQpp.config'
14:30:14 1860 7000 The 'shadow copy' is disabled.
14:30:14 1860 7000 Creating a new application domain.
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Getting the base directory for the domain.
14:30:14 1860 7000 Success. The directory is 'C:Program FilesBDRQ'.
14:30:14 1860 7000 Searching for the Add-in Express core library.
14:30:14 1860 7000 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
14:30:14 1860 7000 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
14:30:14 1860 7000 Assembly identity is 'AddinExpress.MSO.2005'.
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Creating an instance of the XML parser class.
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Loading the manifest file (C:Program FilesBDRQdxloader.dll.manifest).
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Getting the root element of the manifest (C:Program FilesBDRQdxloader.dll.manifest).
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Getting the 'assemblyIdentity' element of the manifest (C:Program FilesBDRQdxloader.dll.manifest).
14:30:14 1860 7000 Success.
14:30:14 1860 7000 Searching for the 'name' attribute of the 'assemblyIdentity' element.
14:30:14 1860 7000 Success. The name is 'Malone, PublicKeyToken=a35be5083775e042'.
14:30:14 1860 7000 Calling the managed procedure to register the 'Malone, PublicKeyToken=a35be5083775e042' assembly.
14:30:14 1148 Connecting to the application domain of the Add-in Express loader.
14:30:14 1148 Success.
14:30:14 1148 Loading the 'Malone, PublicKeyToken=a35be5083775e042' assembly.
14:30:14 1148 Success.
14:30:14 1148 Registering the 'Malone, PublicKeyToken=a35be5083775e042' assembly (user).
14:30:15 1148 The ' Malone, PublicKeyToken=a35be5083775e042' assembly has been registered successfully.
14:30:15 1148 The managed registration process is complete with HRESULT = 0.
14:30:15 1860 7000 The add-in registration process is completed with HRESULT = 0.
|
|
|
Eugene Astafiev
Guest
|
|
|
brian
Posts: 31
Joined: 2008-09-02
|
1. We do not
2. Huh! Somehow I missed that when we upgraded to 2010 ... registering adxloader.dll seemed to continue to work fine. However I just had the opportunity to finally have a meeting with this user and try the adxregistrator.exe utility, with the same result. Everything appears to be fine but there is no hint whatsoever of the add-in actually being installed. Very confusing! |
|
|
Eugene Astafiev
Guest
|
Hi Brian,
May I see the adxregistrator.exe utility from the problematic PC? Typically you can find it in the <My Documents>\Add-in Express folder. |
|
Forums
Topics
Search
Help
Login
Register