Issue:
After logging into Outlook, an error is presented:
Microsoft.Exchange.Data.Directory.ADDriverStoreAccessNonLocalException
Afterwards, we notice that the account at the top has been changed from the email address to a MS BPOS/365 format.
Cause:
IMAP has been functioning with a local non-MS cloud login for about a year. After a MS Windows update, the next launch of Outlook "upgrades" the IMAP configuration to a MS cloud login (which doesn't exist).
(e.g. myadminid@mindwatering.net to MindwateringAdminID@mindwatering.onmicrosoft.com)
Of course, Outlook is now hardcoded to the new cloud account and although via Advanced Settings, IMAP can be selected, at the end, the email address for the IMAP login reverts to the MS login, and the IMAP server FQDN and outgoing SMTP server FQDN are both automatically updated so that the domains have the microsoft.cloud.url.suffix added to each.
The MS Bondage Option:
MS solution says to rename your cloud account, create a new alias for your cloud account to fix it, or the best suggestion, create a new OS login with a new MS cloud account and subscription. In other words, create a new MS cloud account which will set-up new email and leave all that mail behind, and enjoy your new account user bill to pay each month.
A web search shows this is actually a pretty common occurrence. They suggest:
Try 1. Reset the Outlook Launcher program olk.exe:
a. Close Outlook
b. Clear the local config:
- Windows key or Search --> cmd -->
> olk.exe --clearLocalState
This only clears the server config, but not the new MS cloud account it made up. Not helpful.
Try 2. Delete the olk config folder so it has to start over:
Warning:
If previously using POP, the next will wipe out -all- mail, and if your POP mail is set to download all mail (typically the default in a POP configuration), the mail is only on this workstation. Deleting the Olk folder will be very, very bad - all mail will be gone. Do not do this next step. However, if previously using IMAP, then all mail will still be on the server and just show back up after the new setup is done again.
a. Close Outlook
b. Bring up the local AppData folder to delete the Olk folder:
- Windows key or Search --> %LocalAppData% --> click folder results pop-up --> in the new folder --> Microsoft (folder) --> Olk (folder) -->
- We could back it up first, but it is corrupted, right-click, and Delete.
c. Relaunch Outlook
- Perform set-up like normal.
Hope this helps. It helped us just dodge the latest MS bullet.
previous page
|