Outlook 2007, adxloader.dll 8.7.4430 fails, calling SetDefaultStartupFlags method

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

Outlook 2007, adxloader.dll 8.7.4430 fails, calling SetDefaultStartupFlags method
Loading add-in into Outlook 2007 fails with a "parameter is incorrect" error when calling SetDefaultStartupFlags method, loader version: 8.7.4430.0 
Douglas Goodman


Guest


We are receiving customer-reported issues that the newest version of our add-in is failing to load in Outlook 2007. Our add-in is built with the latest version of Add-in Express 8.7.4430. This seems to happen on systems with Windows 7 and Outlook 2007 only. Is this a known issue in Outlook 2007? We weren't seeing this issue with 8.6.4408.0.

Adxloader.log below:

Add-in Express Loader Log File: 11/24/2017 09:42:40:243

Startup directory: C:\Users\XXXX\AppData\Local\XXXX\OutlookPlugin\
Loader version: 8.7.4430.0
Operating System: Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit
Process Owner: Administrator
Command Line: "C:\Program Files (x86)\Microsoft Office\Office12\OUTLOOK.EXE"
Run 'As Administrator': No
Process Elevated: No
Integrity Level: Medium
UAC (User Account Control): On
------------------------------------------------------------------------
09:42:40:243 14352 5304 Starting the add-in registration process.
09:42:40:243 14352 5304 Loading mscoree.dll
09:42:40:243 14352 5304 Getting the latest CLR version.
09:42:40:243 14352 5304 The latest CLR version is 'v4.0.30319'.
09:42:40:243 14352 5304 Loading CLR: v4.0.30319.
09:42:40:243 14352 5304 Calling CLRCreateInstance method.
09:42:40:243 14352 5304 Success.
09:42:40:243 14352 5304 Calling GetRuntime method.
09:42:40:243 14352 5304 Success.
09:42:40:243 14352 5304 Checking if the hosting API of .NET Framework v4.0 beta is installed.
09:42:40:243 14352 5304 The hosting API is up to date.
09:42:40:243 14352 5304 Calling SetDefaultStartupFlags method.
09:42:40:243 14352 5304 The parameter is incorrect.
Posted 27 Nov, 2017 11:36:04 Top
Andrei Smolin


Add-in Express team


Posts: 18830
Joined: 2006-05-11
Hello Douglas,

Please find out the add-in unchecking which in the COM Add-ins dialog prevents the issue from occurring.


Andrei Smolin
Add-in Express Team Leader
Posted 28 Nov, 2017 01:24:24 Top
Douglas Goodman


Guest


I'm not sure I follow what you mean. I don't currently have access to any of the PCs that were displaying the error.
Posted 28 Nov, 2017 08:18:55 Top
Andrei Smolin


Add-in Express team


Posts: 18830
Joined: 2006-05-11
Hello Douglas,

The issue is quite serious. I suggest that you turn off all of the other COM add-ins on an affected machine. Then, you turn them on one by one to find the add-in with which the issue is reproducible.

We need to know the name of the add-in as we (most probably) need to contact the vendor. For the time being, your only workaround is to turn that add-in off until we contact the vendor and find a solution with them.

You may prefer to discuss any details outside of the forum. If so, you can send us an email to the support email address; find it in {Add-in Express installation folder}\readme.txt; please make sure your email contains a link to this topic.


Andrei Smolin
Add-in Express Team Leader
Posted 28 Nov, 2017 08:38:27 Top
Douglas Goodman


Guest


We've already determined that our add-in is causing the error. We are the vendor. :)

I'm unable to repro this locally. We've only seen this in customer environments: Windows 7 and Outlook 2007.

I'll email you at the support email address.
Posted 28 Nov, 2017 08:45:48 Top
Andrei Smolin


Add-in Express team


Posts: 18830
Joined: 2006-05-11
Hello Douglas,

Douglas Goodman writes:
We've already determined that our add-in is causing the error. We are the vendor. :)


What I'm trying to tell is this: there's one more add-in that you need to turn off in order to let your add-in work.


Andrei Smolin
Add-in Express Team Leader
Posted 28 Nov, 2017 08:47:30 Top