Link to home
Start Free TrialLog in
Avatar of sgarces
sgarces

asked on

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]

We have come across a rather strange problem with one of our sites. Our staff are receiving an email back from our exchange server (System Administrator) saying:


Your message did not reach some or all of the intended recipients.

      Subject:      
      Sent:      09/07/2012 20:18

The following recipient(s) cannot be reached:

                        on 09/07/2012 20:33
            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].

                       on 09/07/2012 20:33
            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].


But looking on the Exchange server I am not able to see it hitting our server at all. Also the user will have emails arrive days after they have been sent, Which has happened to our other 2 users on site also. I have Checked with our ISP to see whether there has been drops on our WAN link but the drops have been minimal (a matter of minutes at the maximum), which would not justify such a lag between the sent and received

I have checked the web and seen that for the above error it could generally be cause by 1 connectivity issues or the offline address book has not been updated recently. I have checked both of these options.

They are connected to our head office through an MPLS (WAN) and although they do not have the best/most stable connection they have not suffered from this issue in the past.  

The way that our emails work is that anything not local to our domain gets routed through Germany mail servers and anything external to us goes through them to get to us in the UK. The above error message was received from an email that was sent to an external address with a local user CC'd on it. It also appears to be local mail that is getting halted. One example is that our user sent an email on the Friday at 4:50pm and the user who it was intended for (on the same site/LAN) did not receive it until 1:30pm on the Monday (When I happened to be at site to see it first hand). This problem does seem limited to this site for the time being and the repercussions of the delayed mail has been minimal so far but if the issue spreads to the larger sites it could become a big problem very quickly.

In Terms of testing:

Checked there local LAN connections between eachother which all appear to be fine.
Checked there WAN Connection by ping/tracert to head office, all of which seems to be relatively stable.
Sent emails back and forth between them and other users without being able to replicate the problem so that I can see it happen first had and see where the bottle neck is.

Any Help on this will be appreciated.

Regards

Sean
SOLUTION
Avatar of Rajkumar Duraisamy
Rajkumar Duraisamy
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sgarces
sgarces

ASKER

Hi Rajkumar,

Thanks for the response.

That was my initial thought with this and could explain the NDR received but does not explain such a delay in the send/receive of the emails.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sgarces

ASKER

This issue has sorted itself out. I am not to sure as to what it was that stopped the problems. I did do a couple of things however.

updated the offline address book on the users pc
amended the send/receive settings in outlook so that it checks for updates more frequently.
raised a call with our ISP who have been looking into possible connectivity issues. As suggested by Rajkumar