|
|
|
Josep Llort Tella
Posts: 34
Joined: 2012-01-18
|
Hi,
I have a problem my plug-in is not visible on some computers.
In the adxloader.log file, it tells me the error: 0x80131022
I have reviewed similar problems in the forum and proceeded to update version 9.4.44644 of the AddinExpress, how curious that the file 8.6.4408 still remains in the log file.
I hope your help, thanks.
Add-in Express Loader Log File: 01/17/2020 16:10:06:105
Startup directory: C:Users alentinaAppDataLocalOpenKMOKMOutlookAddIn
Loader version: 8.6.4408.0
Operating System: Microsoft Windows 10 Professional (build 18363), 64-bit
Process Owner: User
Command Line: "C:Program FilesMicrosoft Office
ootOffice16OUTLOOK.EXE"
Run 'As Administrator': No
Process Elevated: No
Integrity Level: Medium
UAC (User Account Control): On
------------------------------------------------------------------------
16:10:06:115 6980 13292 Start.
16:10:06:115 6980 13292 Creating a new instance of the add-in loader.
16:10:06:115 6980 13292 Loading mscoree.dll
16:10:06:115 6980 13292 Success.
16:10:06:115 6980 13292 Loading the configuration from the system registry.
16:10:06:115 6980 13292 Getting the latest CLR version.
16:10:06:115 6980 13292 The latest CLR version is 'v4.0.30319'.
16:10:06:115 6980 13292 The configuration has been loaded successfully.
16:10:06:115 6980 13292 Runtime version: v4.0.30319.
16:10:06:115 6980 13292 Assembly name: OpenKMOutlookAddIn.
16:10:06:115 6980 13292 Class name: OKMOutlookAddIn.AddinModule.
16:10:06:115 6980 13292 Registry key: CLSID{AE27ADC9-1254-4B80-A0D6-D3B5F4E7DF19}.
16:10:06:214 6980 13292 Attempting to create a new instance of the managed add-in class: CLR - v4.0.30319
16:10:06:214 6980 13292 Loading CLR: v4.0.30319.
16:10:06:214 6980 13292 Calling CLRCreateInstance method.
16:10:06:214 6980 13292 Success.
16:10:06:214 6980 13292 Calling GetRuntime method.
16:10:06:214 6980 13292 Success.
16:10:06:214 6980 13292 Checking if the hosting API of .NET Framework v4.0 beta is installed.
16:10:06:214 6980 13292 The hosting API is up to date.
16:10:06:214 6980 13292 Calling GetInterface method for the CorRuntimeHost interface.
16:10:06:214 6980 13292 Error code: 0x80131022
|
|
|
Posted 22 Jan, 2020 13:47:48
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18821
Joined: 2006-05-11
|
|
|
Posted 23 Jan, 2020 02:09:07
|
|
Top
|
|
|
Josep Llort Tella
Posts: 34
Joined: 2012-01-18
|
Hi Andrei,
I have done what I indicated:
On your machine, check out your project and make sure the loader files and manifest are writable. Then register the project and confirm replacing the loader. Once done, make sure your setup project deploys the new loader files and manifest (if it is updated).
Now I don't generate the adxloader.log but the addin is visible. This is correct?
Regards.
My development machine has a windows 7 sp1 and I use the .NET Framework 4.5.2 for the project. |
|
|
Posted 23 Jan, 2020 11:11:57
|
|
Top
|
|
|
Josep Llort Tella
Posts: 34
Joined: 2012-01-18
|
Ah, I learned that the route is now in: {user profile}\AppData\Local\Temp\<ProductName>\adxloader.log;
I will try now on the pc with windows10, to see if the problem persists or not. |
|
|
Posted 23 Jan, 2020 13:57:19
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18821
Joined: 2006-05-11
|
Hello Josep,
Josep Llort Tella writes:
Now I don't generate the adxloader.log but the addin is visible. This is correct?
I don't understand you, sorry.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 24 Jan, 2020 03:08:16
|
|
Top
|
|
|
Josep Llort Tella
Posts: 34
Joined: 2012-01-18
|
Solved, with the update to the latest version the add-in is registered correctly and it already works from outlook.
Thanks Andrei. |
|
|
Posted 30 Jan, 2020 10:02:13
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18821
Joined: 2006-05-11
|
You are welcome!
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 31 Jan, 2020 05:13:29
|
|
Top
|
|
Forums
Topics
Search
Help
Login
Register