Automation of Outlook 2016 different from Outlook 2013

Occasional Visitor

A client of ours has started using Windows 10 with Office 2016. Previously they where on Windows 7 with Office 2013.  We now get "Automation server can't create object" errors on the desktops. The users don't have admin permissions on their desktops - which wasn't an issue before using Office 2016. Is there perhaps a policy setting (or something else) we can suggest to the client, that will allow our desktop scripts to create ActiveX objects from Office 2016?


To clarify, we run JScript code in a host application from where Outlook (and most other Office apps) are accessed, as part of business process automations.



0 Replies