ClearBlueTechnologies
asked on
Exchange 2013 Autodiscover issue with all versions of Outlook. Request Entity Too Large.
Having an issue with Exchange 2013 and Autodiscover. Have a GoDaddy cert with mail.domain.org and autodiscover.domain.org. Have all the URLs pointing to those. Have Outlook Anywhere setup correctly. OWA and ECP work fine with no cert warnings. Have split DNS internally for the domain.local and domain.org. Everything resolves correctly. Getting a weird error with Outlook when setting up a profile. It uses autodiscover and throws a cert redirect warning then throws a error " The connection to Exchange is unavailable. Outlook must be online or connected to complete this action". Everything is online.
On the server I run:
Test-OutlookWebServices -Identity:username@domain. org -MailboxCredential:(Get-Cr edential domain\username) | fl >> C:\TestResult.txt
Results:
[2015-11-05 15:54:31Z] Autodiscover response:
System.Net.WebException: The remote server returned an error: (413) Request Entity Too Large.
at System.Net.HttpWebRequest. GetRespons e()
Also get something similar running the Outlook - Test connection .
Any thoughts?
On the server I run:
Test-OutlookWebServices -Identity:username@domain.
Results:
[2015-11-05 15:54:31Z] Autodiscover response:
System.Net.WebException: The remote server returned an error: (413) Request Entity Too Large.
at System.Net.HttpWebRequest.
Also get something similar running the Outlook - Test connection .
Any thoughts?
ASKER
I think it is a web issue too. How do I rebuild the virtual directories?
ASKER
I ran the test-OutlookWebServices cmdlet from the Powershell and am getting these results.
Source - ServiceEndPoint - Scenario - Result
server.domain.local - server.domain.local - Autodiscover: Outlook Provider - Failed
server.domain.local - server.domain.local - Exchange Web Services - Failed
server.domain.local - - Availability Service - Skipped
server.domain.local - server.domain.local - Offline Address Book - Failed
The odd thing is I have all the virtual directories, DNS, SCPs, etc...pointing to the mail.domain.org address. Not sure why these are still displaying the old address. Not a 100% sure which is correct at this point either.
Source - ServiceEndPoint - Scenario - Result
server.domain.local - server.domain.local - Autodiscover: Outlook Provider - Failed
server.domain.local - server.domain.local - Exchange Web Services - Failed
server.domain.local - - Availability Service - Skipped
server.domain.local - server.domain.local - Offline Address Book - Failed
The odd thing is I have all the virtual directories, DNS, SCPs, etc...pointing to the mail.domain.org address. Not sure why these are still displaying the old address. Not a 100% sure which is correct at this point either.
Here's a fw good resources on recreating the virtual directories, but it does look like your urls may be wrong.
http://blogs.technet.com/b/get-exchangehelp/archive/2013/02/07/managing-exchange-2013-iis-virtual-directories-amp-web-applications.aspx
https://technet.microsoft.com/en-us/library/ff629372.aspx
try this for info on checking/setting the urls:
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
http://blogs.technet.com/b/get-exchangehelp/archive/2013/02/07/managing-exchange-2013-iis-virtual-directories-amp-web-applications.aspx
https://technet.microsoft.com/en-us/library/ff629372.aspx
try this for info on checking/setting the urls:
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
ASKER
The URLs seem to be fine.
your test of the webservices suggested otherwise though.
Could you post the results of the 'get' commands from the links I provided so we can double check them please?
Could you post the results of the 'get' commands from the links I provided so we can double check them please?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
None of the others fixed the issue
try rebuilding the virtual diretcories.
otherwise check the urls you have set for the autodiscover & ews folders to check you are pointing internal clients to the correct IPs for autodiscover.domain.org & mail.domain.org (not domain.local as you cant get SSLs for that these days.)