

- #WORD CRASHES WHEN OPENING VB ENVIRONMENT HOW TO#
- #WORD CRASHES WHEN OPENING VB ENVIRONMENT CODE#
- #WORD CRASHES WHEN OPENING VB ENVIRONMENT LICENSE#
Since the users are on-prem AD (synced by AADC to AzureAD) we switched it to Org ID and the problem is gone. The first few versions of Excel (1.0 through 4.0) had a rudimentary macro programming capability using a programming language so embarassing that it never had a name, although it was sometimes called XLM (its file extension). It had been set for something entirely unrelated, but the GPO setting provides for 4 options: Microsoft ID, Org ID, Both or None. The setting is part of the ADMX for O365/2016, under Office 2016 / Miscellaneous / named "Block Signing into Office". Upon further testing, we found that there was a GPO setting in the environment blocking the SSO channel from passing the user creds to MS for verifying the license. If you think you're a noob though, look at the following line. Open on a computer with MS Office installed, then right-click on Microsoft Office document in files list pane and select Edit Document command in the context menu. Otherwise, you shouldn't be anywhere near a computer. Use our demo WebDAV server (or any Class 2 WebDAV server sample provided with SDK) to open, edit and save MS Office documents.
#WORD CRASHES WHEN OPENING VB ENVIRONMENT HOW TO#
The fault would mention the same memory offset ending with 6f8. Anyone using Windows (or even Mac users, if they have MS Word on their Mac) should know how to open it. I just downgraded the 8067.2115 version to previous version 7967.2161 and the same file open again perfectly.
#WORD CRASHES WHEN OPENING VB ENVIRONMENT CODE#
When I open an Excel xlsm file which includes VBA code Excel starts to open it and after about 10 seconds Excel crashes and the file is not opened.


#WORD CRASHES WHEN OPENING VB ENVIRONMENT LICENSE#
The installation would complete successfully, the user would open an app (Outlook, Word, etc.) and see it associate the logged on user with the app license at the top right of the form. We were going through a PoC project with a customer who kept having an issue with O365 PP apps crashing as soon as they're launched.
