S4B Storage Service Event 32054报错处理

Skype For Business S4B Storage Service had an EWS Autodiscovery failure Event ID 32054

If you get the Error with Event ID:32054 which has details like below

Log Name: Lync Server
Source: LS Storage Service
Date: 10/6/2016 8:37:34 AM
Event ID: 32054
Task Category: (4006)
Level: Error
Keywords: Classic
User: N/A
Computer: ISTTURSFB-P01.infralib.com
Description:
Storage Service had an EWS Autodiscovery failure.

ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings failed, [email protected], Autodiscover Uri=https://autodiscover.infralib.com/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> —> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The request was aborted: The request was canceled. —> System.Net.WebException: The request was aborted: The request was canceled. —> Microsoft.Rtc.Internal.Storage.StoreConfigException: No issuers are accepted by the target server, expected 1-many accepted Issuer(s)
at Microsoft.Rtc.Internal.Storage.Security.OAuthTokenProcessor.GetIssuer(StoreContext ctx, OAuthIssuerMetadata[] acceptedIssuers, Guid srcTenant, String& issuerMetadata, Uri& issuerEndpointUri, String& issuerAudience)
at Microsoft.Rtc.Internal.Storage.Security.OAuthTokenProcessor.CreateAppActAsToken(StoreContext ctx, Guid tenantId, String smtpAddress, String userSid, String userUpn, String destinationAppId, String realmFromChallenge, String destinationHost, OAuthIssuerMetadata[] trustedIssuersFromChallenge)
at Microsoft.Rtc.Internal.Storage.Security.OAuthCredential.Authenticate(HttpAuthenticationChallenge challenge, WebRequest webRequest)
at Microsoft.Rtc.Internal.Storage.Security.OAuthAuthenticationModule.Authenticate(String challengeStr, WebRequest request, ICredentials credentials)
at System.Net.AuthenticationManagerDefault.Authenticate(String challenge, WebRequest request, ICredentials credentials)
at System.Net.AuthenticationState.AttemptAuthenticate(HttpWebRequest httpWebRequest, ICredentials authInfo)
at System.Net.HttpWebRequest.CheckResubmitForAuth()
at System.Net.HttpWebRequest.CheckResubmit(Exception& e, Boolean& disableUpload)
at System.Net.HttpWebRequest.DoSubmitRequestProcessing(Exception& exception)
at System.Net.HttpWebRequest.ProcessResponse()
at System.Net.HttpWebRequest.SetResponse(CoreResponseData coreResponseData)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
— End of inner exception stack trace —
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
at Microsoft.Exchange.WebServices.Autodiscover.GetUserSettingsRequest.Execute()
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(L ist 1 smtpAddresses,List 1 settings, Nullable 1 requestedVersion, Uri& autodiscoverUrl)
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](L ist 1 identities,List 1 settings, Nullable 1 requestedVersion, GetSettingsMethod 2 getSettingsMethod, Func 1 getDomainMethod)
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(L ist 1 smtpAddresses,List 1 settings)
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress,List 1 requestedSettings)
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
at Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
— End of inner exception stack trace —
at Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
at Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)

Cause: Autodiscovery Uri was not correctly configured or unreachable, that there is a problem with the Proxy, or other errors.
Resolution:
Check event details. Check autodiscovery Uri is properly configured and reachable. Check that proxy setting is properly configured and reachable. Validate Skype for Business to Exchange Autodiscovery configuration by following the trouble shooting guide. If problem persists, notify your organization’s support team with the event details.

解决方法:
This is caused by missing AutoDiscovery Uri information, you can check and define them by using the cmdlet called Get-CsOAuthConfiguration and Set-CsOAuthConfiguration

Example:

Getting the current configuration

This is caused by missing AutoDiscovery Uri information, you can check and define them by using the cmdlet called Get-CsOAuthConfiguration and Set-CsOAuthConfiguration

Example:

Getting the current configuration

PS C:\> Get-CsOAuthConfiguration

Identity : Global
PartnerApplications : {}
OAuthServers : {}
Realm :
ServiceName : 00000004-0000-0ff1-ce00-000000000000
ClientAuthorizationOAuthServerIdentity :
ExchangeAutodiscoverUrl :
ExchangeAutodiscoverAllowedDomains :


Adding values

