Lync Server 2013: Event ID 32054, LS Storage Service

Problem With event ID 32054 appearing in event log on Lync 2013 server.

The scenario is as follows:
Lync 2010 upgraded to Lync 2013 CU3 in co-excistence with Exchange 2010 SP2 running on Windows Server 2008 R2.

The event log on the Lync 2013 server is showing repeated event ID 32054. “Sorage Service had an EWS Autodiscovery failure.”
Event ID 32054

The error message pointing in direction of missconfigured autodiscovery or reverse proxy configuration. Since I’m not a big fan of red messages in the event log, I proceeded to check out the possible causes to this error.

Ran a check of the Exchange web services configuration:


Everything seems OK here.
Also checked for in internal and external DNS. All good there as well. Even had the SRV records for autodiscovery in place both internally and externally.
Next step was to check all the Lync features to see if anything was not working as it should. Did a complete check of all features both on my internal Lync PC client and from my mobile iOS client. Everything worked like a charm, while at the same time the events kept popping up in the event log saying “this is not right”.

My conclusion:
The event ID 32054 can safely be discarded as rubbish as long as everything is working fine. I’ve seen multiple posts regarding the same problem all over, and currently there has been no cure.

If anyone by any chance has a working, documented solution to this “problem”(Microsoft???), please feel free to post a comment with links in this post.

16 thoughts on “Lync Server 2013: Event ID 32054, LS Storage Service

  1. This error is all over… And for no reason. I think it should be classified as a warning since it really doesn’t affect anything.

      1. I know. I’ve also seen a couple of servers lately with CU4 installed and the EWS error messages still appear in the log.
        Don’t know if anyone else for a fact has experienced differently?

  2. Dang. I hate this error message. I hate errors in general. But, this one particularly. It reminds me of something … I just can’t put my finger on it. Maybe one day it’ll get fixed.

    1. Hi Truong.
      It could very likely be as a result of mobile client login, but still it’s rubish. There is no problems whatsoever in signing in with mobile devices. Maybe the event occurs every time someone tries to log in with a mobile device? I haven’t been able to look into this possible reason.

  3. In a few occasions I managed to fix this issue by altering the exchangeautodiscoverurl with the set-csoauthconfiguration cmdlet. If the url points to a xml file, you should change it to .svc.


        After the autodiscover service has been configured you must then modify the Lync Server OAuth configuration settings; this ensures that that Lync Server knows where to find the autodiscover service. To modify the OAuth configuration settings in Lync Server 2013, run the following command from within the Lync Server Management Shell. When running this command, be sure that you specify the URI to the autodiscover service running on your Exchange server, and that you use autodiscover.svc to point to the service location instead of autodiscover.xml (which points to the XML file used by the service):

        Set-CsOAuthConfiguration -Identity global -ExchangeAutodiscoverUrl “”

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s