I have an add-in created in VB6. I recently updated to Office 365 and Outlook 16 (10.0.6741.2071). I run Windows 7. Now my add-in has stopped loading. The message is:
"Not loaded. A runtime error occurred during the loading of the COM Add-in."
But, a little more information...
There is a development version of the add-in and a production version. Yesterday as I was starting this request, I went to get the error message to ensure it was word-for-word. Imagine my joy, confusion & annoyance when the add-in loaded and ran. Even in the VB6 IDE mode so I could debug it. There before my eyes was the development version running. I quickly told everyone that the issue had resolved itself - bad mistake!
Today I switched to the production version so I could run against a production database. This involves: unregistering the development version, checking the registry to ensure that was effective, then registering the production version. All that seemed to work perfectly. The add-in connection class pointed to the correct DLL. But, Outlook loaded the development version. The description was the production version's but the path was to the development version. I checked the registry for the add-in. All entries that I could read (ie not binary) were to the production version. I even tried deleting binary ones, just to be sure. Didn't help.
I tried hiding the development version - Outlook didn't like that.
Has anyone experienced this? I realise that this is a legacy add-in, but it's still a viable item (or is it?). If you know where Outlook is getting its add-in path from that would be appreciated.
Thanks,
Jef Lee, Perth, Western Australia.
"Not loaded. A runtime error occurred during the loading of the COM Add-in."
But, a little more information...
There is a development version of the add-in and a production version. Yesterday as I was starting this request, I went to get the error message to ensure it was word-for-word. Imagine my joy, confusion & annoyance when the add-in loaded and ran. Even in the VB6 IDE mode so I could debug it. There before my eyes was the development version running. I quickly told everyone that the issue had resolved itself - bad mistake!
Today I switched to the production version so I could run against a production database. This involves: unregistering the development version, checking the registry to ensure that was effective, then registering the production version. All that seemed to work perfectly. The add-in connection class pointed to the correct DLL. But, Outlook loaded the development version. The description was the production version's but the path was to the development version. I checked the registry for the add-in. All entries that I could read (ie not binary) were to the production version. I even tried deleting binary ones, just to be sure. Didn't help.
I tried hiding the development version - Outlook didn't like that.
Has anyone experienced this? I realise that this is a legacy add-in, but it's still a viable item (or is it?). If you know where Outlook is getting its add-in path from that would be appreciated.
Thanks,
Jef Lee, Perth, Western Australia.