Newsletter Archives
-
Reports that this month’s Outlook update knocks out Search via Exchange Server
I’ve seen several reports along this line, from u/leaker929 on Reddit:
Over the weekend Outlook updated version 2004 build 12730.20236 and now they have 2 issues. They can’t adjust the reading pane widths. You can move them but they snap back. The search is also broken – says they are offline. Mine also updated but I am not having these issues. Repair did not help nor did rebuilding the index.
Then there’s this from u/itechniker also on Reddit:
today some customers reported that their Outlook search is not working.
They have Outlook 2016 and using Exchange 2016 accounts with enabled Exchange Cache Mode.
If you want to use the search bar, a yellow bar pops up with the text:”Something Went Wrong And Your Search Couldn’t Be Completed”, if you search shared mailboxes which are not cached (only online) then the search is working – if not restart the Windows Search service.
In the result area there is a link to “search only locally” and above there is the text “There is a problem with your network connection”, this search is working, but only for the cached items. OWA Search is also working without problems.
The latter poster says that reverting to build 12624.20466 clears up the problem — but not for everyone.
Further discussion on that thread says that disabling and re-enabling cached Exchange Mode also fixes the problem — but that doesn’t work for everyone.
Looks like the bug also bites Office 365.
-
Patch Lady – seeing Outlook authentication issues
On a private facebook group and on this thread in a Microsoft forum I’ve been seeing issues where Outlook via Office 365 is having issues authenticating. I’m not quite sure of the trigger. I don’t think it’s due to updates. But the symptoms are that suddenly Outlook can’t authenticate and an error message that references a trusted platform module
“”something went wrong” error that Trusted Platform Module has malfunctioned, error code 80090016. The server message is “Keyset does not exist Keyset does not exist”
There are a couple of ways around the issue.
- Build a new profile. Icky but it works.
- Enable multi factor authentication (which is wise to do anyway)
- Clear out the TPM chip cache (it appears some corruption is occurring which messes up the authentication)
- Or use this registry setting:
Shut down Outlook and set the following registry key. (Disables modern authentication)
HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\
REG_DWORD
EnableADAL
0 -
Another botched Microsoft patch: Office 365 ProPlus says ‘Something went wrong’
The second bad Office 365 patch in two months – and it locked out Office 365 customers for 12 days.
If you paid for Office 365, and couldn’t use it for 12 days, you should be steamed.
InfoWorld Tech Watch.