mscoree.dll as location instead of adxloader.dll

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

mscoree.dll as location instead of adxloader.dll
 
Catherine Levis


Guest


We are experiencing issues with writing to files from our add-in. User preferences are stored in a file that gets saved to a directory in the roaming appdata directory. However, they aren't getting written in the case of this issue, and we have found that the one thing all of these "bad installs" have in common is that mscoree.dll is the location of the add-in instead of adxloader.dll.

I have looked over logs from bad installs vs. good installs and they are completely the same. In a few rare cases, reinstalling Office completely has solved the issue but that's far from an ideal workaround and has not consistently solved the bug.

Any help would be greatly appreciated, thank you!
Posted 02 Oct, 2018 08:43:48 Top
Andrei Smolin


Add-in Express team


Posts: 18825
Joined: 2006-05-11
Hello Catherine,

Make sure that you deploy adxloader.dll, adxloader64.dll, and adxloader.dll.manifest along with other files of your add-in. Also, look in adxregistrator.log: are there any issues in it?


Andrei Smolin
Add-in Express Team Leader
Posted 02 Oct, 2018 09:19:38 Top
Catherine Levis


Guest


No issues with adxregistrator.log, all of them look the same and the command line is the same. The add-in works inside of Office for all of the people who are having this issue, the only thing that's not working in the error case is that it will not write this info to our custom preferences files.

Just in case I'm missing something, here is an adxregistrator.log from an error case:

Add-in Express Registrator Log File: 10/01/2018 15:10:31

Installation directory: C:\Windows\Installer\
Registrator version: 8.2.4371.0
Operating System: Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit
Process Owner: Administrator
Command Line: "C:\Windows\Installer\MSI162D.tmp" /install="C:\Program Files (x86)\DocFinity Office Integration\DocFinity.OfficeIntegration.dll" /privileges=admin /returnExitCode=false
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): On
--------------------------------------------------------------
15:10:31 0204 Starting the add-in registration process.
15:10:31 0204 Loading mscoree.dll
15:10:31 0204 Success.
15:10:31 0204 .NET Framework installation directory:
15:10:31 0204 The latest version of .NET Framework: 'v4.0.30319'
15:10:31 0204 Loading CLR: v4.0.30319.
15:10:31 0204 Calling CLRCreateInstance method.
15:10:31 0204 Success.
15:10:31 0204 Calling GetRuntime method.
15:10:31 0204 Success.
15:10:31 0204 Checking if the hosting API of .NET Framework v4.0 beta is installed.
15:10:31 0204 The hosting API is up to date.
15:10:31 0204 Calling GetInterface method for the CorRuntimeHost interface.
15:10:31 0204 Success.
15:10:31 0204 Starting CLR...
15:10:31 0204 Success.
15:10:31 0204 Getting the CLR version.
15:10:31 0204 The CLR v4.0.30319 has been initialized successfully.
15:10:31 0204 Creating a new domain setup.
15:10:31 0204 Success.
15:10:31 0204 The 'shadow copy' is disabled.
15:10:31 0204 Creating a new application domain.
15:10:31 0204 Success.
15:10:31 0204 Getting the base directory for the domain.
15:10:31 0204 Success. The directory is 'C:\Program Files (x86)\DocFinity Office Integration\'.
15:10:31 0204 Searching for the Add-in Express core library.
15:10:31 0204 Success. The 'AddinExpress.MSO.2005.dll' file is found.
15:10:31 0204 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
15:10:31 0204 Assembly identity is 'AddinExpress.MSO.2005'.
15:10:31 0204 Success.
15:10:31 0204 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
15:10:31 0204 Success.
15:10:31 0204 Calling the managed registration procedure (DISPID = 1610743823).
15:10:35 0204 Success.
15:10:35 0204 The add-in registration process is completed with HRESULT = 0.
Posted 02 Oct, 2018 09:26:46 Top
Andrei Smolin


Add-in Express team


Posts: 18825
Joined: 2006-05-11
Hello Catherine,

I suppose the issue may relate to an older loader version. I suggest that you install 8.9. Then make sure that your add-in project uses assemblies of that version and your setup project deploys files that version provides.


Andrei Smolin
Add-in Express Team Leader
Posted 02 Oct, 2018 09:49:19 Top
Catherine Levis


Guest


We have just upgraded to 8.9 and are seeing no change on the affected machines. mscoree.dll still as the location. In addition, log files are no longer getting updated after the update.

I've checked the manifest, have edited logFileLocation to try and get it to put them somewhere else, and none of that seems to work. All .dlls are updated and the redistributables are all put in their correct locations, and our installer builds just fine.

In summation, we are still seeing the original issue and now we don't have any log files with 8.9.4453, but otherwise the application runs fine.
Posted 03 Oct, 2018 09:50:58 Top
Andrei Smolin


Add-in Express team


Posts: 18825
Joined: 2006-05-11
Hello Catherine,

In 8.9 and above, the default log location is moved to {user profile}\AppData\Local\Temp\<ProductName>\adxloader.log; the ProductName part reflects the ProductName field of AssemblyInfo.cs (AssemblyInfo.vb).

Please confirm that you deploy adxloader.dll, adxloader64.dll, and adxloader.dll.manifest to the installation folder of your add-in.

