• Call Toll Free: 1-855-909-3300

How To Resolve Mac’s Exchange 2010 Error 18500?

Exchange Server 2010 by Microsoft has been a booster for the internet users as well as businesses being operated on the web. It is a calendaring as well as a mailing server that works efficiently on all kinds of electronic devices. Highly reliable as well as flexible cloud environment has improved the level of online business standards. Around-the-clock data access improved security and enormous storage volume has made it a successful cloud server.

SQL Server 2010

Host your Accounting Software in secured Cloud

While it runs well on Android, Windows and on Apple devices also, there are certain issues that may pop up while using it, especially, when there is some upgrade or renewal set about.  Some of the issues are quite common. Users can fix those following simple steps.

Users of MAC often experience the prominent MAC Exchange error 18500 while using Exchange 2010. It is the error that occurs because of an issue of a large file. Here we have discussed on how to fix mac exchange 2010 error 18500.

The MAC exchange error 18500 stating “Large file type” may have cropped up because of either of the two issues mentioned below:

Unable to send above 1Meg

Step1:        In this case, the failure to send a file above 1 Meg may be due to an issue in the EWS folder. This error may also arise because of authentication issues. This issue can be resolved by adding Basic authentication to the EWS folder in IIS.

Step 2:          Open IIS under the default web site and then click on the EWS folder:

Step 3:              Click on Authentication and enable the Basic Authentication

Attractive Plans Available for Application Hosting

Unable to send anything above 13Meg

If the user encounters a problem related to above 13 Meg file size, then comes a need to raise file size allowed in the web.config file. The upper level of the file size is required to be increased. To change the maximum limit, follow the given steps:

    Step1:

Option 1

   In “web.config” file, change “maxAllowedContentLength” parameter.

         From CMD change folder to “%windir%\system32\inetsrv\”.

   Run below command: appcmd set config

 “Default Web Site/ews” -section:requestFiltering         requestLimits.maxAllowedContentLength:<ZZ>Note.

                                    OR

Option 2

In “web.config” file, change “maxRequestLength” parameter.

Open “web.config” file located in the EWS Virtual directory

Microsoft\Exchange Server\ClientAccess\exchweb\EWS“will have the       following entry<httpRuntime maxRequestLength=”13280″ />Note

Change the item <httpRuntime maxRequestLength=”13280″ /> to <httpRuntime maxRequestLength=”KK” />Note.

   OR

Option 3

In “web.config” file, change “executionTimeout” parameter.

Open web.config file located in the EWS Virtual directory

Microsoft\Exchange Server\ClientAccess\exchweb\EWS“Change the item <httpRuntime maxRequestLength=”13280″ /> to <httpRuntime executionTimeout=”X” maxRequestLength=”13280″ />Note.

      Step 2:

Further, go to “IIS Manager”. Select “Default Web Site”.

      Step 3:  

Click “Advanced Settings”. Select “Connection Timeout”. Change the value in Seconds.

It is suggested not to make any change in the web.config file. Also, only OWA by Microsoft must be used for transferring files to another location.

Leave a Reply

Techarex NetWorks Products