So we created a new mailbox policy with an unlimited value for this setting, applied it to his mailbox and presto! Conversation History was working. We ended up opening a case with Microsoft and, to summarize, the issue is that our user had so many folders and nested folders that it hit a maximum set in the “EWSFindCountLimit” setting. Finally some proof that EWS was rejecting his connections. What value this utility actually provides is anyone’s guess but to use it you have to log in directly against EWS. I had him try to connect with this (pointless?) little utility from Microsoft – the Lync Conversation Analyzer. Our Exchange Admin correctly pointed out that if EWS wasn’t working for him then pretty much all of Outlook wouldn’t be working for him.Īs time passed and we got more desperate.
I kept coming back to the thought that Exchange Web Services (EWS) weren’t working for him.
But he was persistent and kept pushing us to find a solution. He was extremely patient and very helpful in our long, long period of troubleshooting. We had an end user who politely insisted that we get his Conversation History working.
