Exchange Web Services 500 Internal Server Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: EWS Problem Exchange Server > Exchange Server 2013 -
Exchange Owa 500 Internal Server Error
Administration, Monitoring, and Performance Question 0 Sign in to vote I http 500 internal server error web service beleive my previous thread may contain a bunch of data that may not be helping as it appears
500 Internal Server Error Web Service Call
to have been caused by my attempts at troubleshoting so I am resetting. Config: Exchange 2013 CU1 on Server 2012 VM. All appeared to be working (although full autodiscover asmx 500 internal server error DNS had not been set up) prior to CU1 upgrade last week. Symptoms: In OWA,Options | Apps generates a response didn't contain valid XML error In Outlook, opening a shared calendar results in No Connection, an attempt to share a calendar results in an "unexpected error", no free busy information is shown. Browsing to /EWS/exchange.asmx from anywhere results in html 500 error code a server error message. Browsing to /EWS/exchange.asmx on the exchange server gives the much more instructive detail page. In indicates 500.19, Absolute physical path "c:\inetpub\custerr" is not allowed in sytem.webServer/httpErrors section in web.config file. Use relative path instead. ExRCA shows autodiscovery tests passing but EWS tests fail with an invalid XML error. Autodiscovery is working as far as I can tell. The instaled cert has autodiscover.domain.com, internal name, and external name in it. I have reset the EWS virtual directory via EAC twice now and restarted IIS. This last time I ensured that all I did after the reset was add the external URL. I retested all of the above and got the same results. Do so from inside or outside gives the same results. I am at a loss as to where to go from here to troubleshoot what to do. I suspect that the key is the absolute path error when browsing to \EWS\exchange.asmx on the exchange box but I have no idea where to look. I would appreciate any suggestions on whatt
All Tests are failing "The remote server returned an error: (500) Internal Server Error." Issue: On one of the Exchange 2013 Server out of 4 Exchange 2013 servers all
Exchange 2013 Ews 500 Internal Server Error
tests were failing. No change after IISreset No change after server restart an http 500 response was returned from iis7 activesync exchange 2013 Here are the test screenshots Test-ActiceSyncConnnectivity failed WinRM with start failing Test-webservicesconnectivity failed In verbose mode I got "The
Test-outlookwebservices Exchange 2013 Failure
remote server returned an error: (500) Internal Server Error" Test-outlookwebservices failed Open IIS à Default web site à Active Sync and browse and I got below message. HTTP Error 500.19 https://social.technet.microsoft.com/Forums/exchange/en-US/15a18a14-1ec0-4179-9e39-c754c16a5360/ews-problem?forum=exchangesvradmin Internal Server Error. Cause: Misconfiguration on c:inetpubwwwrootWeb.config Solution: Fixing the web.config file. We have to remove the below text. --------------------------------------
for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this http://sharepoint.stackexchange.com/questions/175022/web-service-calls-returns-http-500-internal-server-error-on-my-sharepoint-2013-s site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint http://www.msexchange.org/blogs/walther/news/exchange-2010-sp1-experiecing-an-owa-http-500-error-554.html Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can 500 internal answer The best answers are voted up and rise to the top Web service calls returns HTTP 500 Internal Server Error on my SharePoint 2013 site up vote 0 down vote favorite I have a SharePoint site that was running without any problem. Few days ago the search stopped working with a error in the crawl log The crawler could not communicate with 500 internal server the server. Check that the server is available and that the firewall access is configured correctly From the ULS log I was able to see that the crawler is trying to call a web service _vti_bin/sitedata.asmx but it is failing with error HTTP 500 Internal Server Error. I believe because of this failure the crawl is not working in the farm. When i tried to call other built-in webservices in SP2013 (such as lists.asmx?WSDL), I noticed that all the ASMX services have the same problem. Can anybody please help me to figure out what is going wrong in SharePoint? I tried to see the ULS and event viewer nothing logged there. Is there any way I can "reinstall" the ASMX web services in SharePoint? UPDATE: The web services are not working on the site collection root site. For any subsite the web services works properly. I am still confused. Thank you sharepoint-enterprise sharepoint-server share|improve this question edited Mar 30 at 5:02 asked Mar 26 at 11:22 Arun 10919 You probably could get more info from logs: either from the Windows Event Viewer (
seen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my credentials and then boom it throws an “HTTP 500” error instead of opening the mailbox. You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom.So the issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue. Why it sometimes doesn’t start automatically after a reboot of the servers is a very good question. I’ll do some more research in order to find the root cause.Until later,Henrik WaltherTechnology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture I’ve seen this issue a couple of times after applying Exchange 2010 SP1 on Client Access servers. I’m presented with the OWA FBA page and enter my credentials and then boom it throws an “HTTP 500” error instead of opening the mailbox. You tried to issue an “IISReset /NoForce” and even rebooted the server and still see the symptom. So the issues is typically caused by the “Microsoft Exchange Forms-Based Authentication” service being in a stopped state. Starting the service immediately fixes the issue. Why it sometimes doesn’t start automatically after a reboot of the servers is a very good question. I’ll do some more research in order to find the root cause. Until later, Henrik WaltherTechnology Architect/WriterMCM: Exchange 2007 | MVP: Exchange Architecture See Also Review and Comments Name * Email address * URL * Comment * If you enter anything in this field your comment will be treated as spam * * Required field Kenny K Sun, 12 July 2015 00:17 1000 thank you's your suggestion totally worked. How many times we're looking for the issue in the most complicated places only to find a service failed to start. I feel like an intern right about now... -Ken mgaytan Wed, 24 June 2015 22:51 did you find a root cause? yotks! Sat, 28 Feb. 2015 22:15 tks! it worked! Bahloul Wed, 10 Dec. 2014 10:31 thanks Henrik. See Also Simplifying the Outlook Web App 2010 URL 11 Sept. 2009 Henrik Walther Office 365: ADFS - Support for Multiple UPNs 23 April 2013 Henrik Walther Accessing an Office 365 tenant using the new Windows Azure Active Directory Manager (WAADM) 17 Sept. 2012 Henrik Walther EAS issues after moving user mailboxes to Exchange 2010 13 Sept. 2009 Henrik Walther Exchange 2010 RPC Client Access arrays and Outlook 2003 10 Sept. 200