Urgent Feedback needed - Attachment size exceeds allowable limit

Status
Not open for further replies.
P

PiMPstAR

Hi,

We have recent migrated from a exchange 2003 server to a exchange 2007 server. We have users receieving email and when attempting to opeb the email, they recieving a window pops up: "Attachment size exceeds allowable limit" in the email there are no attachments in the email. When the users attempt to close the email they basically have to end task and kill outlook. Is anybody aware of a fix available for this?

Regards
KevinKind Regards PiMpSTAR msn chat : veno_32@hotmail.com
 
D

DeVa

* What's the Outlook version and service pack?

* Have tried opening via MFC MAPI? What's the result that you see?DeVa, M.S., {MSFT}
 
O

Office2Mobile

PiMPstAR,

You may want to look at the attachment filters you have set within Exchange 2007, though it might be set to strip the email attachments if it has exceeded a specified size, i cant see how its causing Outlook to hard lockup. Are all PC able to replicate the hard lockup, and are they at least able to receive any attachments, like a simple test.txt file?Office2Mobile, On the move with enterprise-class tools hosted by http://themessagecenter.com/
 
A

Allen Song

Hi,

Did you test this issue in OWA? Whether all users had this issue?

Thanks

Allen
 
J

Joe Rainero

We have been seeing similar issues. Our users use Terminal Services to run Outlook 2007 and the message is usually happening when they click to set the category for a message. The issue does not happen all of the time and it never has happened when running Outlook 2007 from a local computer via Outlook Anywhere. Are there any updates to this thread?

Also, since it doesn't happen all of the time, we're having trouble tracking down where it is happening. Is there a log of these errors somewhere?

Thanks,
Joe
 
E

Ed Crowley [MVP]



You might want to ask in an Outlook newsgroup.
--

Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.



"Joe Rainero" wrote in message news:00eb4f59-2c65-4d36-a339-8348fea3fef0...

We have been seeing similar issues. Our users use Terminal Services to run Outlook 2007 and the message is usually happening when they click to set the category for a message. The issue does not happen all of the time and it never has happened when running Outlook 2007 from a local computer via Outlook Anywhere. Are there any updates to this thread?

Also, since it doesn't happen all of the time, we're having trouble tracking down where it is happening. Is there a log of these errors somewhere?

Thanks,
Joe Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
 
Status
Not open for further replies.
Top