Storage service had an ews autodiscovery failure.
Storage service had an oauth authentication failure.
Well apparently these event errors don t disappear with the change but it does resolve the oauth issue and i do get to have server side conversation history working with the skype for business mobile client for a skype onprem exchange online environment.
In that configuration you have to delineate that is uses autodiscover svc.
Storage service had an ews autodiscovery failure microsoft rtc internal storage storeconfigexception.
Storage web service request succeeded.
Storage service had an ews autodiscovery failure.
Update dec 27 2016.
Some of you might already know this but i choose to post this anyway if for some reason someone don t.
If the on premises exchange organization can successfully connect to exchange online you may receive the following error.
When you set up oauth authentication between an exchange server 2013 hybrid on premises installation and office 365 oauth authentication may fail in a proxy scenario.
After spending some time being frustrated over the repeated event id 32054 storage service had an ews autodiscovery failure described in my previous blogpost lync server 2013 event id 32054 ls storage service i finally came accross the solution for this problem.
Storage service had an ews autodiscovery failure microsoft rtc internal storage storeconfigexception.
Event id 32054 ls storage service storage service had an oauth authentication failure.
No issuers are accepted by the target server expected 1 many accepted issuer s storage service had an oauth authentication failure.
The s4b standard server is throwing the following ls storage service 32054 event s and the s4b client is prompting for exchange credentials.
Autodiscover oauth configuration was successfully.
Once this is complete you have configured lync sfb to use the office 365 oauth servers and you will start to see the following errors in the event log.
The event log errors should clear and the following information event will be logged once the sfb front end server is able to reach the exchange autodiscover service via the newly configured autodiscover url.
I agree with the previous poster who hypothesized that it has to do with the autodiscover url that lync is using for oauth.
No issuers are accepted by the target server expected 1 many accepted issuer s storage service had an oauth authentication failure.
