Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

Test-OutlookWebServices returns (413) Request Entity Too Large for EWS

$
0
0

Completed Exchange 2013 deployment upgrade from Exchange 2010

Troubleshooting why Outlook 2011 doesn't work, nor does calendaring or other EWS functions. I ran Test-OutlookWebServices -Identity user@company.com -MailboxCredential (Get-Credential $prompt) | FL and came back with the following:

RunspaceId          : 6084ee5a-8af1-4607-a6ff-ff8f81df4ada
Source              : server.company.com
ServiceEndpoint     : mail.company.com
Scenario            : ExchangeWebServices
ScenarioDescription : Exchange Web Services
Result              : Failure
Latency             : 2
Error               : System.Net.WebException: The remote server returned an error: (413) Request Entity Too Large.
                         at System.Net.HttpWebRequest.GetResponse()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
Verbose             : [2013-06-15 01:25:02Z] Exchange Web Services connecting to
                      'https://mail.company.com/EWS/Exchange.asmx'.
                      [2013-06-15 01:25:02Z] Test account: user Password: ******
                      [2013-06-15 01:25:02Z] Exchange Web Services request:
                      Content-Type: text/xml;charset=utf-8
                      User-Agent: mbxserver/Test-OutlookWebServices/user@company.com
                      Accept: text/xml
                      Host: mail.company.com
                      Content-Length: 746
                      Expect: 100-continue
                      [2013-06-15 01:25:02Z] Exchange Web Services request:
                      <?xml version="1.0" encoding="utf-8" standalone="yes"?>
                      <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                      xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages"
                      xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"
                      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
                        <soap:Header>
                          <t:RequestServerVersion Version="Exchange2007_SP1" />
                        </soap:Header>
                        <soap:Body>
                          <m:ConvertId DestinationFormat="OwaId">
                            <m:SourceIds>
                              <t:AlternateId Format="EntryId" Id="AAAAAJrt68tcvoJHj4EZX4tVxJkHAJkQvNaLMepFoct50Pnbm4gAA
                      AHZbQQAAF1I2v4S5IFMi6vJDIXLpOEAAAAI6ocAAA==" Mailbox="nobody@contoso.com" />
                            </m:SourceIds>
                          </m:ConvertId>
                        </soap:Body>
                      </soap:Envelope>
                      [2013-06-15 01:25:02Z] Exchange Web Services response:
                      X-FEServer: casserver
                      Connection: close
                      Content-Length: 0
                      Date: Sat, 15 Jun 2013 01:25:03 GMT
                      Server: Microsoft-IIS/8.0
                      X-Powered-By: ASP.NET
                      [2013-06-15 01:25:02Z] Exchange Web Services response:
                      System.Net.WebException: The remote server returned an error: (413) Request Entity Too Large.
                         at System.Net.HttpWebRequest.GetResponse()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
MonitoringEventId   : 6002

Thanks in advance for any guidance!



Viewing all articles
Browse latest Browse all 10580

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>