Note that a standard configuration should provide output similar to the above. One of the workarounds for this issue is to manually configure Skype for Business to use a different autodiscover URL but before doing so, confirm that there isn’t already an existing manually created configuration by executing the cmdlet: The environment where I encountered this issue did not use the standard Exchange autodiscover URL and therefore caused this issue for their SfB users.
One of the reasons why this event error would be logged causing the out of sync messages is if the Exchange autodiscover URL is unreachable as indicated in the event ID details: If problem persists, notify your organization's support team with the event details. Validate Skype for Business to Exchange Autodiscovery configuration by following the trouble shooting guide. Check that proxy setting is properly configured and reachable. Check autodiscovery Uri is properly configured and reachable. End of inner exception stack trace -Īt .(StoreContext ctx, String smtpAddress)Īt .(StoreContext ctx, String smtpAddress, CacheMode cacheMode)Ĭause: Autodiscovery Uri was not correctly configured or unreachable, that there is a problem with the Proxy, or other errors.Ĭheck event details.
StoreWebException: code=ErrorEwsAutodiscover, reason=GetUserSettings failed,, Autodiscover Uri=, Autodiscover WebProxy=, WebExceptionStatus=NameResolutionFailure -> : The remote name could not be resolved: ''Īt (TransportContext& context)Īt ()Īt .AutodiscoverRequest.InternalExecute() Storage Service had an EWS Autodiscovery failure. Logging onto the Skype for Business front-end server and reviewing the Lync Server logs show that event ID 32054 errors are logged and refer to the users who have complained about the issue: You’ve received complaints from users that they are experiencing out of sync messages between devices such as their mobile phones compared to the Skype for Business clients.
0 kommentar(er)
