Add-In does not stay active

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

Forums

Topics

Help

Add-in Express blogs

Add-in Express forums > Add-in Express for .net and VSTO forum

Add-In does not stay active

Posts 1 - 10 of 11
First | Prev. | 1 2 | Next | Last

Amit B

Guest

We have some users who are stating that their Add-In does not stay active after they shuts down Excel and they have to go and reactivate it each time after opening the excel session.

Most of that have multiple excel environments (2010, 2013) / (2010, 2016)

We have not faced any such issue in our test environment but it started coming in production.

Just for your information, everything was running smoothly until last month where they were on previous adx version 7.
Since they asked for 2016 support so we bought new adx licenses (version 8) and packaged it. That was the only major change which we did.

I have 2 questions for you ?В?Р?г
1. Are there any other customers reporting similar issue with new adx upgrade?
2. Can you tell us in which direction we should start investigating or what further details/logs you would need from me?

Thanks,
Amit B

Posted 24 Oct, 2016 08:22:28

Top

Andrei Smolin

Add-in Express team

Posts: 18830
Joined: 2006-05-11

Hello Amit,

#1. No.

Is adxloader.log created when this occurs? If yes, does it contain an indication of an error?

Andrei Smolin
Add-in Express Team Leader

Posted 24 Oct, 2016 08:29:36

Top

Amit B

Guest

Hello Andrei,

adxloader.log file was not in the folder 'C:\Users\?В?Р?иUser ID?В?Р?й\Documents\Add-in Express'. Could it be that since the load behavior was set to ?В?Р?иUnloaded?В?Р?й, the load logs would not be created? Although as per adxregistrator log, registration is successful (see below).

Is there any other place where I need to look upon.

08:28:35 0240 Starting the add-in registration process.
08:28:35 0240 Loading mscoree.dll
08:28:35 0240 Success.
08:28:35 0240 .NET Framework installation directory:
08:28:35 0240 The latest version of .NET Framework: 'v4.0.30319'
08:28:35 0240 Loading CLR: v4.0.30319.
08:28:35 0240 Calling CLRCreateInstance method.
08:28:35 0240 Success.
08:28:35 0240 Calling GetRuntime method.
08:28:35 0240 Success.
08:28:35 0240 Checking if the hosting API of .NET Framework v4.0 beta is installed.
08:28:35 0240 The hosting API is up to date.
08:28:35 0240 Calling GetInterface method for the CorRuntimeHost interface.
08:28:35 0240 Success.
08:28:35 0240 Starting CLR...
08:28:35 0240 Success.
08:28:35 0240 Getting the CLR version.
08:28:35 0240 The CLR v4.0.30319 has been initialized successfully.
08:28:35 0240 Creating a new domain setup.
08:28:35 0240 Success.
08:28:35 0240 Getting the add-in directory.
08:28:35 0240 Success. The directory is 'C:\Program Files (x86)\*****\'
08:28:35 0240 The 'shadow copy' is disabled.
08:28:35 0240 Creating a new application domain.
08:28:35 0240 Success.
08:28:35 0240 Getting the base directory for the domain.
08:28:35 0240 Success. The directory is 'C:\Program Files (x86)\Apparity Client\'.
08:28:35 0240 Searching for the Add-in Express core library.
08:28:35 0240 Success. The 'AddinExpress.MSO.2005.dll' file is found.
08:28:35 0240 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
08:28:35 0240 Assembly identity is 'AddinExpress.MSO.2005'.
08:28:35 0240 Success.
08:28:35 0240 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
08:28:35 0240 Success.
08:28:35 0240 Calling the managed registration procedure (DISPID = 1610743823).
08:28:38 0240 Success.
08:28:38 0240 The add-in registration process is completed with HRESULT = 0.

Posted 24 Oct, 2016 14:51:11

Top

Amit B

Guest

I also want to mention that load behavior of our plugin is 'load on startup' by default. But as per user, the plugin is not loading on startup. So is it possible that logs were not generated because of this?

Posted 24 Oct, 2016 15:01:55

Top

Andrei Smolin

Add-in Express team

Posts: 18830
Joined: 2006-05-11

Amit,

The loader not created means the add-in didn't even start to load.

Could you load the add-in using the COM add-ins dialog and send me (or post here) adxloader.log?

Andrei Smolin
Add-in Express Team Leader

Posted 25 Oct, 2016 06:04:16

Top

Amit B

Guest

The production user 'Load Behavior' is set to Unloaded. He can still use plugin but manually enabling the plugin after opening excel. But on doing this adxloader.log was not generated on his machine.

But we have 1 machine in our test environment where same issue is now reproducible and adxloader log was also generated.
Please find the log file below.

Moving forward, is it possible for you to give me your direct email address?

*********************************************************************************
Add-in Express Loader Log File: 10/26/2016 10:11:17:490

