Access violation when copying Outlook 2016 messages to UR via extension

[cnewtonne]

Thank you.
I tried using 5 different releases of riched20.dll/msptls including %windir% default ones. All of them produce same problem.

I appreciate that you took the time to test it in your lab. It is not conclusive, however, as to why it is crashing on mine.

What can be done to advance our troubleshooting for this failure. I do not see mso20win32client.dll in the folder location described in the message. It exists in C:\Program Files (x86)\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16

There are 2 files of same version, yet different sizes. Not sure why.

How do these files compare to your setup. Again, I'm using Windows 10 and Office 16 with latest updates for both.

Can UR be debugged? Can we trace its calls?

Thanks

[kinook]

Office uses some sort of weird virtual file system redirection for loading DLLs. One of the DLLs is 64-bit and the other is 32-bit. The versions/sizes of that file on my test system is:

Directory of C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16

05/26/2016 02:28 PM 3,469,568 Mso20win32client.dll

Version: 16.0.6925.1014


Directory of C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\OFFICE16

05/26/2016 02:23 PM 2,323,712 Mso20win32client.dll

Version: 16.0.6925.1014


I would guess that a recent Office update is the reason for the different behavior on your machine (I don't have automatic updates enabled on the test system).

The access violation is occurring in the Office DLL, not UR code that we could debug.

[cnewtonne]

Does not look like humanity at large has yet known of my issue. Googling 'Mso20win32client.dll 16.0.6925.1014' yields 0 hits

All I can find is this file got updated April 5, 2016, update for Office 2016 (KB3114535) Mso20win32client.dll 16.0.4366.1000

This is a major step in my daily workflow. Sad to see it broken like this. Change is hard specially at my age.

I'll keep an eye for future UR & Office updates. Hoping one day it will fix itself.

[cnewtonne]

Kinook ...
The error message says 'error processing command line'. What command line it is referring to?

What command line/API is it calling?

[kinook]

The UR Outlook add-in calls UR with a command-line flag of /linkoutlook or /copyoutlook.
http://www.kinook.com/UltraRecall/Ma...linesyntax.htm

UR then uses the MAPI & Outlook object model APIs to locate and process the selected Outlook item(s).

[cnewtonne]

So may be the Outlook 2016 API's or the object model got changed. UR may be using older version of the calls.

Not sure if Office 2016 guarantees backward comparability. Does it?

Thanks

[kinook]

I'm sure Microsoft wouldn't intentionally break an API in this way.