I am attempting to send large >30 MB attachments via OWA 2007. I receive an error " The files (file name) were not attached because they exceed the maximum size limit of 5 megabytes (MB) for attachments.".I have referenced the article at http://msexchangeteam.com/archive/2006/11/14/431477.aspx. I have previously changed the transport MaxSendSize using the set-TransportConfig cmdlet to unlimited . This was to allow the sending of large attachments via Outlook 2007. I can send large attachment using Outlook successfully. I have modified the maxRequestLength setting in theASP.NET web.config setting. The default was <httpRuntime maxRequestLength="30000" />. I changed it to <httpRuntime maxRequestLength="50000" /> . This should allow me to send attachments of 50MB if I understand the setting correctly.I still receive the same error message. What else am I missing? Where is OWA picking up the 5MB limit? I have set the to maxRequestLength to 50000, (50 MB), it was set for the default of 30000, (30 MB) Thank you for any assistance.

Try that:for one userget-mailbox -identity "Mailbox name" | set-mailbox -maxsendsize 30MBFor the whole databaseget-mailbox | set-mailbox -maxsendsize 30MB

Hy, Ihave the same problem , I try the same but the problem persists, what more can I do?

Make sure after you have changed your limits that you restart Exchange.

Bilm, I'm having the same issue. Whats funny is the server i'm working on has a 5MB OWA limit as well. This doesn't seem to affect Outlook users - just OWA. I've checked: user mailbox setting send connector setting & global transport config all set to 50MB I've also verified web.config is at the default 3000 as stated here. Did you ever resolve your issue? Do you have SP1 installed?

I see that there isa glitch in the way IIS reads max size limits. see here for more detail: http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1302783,00.html The short of it is: OWA cant understand a "transportconfig" of "unlimited". Manually setting it to 50MB worked for me. Open ems Get-TransportConfig verify MaxSendSize is unlimited set-TransportConfig -MaxSendSize 50mb I haven't applied sp1 to this server yet. Has installing sp1 fixed this for anyone?

Mike, I was running SP1 when I had this problem. I found the same fix. I changed transportconfig to 100 MB to resolve it. Yes I know 100 MB is large but the customer insisted. Bil Martin

i'm having this issue and changed the transport config to 100MB also, still same issue. do i need to restart the server for the changes to take effect?

There are two issues here. The OP was related to the IIS upload default, which isn’t really a quota issue. This only needs to be adjusted if you want to allow people to upload >30MB files into OWA. The 2^nd issue is regular transport configurations. There could be transport limits on connectors, mailbox or the global config. please post your exact error message. Mike Crowley Check out My Blog!

I have this exact same problem. I am running Exchange 2010. Outlook clients can send/receive large attachments but OWA gives an error that the attachment limit is 5MB. Everyplace I can find to change the limit is set to 52000KB. I've also adjusted my web.config. Do I need to restart the server after modifying web.config? Thanks

Issue "Get-TransportConfig | fl" and ensure that "maxsendsize" and "maxreceivesize" are set to your preference. If not, you need to increase your send and receive connectors. Please take a look at this white paper: http://technet.microsoft.com/en-us/library/bb124345%28EXCHG.80%29.aspx.

Jose - yes my TransportConfig MaxSendSize and MaxReceiveSize are both set to 50MB. No place can I find anything set to the 5MB limit that OWA is reporting when I attempt to attach in an OWA email...

Attempt to restart all of the Exchange services. If it still does not work, you're missing one of the send or receive connectors; all of them must be set to that size. Keep us posted.

I am having this same issue. It's not an issue with settings in Exchange 2007, as Outlook clients do not have the problem. It's only OWA users that have the problem.

If you really believe you have done everything correctly, and it still doesn't work; restart your computer, or restart all exchange services, or try individual exchange services until it starts working :)