We once had the problem that some emails with a long text in it were taking ages till they were send. We are using the email router to send and receive emails to our support team.
As we moved some months ago from normal exchange to BPOS my first suggestion was that it has to do with the connection between BPOS and the Emailrouter. ( RU 14)
In the event-viewer I recognized the following entry:
#61042 - An error occurred while the outgoing email message with the subject Re: urgent problem with DCP config PTM CRM00114110 CRM: 0000132293' for ExchangeOnline: http://[servername]/PTMEDVSystemeGmbH for delivery through https://autodiscover-red002.mail.emea.microsoftonline.com/ews/Exchange.asmx The request failed with HTTP status 413: request entity too large,
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters) bei Microsoft.Crm.Tools.Email.Providers.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.SendMessage(MessageType mailMessage) bei Microsoft.Crm.Tools.Email.Providers.ExchangeOnlinePollingSendEmailProvider.ProcessMessageInternal(email emailMessage)
So I created a case by Microsoft to let them look through this behavior. In this last month I was forwarded 3 times from the CRM team to the BPOS team and back. Today was the big day and the wonderful guy from the BPOS team was able to give the right hint with the following description in his email to me:
For messages to be sent to Exchange Online through the Email Router for CRM, the Secure Sockets Layer certification must be enabled for Exchange Online and your Email Router to communicate. The default size for the buffer in the SQL Server is 48k and every email with more text results in error HTTP status 413: request entity too large.
The solution to this is to logon to your SQL server and follow these instructions:
Increase the size of the UploadReadAheadSize property on your SQL server:
- Click Start, click Run, type cmd, and then click on the [OK]-button.
- At the command prompt, type the following:
cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 500000
Please note: This command changes the UploadReadAheadSize property to 500 KB (500,000 bytes).
- Press the [ENTER]-button.
- By running this command, you update the Microsoft Internet Information Services (IIS) metabase so that you can upload files that are as large as 500 KB.
Please note: In certain situations, you may have to set the UploadReadAheadSize property to even larger than 500 KB.
In my case I had the SQL Server and the CRM Server on one machine and I executed this script and I was not able to reproduce the error. The conclusion is that this had nothing to do with BPOS and everyone also with a normal Exchange can come into this problems.
The dangerous thing is that you do not realize that behavior easily, because you send your email from the web client and the email closes successfully. If you do not explicitly look for the email, you do not see that it was not send or delayed.
If you have the same problem, I hope this will solve your issue too.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to email@example.com.