Set-CsOAuthConfiguration -ExchangeAutodiscoverUrl "https://autodiscover.infralib.com/autodiscover/autodiscover.svc" -Realm "infralib.com" -ExchangeAutodiscoverAllowedDomains
"*.infralib.com"


Checking again

PS C:\> Get-CsOAuthConfiguration

Identity : Global
PartnerApplications : {}
OAuthServers : {}
Realm : infralib.com
ServiceName : 00000004-0000-0ff1-ce00-000000000000
ClientAuthorizationOAuthServerIdentity :
ExchangeAutodiscoverUrl :
ExchangeAutodiscoverAllowedDomains : *.infralib.com



To get more detail about Set-CSOAuthConfiguration cmdlet please visit https://technet.microsoft.com/en-us/library/jj204841.aspx , for Get-CSOAuthConfiguration : https://technet.microsoft.com/en-us/library/jj205155.aspx

原文地址:http://blog.51cto.com/3032439/2103835

时间: 2024-10-09 16:43:38

S4B Storage Service Event 32054报错处理的相关文章

service docker start 报错 :Failed to start docker.se

service docker start 报错 :Failed to start docker.service: Unit not found. 解决办法: vi /usr/lib/systemd/system/docker.socket 添加内容如下: [Unit] Description=Docker Socket for the API PartOf=docker.service [Socket] ListenStream=/var/run/docker.sock SocketMode=0

service network restart报错,出现FAILED

在运行service network restart命令时候,显示如下错误 hutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] fgrep: ifcfg-ifcfg-eth0: No such file or directory fgrep: ifcfg-ifcfg-eth0: No such file or directory fgrep: ifcfg-ifcfg-eth0: No suc

fastdfs一个tracker两个storage,上传报错

发起请求的页面地址 POST http://192.168.1.17/fast/file/upload HTTP/1.1 log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.

service cloudera-scm-server restart报错 Unable to retrieve remote parcel repository manifest

Unable to retrieve remote parcel repository manifest 1 详细错误 ERROR ParcelUpdateService:com.cloudera.parcel.components.ParcelDownloaderImpl: Unable to retrieve remote parcel repository manifest java.util.concurrent.ExecutionException: java.util.concurr

重启网卡报错 “Device not managed by NetworkManager or unavailable”

service network restart报错 获取不到ip地址 解决方法: chkconfig network off chkconfig network on service NetworkManager stop service NetworkManager start 卸载网卡/加载网卡ifconfig eth0 down / ifconfig eth0 up

Mysql启动报错解决方案:Failed to open log (file &#39;./mysql-bin.000901&#39;, errno 2)

ps -ef|grep mysql 发现里边没有mysql进程,于是进行重启. service mysqld start报错 查看错误日志 tail -100 /usr/local/mysql/var/iZ11yohng9aZ.err(主机名.err) 180223 15:31:51 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var 180223 15:31:51 InnoDB: The Inn

npm run dev报错,events.js:160 throw er; // Unhandled &#39;error&#39; event

错误代码如下: [email protected] dev E:MySoftwaretestGitwebpackvue-projectnode build/dev-server.js "8088" events.js:160 throw er; // Unhandled 'error' event ^ Error: listen EACCES 0.0.0.0:8080 at Object.exports._errnoException (util.js:1026:11) at expo

安装zookeeper时候,可以查看进程启动,但是状态显示报错:Error contacting service. It is probably not running

安装zookeeper-3.3.2的时候,启动正常没报错,但zkServer.sh status查看状态的时候却出现错误,如下: JMX enabled by defaultUsing config: /hadoop/zookeeper/bin/../conf/zoo.cfgError contacting service. It is probably not running. jps查看进程,却发现进程已启动 7313  QuorumPeerMain 在网上查阅资料一共有三种解决方法: 1,

VMware启动报错:The VMware Authorization Service is not running

The VMware Authorization Service is not running 今天在使用虚拟机的时候,竟然发现不能启动,而且伴有启动虚拟系统报错: The VMware Authorization Service is not running. 截图如下: 故障排除思路: 之前为系统做最大优化时将相关无用启动项及相关服务启动方式做了相应修改: 导致VMware Authorization Service 未启动 系统本地VMware相关服务截图: 解决故障步骤: 1:打开CMD