jerkady
asked on
Periodic Transport Crash (possible BackPressure?)
Gday Everyone
I am running an Exchange 2007 SP1 (rollup 2) server, on Windows Server 2008 with all the latest updates, running on the latest version of VMWare Server 2.0 beta. I will start by saying that i'm aware that this is an unsupported configuration (any VM) but I'm sure that there are people out there who have this configuration working.
What is happening, is that at a seemingly random interval (sometimes a few hours, at other times several days) I will get event ID 1009 The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
Obviously at this point on, the users experience mail not leaving their outbox/drafts, and mail is not submitted to clients.
Typically what i've found is that most of the time answers relating to this event ID are relating to either a network connectivity issue between hub and edge server [Note that i'm using a single exchange server deployment so this is not relevant] or a BackPressure issue. However my impression is that if this were a back pressure issue, it would log a warning regarding resource levels - which is not the case. This is the only error and or warning that the server logs at or near the time of transport failure. In fact it's basically the only error/warning that is logged on the server at all!
FYI the server is fairly well stocked, having been allocated 5GB of RAM, storage is on a FC SAN (dedicated LUN) and i've allocated 2 processor cores for the VM. The host Server is purely acting as a 2008 DC (ie. not file sharing/print serving/anything really).
Can anyone point me in the right direction to resolving this issue, or where I would start looking?
I am running an Exchange 2007 SP1 (rollup 2) server, on Windows Server 2008 with all the latest updates, running on the latest version of VMWare Server 2.0 beta. I will start by saying that i'm aware that this is an unsupported configuration (any VM) but I'm sure that there are people out there who have this configuration working.
What is happening, is that at a seemingly random interval (sometimes a few hours, at other times several days) I will get event ID 1009 The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
Obviously at this point on, the users experience mail not leaving their outbox/drafts, and mail is not submitted to clients.
Typically what i've found is that most of the time answers relating to this event ID are relating to either a network connectivity issue between hub and edge server [Note that i'm using a single exchange server deployment so this is not relevant] or a BackPressure issue. However my impression is that if this were a back pressure issue, it would log a warning regarding resource levels - which is not the case. This is the only error and or warning that the server logs at or near the time of transport failure. In fact it's basically the only error/warning that is logged on the server at all!
FYI the server is fairly well stocked, having been allocated 5GB of RAM, storage is on a FC SAN (dedicated LUN) and i've allocated 2 processor cores for the VM. The host Server is purely acting as a 2008 DC (ie. not file sharing/print serving/anything really).
Can anyone point me in the right direction to resolving this issue, or where I would start looking?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As it currently stands, I did a hardware independent restore to the client's old Small Business Server, and we have experienced no issues since. I will leave this running for 10 days and if the problem has still not reoccurred, will consider this to be a fix for the issue.