Can I install your add-in? If yes, please send me a link to the support email address; see {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 03 Oct, 2018 10:16:09 Top
Catherine Levis


Guest


Here is the new adxregistrator log from a problem machine:

Installation directory: C:\Windows\Installer\
Registrator version: 8.9.4453.0
Operating System: Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit
Process Owner: Administrator
Command Line: "C:\Windows\Installer\MSI6750.tmp" /install="C:\Program Files (x86)\DocFinity Office Integration\DocFinity.OfficeIntegration.dll" /privileges=admin /returnExitCode=false
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): On
--------------------------------------------------------------
10:46:25 0188 Starting the add-in registration process.
10:46:25 0188 Loading mscoree.dll
10:46:25 0188 Success.
10:46:25 0188 .NET Framework installation directory:
10:46:25 0188 The latest version of .NET Framework: 'v4.0.30319'
10:46:25 0188 Loading CLR: v4.0.30319.
10:46:25 0188 Calling CLRCreateInstance method.
10:46:25 0188 Success.
10:46:25 0188 Calling GetRuntime method.
10:46:25 0188 Success.
10:46:25 0188 Checking if the hosting API of .NET Framework v4.0 beta is installed.
10:46:26 0188 The hosting API is up to date.
10:46:26 0188 Calling GetInterface method for the CorRuntimeHost interface.
10:46:26 0188 Success.
10:46:26 0188 Starting CLR...
10:46:26 0188 Success.
10:46:26 0188 Getting the CLR version.
10:46:26 0188 The CLR v4.0.30319 has been initialized successfully.
10:46:26 0188 Creating a new domain setup.
10:46:26 0188 Success.
10:46:26 0188 The 'shadow copy' is disabled.
10:46:26 0188 Creating a new application domain.
10:46:26 0188 Success.
10:46:26 0188 Getting the base directory for the domain.
10:46:26 0188 Success. The directory is 'C:\Program Files (x86)\DocFinity Office Integration\'.
10:46:26 0188 Searching for the Add-in Express core library.
10:46:26 0188 Success. The 'AddinExpress.MSO.2005.dll' file is found.
10:46:26 0188 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
10:46:26 0188 Assembly identity is 'AddinExpress.MSO.2005'.
10:46:26 0188 Success.
10:46:26 0188 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
10:46:26 0188 Success.
10:46:26 0188 Calling the managed registration procedure (DISPID = 1610743823).
10:46:29 0708 32 bits. The 'HKLM\Software\Microsoft\Office\Word\AddIns\DocFinity.OfficeIntegration.AddinModule' registry key was created successfully for the 'DocFinity.OfficeIntegration.AddinModule' class: LoadBehavior=3
10:46:29 0708 32 bits. The 'HKLM\Software\Microsoft\Office\Outlook\AddIns\DocFinity.OfficeIntegration.AddinModule' registry key was created successfully for the 'DocFinity.OfficeIntegration.AddinModule' class: LoadBehavior=3
10:46:29 0708 32 bits. The 'HKCR\CLSID\{7c1d4330-fe00-4a1c-923c-a37dec89805b}\InprocServer32' registry key was created successfully for the 'DocFinity.OfficeIntegration.AddinModule' class: C:\Program Files (x86)\DocFinity Office Integration\adxloader.dll
10:46:29 0708 64 bits. The 'HKLM\Software\Microsoft\Office\Word\AddIns\DocFinity.OfficeIntegration.AddinModule' registry key was created successfully for the 'DocFinity.OfficeIntegration.AddinModule' class: LoadBehavior=3
10:46:29 0708 64 bits. The 'HKLM\Software\Microsoft\Office\Outlook\AddIns\DocFinity.OfficeIntegration.AddinModule' registry key was created successfully for the 'DocFinity.OfficeIntegration.AddinModule' class: LoadBehavior=3
10:46:29 0708 64 bits. The 'HKCR\CLSID\{7c1d4330-fe00-4a1c-923c-a37dec89805b}\InprocServer32' registry key was created successfully for the 'DocFinity.OfficeIntegration.AddinModule' class: mscoree.dll
10:46:30 0188 Registration success.
10:46:30 0188 The add-in registration process is completed with HRESULT = 0.
Posted 04 Oct, 2018 12:22:51 Top
Andrei Smolin


Add-in Express team


Posts: 18825
Joined: 2006-05-11
Hello Catherine,

Thank you. The log looks perfectly okay.

I asked more questions in my previous post. Could you please answer them?

Also, I wonder if you ever switched your add-in from per-user to per-machine or back. In other words, can there exist your add-in's registry keys in HKCU (the log above shows creating keys in HKLM only)? Or, maybe, you renamed your add-in's ProgID?


Andrei Smolin
Add-in Express Team Leader
Posted 05 Oct, 2018 04:36:30 Top
Catherine Levis


Guest


Sorry, was waiting on an answer to see if we could send an installer. Emailing you now.

Have confirmed with both working machines and problem machines that the .dlls and the manifest files are in the installation directory.
Posted 05 Oct, 2018 08:45:45 Top
Andrei Smolin


Add-in Express team


Posts: 18825
Joined: 2006-05-11
Hello Catherine,

I've signed and sent the NDA to you guys.


Andrei Smolin
Add-in Express Team Leader
Posted 08 Oct, 2018 07:27:53 Top