The client operation failed. Error is [0x80004005-0x0004b9-0x000501].

[DJCopa]

Hello.

We get (intermittantly) the following errors from homeworkers ,connecting via VPN (SonicWall), when sending email (Outlook 2003 SP2) through our Exchange 2003 SP2 Server:

The client operation failed. Error is [0x80004005-0x0004b9-0x000501].

It looks as if the email From field has been stripped off. Sending again will work, but it is an annoying problem that is becoming more and more common.

Had a look on the internet, and found one Microsoft Tech say That the error cannot be shared externally - Only for internal use, which is Bonkers!!!

If anyone can shed any light in this issue, it would be great.

Thanks.

 

[sgladman]

Hey there --

Did you have any luck with this issue? I'm starting to run into it here...same situation: SonicWall VPN, 'From' field empty when user replies, NDR comes back with "This message could not be sent. Try sending the message again later, or contact your network administrator. The client operation failed. Error is [0x80004005-0x0004b9-0x000501].", and a resend usually works.

Hoping someone has the magic answer...thanks!

 

[DJCopa]

Hello!

We still get the problem - Think alot of our users are now living with it, which isn't the solution I was after. Articles I've read all point to Outlook 2003's flakey nature over a VPN (with no fix!). It's got to the point where we were spending all our time trying to resolve an issue which may not have an answer (which is pants!).

Still hoping someone may have an idea........

 

[sgladman]

Thanks for the reply!

Bummer that there is no answer yet. Digging through the 'net shows that others have this trouble, and different things fixed it for different people: deleting the Outlook profile and recreating, rebuilding the offline address book and having the user redownload it, moving from cached exchange mode to "old school" OST and synching, turning thrice widdershins under a full moon while clutching an O'Reilly book, and so on.

In other words, it's a problem that is intermittent, hard to reproduce on demand, and which "fixes" itself on a resend, with a too-generic error message. Joy. :^P

Keeping my fingers crossed...I still have faith in the power of teh intrawebs.

 

[DJCopa]

Thought it was only me doing a jig at midnight, whilst sipping moonshine, to fix the problem - Glad to hear (in a non-sadistic way) that others are finding it a nightmare.
I will keep looking as well, and hope that the issue cannot be ignored for too much longer.

I have tried all the things you have suggested also - Looks like it's solved, and then it creeps back. MTU Stacks value in the registry, was another fix - Tried this on a few, but seemed to muck up some of the VPN connections.

Anything else I find, I shall post.

Good Luck!

 

[1LUV1T]

Any luck? Someone just reported this problem to me and Googling didn't help much. Some people said the mailbox was over 2 gigs and after archiving it helped but this user is well below 2 gigs. What is the MTU stacks registry fix? Did it help?

 

[DJCopa]

MTU registry fix, ups the limit on packet size that can be sent. This was thought to be one of the causes, and may well be, but didn't really do an awful lot for us (apart from cause more work). Link attached below, but best to do some tests first

http://support.microsoft.com/default.aspx?scid=kb;en-us;283165

http://www.internetweekly.org/llarrow/mtumss.html

If you get any joy, please let us know.

Thanks.