Startup directory: C:\Program Files (x86)\****\
Loader version: 8.2.4371.0
Operating System: Microsoft Windows 10 Professional (build 14393), 64-bit
Process Owner: Administrator
Command Line: "C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE" /dde
Run 'As Administrator': No
Process Elevated: No
Integrity Level: Medium
UAC (User Account Control): On
------------------------------------------------------------------------
10:11:17:497 1988 8124 Start.
10:11:17:497 1988 8124 Creating a new instance of the add-in loader.
10:11:17:497 1988 8124 Loading mscoree.dll
10:11:17:500 1988 8124 Success.
10:11:17:500 1988 8124 Loading the configuration from the system registry.
10:11:17:500 1988 8124 Getting the latest CLR version.
10:11:17:501 1988 8124 The latest CLR version is 'v4.0.30319'.
10:11:17:501 1988 8124 The configuration has been loaded successfully.
10:11:17:501 1988 8124 Runtime version: v4.0.30319.
10:11:17:501 1988 8124 Assembly name: ****, PublicKeyToken=36D6DE9C030E9182.
10:11:17:501 1988 8124 Class name: ****.AddinModule.
10:11:17:501 1988 8124 Registry key: CLSID\{F44EB779-26E0-4272-B0D3-001F6548BDB1}.
10:11:17:501 1988 8124 Attempting to create a new instance of the managed add-in class: CLR - v4.0.30319
10:11:17:501 1988 8124 Loading CLR: v4.0.30319.
10:11:17:501 1988 8124 Calling CLRCreateInstance method.
10:11:17:501 1988 8124 Success.
10:11:17:501 1988 8124 Calling GetRuntime method.
10:11:17:502 1988 8124 Success.
10:11:17:502 1988 8124 Checking if the hosting API of .NET Framework v4.0 beta is installed.
10:11:17:514 1988 8124 The hosting API is up to date.
10:11:17:515 1988 8124 Calling GetInterface method for the CorRuntimeHost interface.
10:11:17:515 1988 8124 Success.
10:11:17:515 1988 8124 Starting CLR...
10:11:17:515 1988 8124 Success.
10:11:17:515 1988 8124 Getting the CLR version.
10:11:17:515 1988 8124 The CLR v4.0.30319 has been initialized successfully.
10:11:17:515 1988 8124 Creating a new domain setup.
10:11:17:520 1988 8124 Success.
10:11:17:521 1988 8124 Getting the add-in directory.
10:11:17:521 1988 8124 Success. The directory is 'C:\Program Files (x86)\****\'
10:11:17:522 1988 8124 The configuration file is 'C:\Program Files (x86)\****\app.config'
10:11:17:522 1988 8124 The 'shadow copy' is enabled.
10:11:17:522 1988 8124 Creating a new application domain.
10:11:17:535 1988 8124 Success.
10:11:17:535 1988 8124 Creating an instance of the managed class. Assembly identity: '****, PublicKeyToken=36D6DE9C030E9182'
10:11:20:768 1988 8124 Success.
10:11:20:768 1988 8124 Unwrapping the managed class.
10:11:21:366 1988 8124 Success.
10:11:21:366 1988 8124 Querying the add-in extensibility.
10:11:21:366 1988 8124 Success.
10:11:21:366 1988 8124 Querying the custom task panes.
10:11:21:366 1988 8124 Success.
10:11:21:366 1988 8124 Querying the ribbon extensibility.
10:11:21:366 1988 8124 Success.
10:11:21:366 1988 8124 Querying the form regions.
10:11:21:367 1988 8124 Success.
10:11:21:367 1988 8124 Querying the encryption provider.
10:11:21:367 1988 8124 The 'EncryptionProvider' interface is not supported.
10:11:21:367 1988 8124 Getting the dispid of the 'Dispose' method.
10:11:21:372 1988 8124 Success.
10:11:21:372 1988 8124 The instance of the managed add-in class has been created successfully.

Posted 26 Oct, 2016 15:30:21

Top

Andrei Smolin

Add-in Express team

Posts: 18830
Joined: 2006-05-11

Hello Amit,

Amit B writes:
The instance of the managed add-in class has been created successfully.

This record in adxloader.log means the loader haven't encountered any problem while loading the add-in assembly in the AppDomain and creating an instance of the add-in module. If loading the add-in produces such a record and the add-in still is marked as unloaded, this is an indication of an exception which occurs on a later stage; say, when handling an event of the add-in module. If this is the case, you need to debug the add-in project. Say, you can add a number of debug messages to your code; use System.Diagnostics.Debug.WriteLine(). You collect the messages at run time using DebugView (see http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx).

If you don't have such a record in adxloader.log, then the log should indicate an exception or warning which prevented the add-in from loading.

If adxloader.log isn't created at all, please let me know.

You can send me your questions to the support email address; see {Add-in Express installation folder}\readme.txt.

Andrei Smolin
Add-in Express Team Leader

Posted 27 Oct, 2016 05:39:12

Top

Amit B

Guest

Andrei Smolin writes:
This record in adxloader.log means the loader haven't encountered any problem while loading the add-in assembly in the AppDomain and creating an instance of the add-in module. If loading the add-in produces such a record and the add-in still is marked as unloaded, this is an indication of an exception which occurs on a later stage; say, when handling an event of the add-in module.

This is great piece of information. I will look into it since it is happening on our test machine so I can easily troubleshoot it.

Machine where no adxloader.log is getting generated is happening for only 1 production user. Since I can't pull much information from him so we just recommended their IT support to go for uninstall and reinstall of the product. If problem still persist then I will let you know.

Thanks for your help.

Posted 27 Oct, 2016 07:40:38

Top

Andrei Smolin

Add-in Express team

Posts: 18830
Joined: 2006-05-11

Amit B writes:
Since I can't pull much information from him so we just recommended their IT support to go for uninstall and reinstall of the product.

I suggest that you collect adxregistrator.log after installing the add-in and adxloader.log after starting the host application for the first time.

Andrei Smolin
Add-in Express Team Leader

Posted 27 Oct, 2016 07:53:58

Top

Amit B

Guest

Andrei,
I attached the adxregistrator logs from the production user machine in post 3.
And he mentioned that after loading the addin manually there was no adxloader log generated but he can still use plugin.

Amit B writes:
The production user 'Load Behavior' is set to Unloaded. He can still use plugin but manually enabling the plugin after opening excel. But on doing this adxloader.log was not generated on his machine.

Posted 27 Oct, 2016 08:05:59

Top

Posts 1 - 10 of 11
First | Prev. | 1 2 | Next | Last