Posts 1 - 10 of 13
First | Prev. | 1 2 | Next | Last
|
|
|
|
Warren Wander
Posts: 22
Joined: 2014-10-24
|
Hi, a number of my clients are now getting the unknown version error in the Outlook Security Manager.
I'm using the latest ActiveX version of the OSM on your download site (dated 8 Dec, 2019).
They are on the following versions of Office 365 32-bit
Version 2008 (Build 13127.20408 Click-to-Run).
Current Channel
The version as shown in the "About Outlook" screen is shown as "16.0.13127.20266"
Do you have a time-scale for supporting the above? |
|
|
Posted 25 Sep, 2020 09:48:25
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Warren,
What is the exact error? Please provide a screenshot (if possible).
Warren Wander writes:
Do you have a time-scale for supporting the above?
No, at the moment we don't. I need to find out what the issue is.
Do you have any more details? Do you use the Excel object model or Simple MAPI in your code?
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 25 Sep, 2020 12:00:28
|
|
Top
|
|
|
Warren Wander
Posts: 22
Joined: 2014-10-24
|
Hello Andrei,
We don't use the Excel object model when calling from Access but we do we use Simple MAPI code.
The code is called from VBA within Access and does the following:
1. Create an instance of "AddInExpress.OutlookSecurityManager"
2. Get the running instance of Outlook.
3. Only if both objects exist does the code proceed further.
4. Call the Outlook Security Manager ConnectTo method passing in the Outlook object.
5. Call the Check method of the Outlook Security Manger twice, passing in 2 to check for SimpleMAPI and then passing in 1 as the parameter to check for CDO.
6. If either of those two calls to the Check method return "osmUnknownOlVersion" our error message reports that Outlook Security Manager has returned then a message about an unknown version of Outlook is shown on the user's computer which is what we are seeing on the client PCs.
Thanks |
|
|
Posted 28 Sep, 2020 05:15:22
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Warren,
In a couple of minutes I'll send you an email containing a link to the secman.dll that fixes this issue for us. Please let me know if it fixes the issue for you.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 28 Sep, 2020 05:56:46
|
|
Top
|
|
|
Warren Wander
Posts: 22
Joined: 2014-10-24
|
Hello Andrei
It did fix the issue for users who had reported getting the issue.
Do you know when there will be a release with your fix in it?
Thanks |
|
|
Posted 29 Sep, 2020 04:48:05
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Warren,
Alas, the ETA isn't available in the moment. When we publish such a build, I'll post a note here.
To all,
If you need this fix, post a note here or write us to the support email address using the contact form at https://www.add-in-express.com/support/askus.php.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 29 Sep, 2020 05:11:36
|
|
Top
|
|
|
Warren Wander
Posts: 22
Joined: 2014-10-24
|
Hi Andrei, thanks for the above, which worked - for a small amount of time, unfortunately we have a client that's now reporting 16.0.13231.20110 as the Outlook version and OSM is again reporting an unknown version.
With MS releasing new version of Outlook (Office 365) every couple of weeks, this method of (temporarily) disabling the security warning is become unmaintainable, leading to three questions...
1. How are your other clients getting around this issue, is it not arising for them?
2. Can we either just ignore this call to "Check" the version of Outlook, or ignore the osmUnknownOlVersion error - and try to disable the security as before?
3. Would it be possible/feasible to have the OSM component be less "picky" about the Outlook version and, say, report all 16.0.* versions as ok? Obviously if there were major changes to Outlook and the process failed there would be an issue - but is this a better situation than me having to disturb you whenever there's a minor Outlook update!
Many thanks |
|
|
Posted 13 Oct, 2020 09:36:19
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Warren,
This issue is raised to all of the clients who use that build. Ignoring the Check doesn't make sense: if the Check doesn't work, the Disable won't work either. Unfortunately, it is impossible to bypass this restriction.
What Office channel are you using? See the area to the right of the About Outlook button in the File | Office Account page.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 14 Oct, 2020 06:43:23
|
|
Top
|
|
|
Warren Wander
Posts: 22
Joined: 2014-10-24
|
|
Apologies Andrei, took me a little while to get in touch with our client. Their "initial" About window shows Version 2009 (Build 13231.20390 Click-to-Run) Current Channel, and the "detailed" About window says Outlook 2016 MSO, 16.0.13231.20110 32-bit. |
|
|
Posted 22 Oct, 2020 08:09:05
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Warren,
I've tested the latest secman.dll on that Office build: it works for me. What secman.dll version do you deploy to the customer?
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 23 Oct, 2020 04:52:05
|
|
Top
|
|
|
Posts 1 - 10 of 13
First | Prev. | 1 2 | Next | Last
|
Forums
Topics
Search
Help
Login
Register