B
bitmadmax
Guest
Useless context bit: I am currently in the process of replacing Office 2010 across our organisation with Office 2016 standard. We use on-premise Microsoft Exchange 2010 SP3 patched to update rollup 17, and are on a completely isolated network which is not on the Internet. However I have come across a big stumbling block.
The plea for help bit: On our Windows 10 machines, although Office installs fine and runs, Outlook 2016 does not open. I can open Outlook, the various fields are autocompleted and I get the 3 ticks and confirmation the email account was configured and is ready for use. Outlook then starts to load but immediately fails with the message "cannot start microsoft outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file c:\users\xxx\appdata\local\microsoft\outlook\xxx@domain.internal.ost is not an outlook data file (.ost)."
SO, when I look at the .ost in question it is zero bytes in size. So I modify the profile using the Mail tool in control panel and disable cached mode. When loading outlook this time I now get the error "cannot start microsoft outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft exchange has failed".
WHen I install Office 2016 on a Windows 7 Pro machine, Outlook connects and opens just file, so it seems for whatever reason Outlook 2016 just won't open on Windows 10.
I have checked (as far as I can) that autodiscover is configured and working properly. DNS is working properly and I can resolve the autodiscover and hostnames of our Exchange server from affected machines.
Things I have tried so far unsuccessfully:
Rebooted Exchange server
Starting Outlook in safe mode
Run outlook with DefConnectOps = 0 regkey enabled
Starting outlook with the resetnavpane option
Running outlook in Compatibility mode
Running outlook with the RPC fallback registry key enabled
Running SFC /Scannow (even though these are fresh builds)
Making sure client PC has "dummy" default gateway set (we are air gapped from the Internet so any IP can be used)
Detach and re-attaching the mailbox of an affected user
Created a brand new user with a fresh mailbox
Used a fresh install of Windows 10 Enterprise x64 (we are using LTSB 2015 version) -not domain joined, no group policies applied, no Antivirus, tried both unpatched and patched on a hyper-v VM with nothing but NIC drivers.
I have enabled extended outlook logging but when I try opening the .ETL files generated there doesn't appear to be any verbose, just informational error codes
I have googled the hell out of this issue and although there are similar errors, none of which seem to relate to this specific issue I'm having.
As I say, the only commonality I can see is some issue with Windows 10.
Would really appreciate any pointers.. thanks chaps!
Continue reading...
The plea for help bit: On our Windows 10 machines, although Office installs fine and runs, Outlook 2016 does not open. I can open Outlook, the various fields are autocompleted and I get the 3 ticks and confirmation the email account was configured and is ready for use. Outlook then starts to load but immediately fails with the message "cannot start microsoft outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file c:\users\xxx\appdata\local\microsoft\outlook\xxx@domain.internal.ost is not an outlook data file (.ost)."
SO, when I look at the .ost in question it is zero bytes in size. So I modify the profile using the Mail tool in control panel and disable cached mode. When loading outlook this time I now get the error "cannot start microsoft outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft exchange has failed".
WHen I install Office 2016 on a Windows 7 Pro machine, Outlook connects and opens just file, so it seems for whatever reason Outlook 2016 just won't open on Windows 10.
I have checked (as far as I can) that autodiscover is configured and working properly. DNS is working properly and I can resolve the autodiscover and hostnames of our Exchange server from affected machines.
Things I have tried so far unsuccessfully:
Rebooted Exchange server
Starting Outlook in safe mode
Run outlook with DefConnectOps = 0 regkey enabled
Starting outlook with the resetnavpane option
Running outlook in Compatibility mode
Running outlook with the RPC fallback registry key enabled
Running SFC /Scannow (even though these are fresh builds)
Making sure client PC has "dummy" default gateway set (we are air gapped from the Internet so any IP can be used)
Detach and re-attaching the mailbox of an affected user
Created a brand new user with a fresh mailbox
Used a fresh install of Windows 10 Enterprise x64 (we are using LTSB 2015 version) -not domain joined, no group policies applied, no Antivirus, tried both unpatched and patched on a hyper-v VM with nothing but NIC drivers.
I have enabled extended outlook logging but when I try opening the .ETL files generated there doesn't appear to be any verbose, just informational error codes
I have googled the hell out of this issue and although there are similar errors, none of which seem to relate to this specific issue I'm having.
As I say, the only commonality I can see is some issue with Windows 10.
Would really appreciate any pointers.. thanks chaps!
Continue reading...
