SharePoint SiteMialbox failed with 503 error (AutoDiscover.svc web service call failed)
I followed Technet articles to configure SiteMailBoxes in our environment & exchange sever.
When we created Sitemailbox in a SiteCollection &when we try to open it, it failed with below error.
Site Mailbox
We are having trouble connecting to Exchange Server
The server might be temporarily unavailable. Please check back on this page in a few minutes. If this problem persists, please contact your system administrator.
Correlation ID: bb0fe99c-6f4e-e084-b191-881fbf0fa977, Error Code 10
ULS Log (503 error)
Autodiscover Diagnostics Response Headers: request-id: 95d12ceb-283e-4495-b28b-256503fd097c client-request-id: 742fe69c-ef5a-e084-ca05-6098c759c584 X-CalculatedBETarget: devapwxyz01a.devap.mydomain.com X-FEServer: DEVNAABCD01B Content-Length: 0 Cache-Control: private Date: Tue, 03 Feb 2015 18:53:40 GMT Set-Cookie: X-BackEndCookie=; expires=Sun, 03-Feb-1985 18:53:40 GMT; path=/autodiscover; secure; HttpOnly Server: Microsoft-IIS/8.5 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET 742fe69c-ef5a-e084-ca05-6098c759c584
if I am correct, X-CalculatedBETarget supposed to be DEVNAABCD01B.devna.mydomain.com but it connected to different domain devapwxyz01a.devap.mydomain.com. Do you guys have any idea on this? (I verified the same using fiddler, it is failing right at autodiscover.svc call.)
I wrote a powershell script to connect autodiscover service in sharepoint server & this web service call able connect right server X-CalculatedBETarget. It gave the expected response.
I am not sure why SharePoint webservice call (X-CalculatedBETarget) is going to different server?
let me know if you guys have any ideas.
Thanks.
- Edited by PPReddy19 7 hours 6 minutes ago
Other recent topics
