Jason Slater Weblog

In order to use Virtual Server more effectively on my Exchange 2007 Server I upgraded the memory from 4GB to 12GB and upon rebooting this is where the unusual behaviour started. Firstly, Virtual Server would hang upon bringing up the administrative console. The Event log was reporting:

Event 2216 W3SVC-WP
The script started from the URL ‘/VirtualServer/VSWebApp.exe’ with parameters ‘view=1′ has not responded within the configured timeout period. The HTTP server is terminating the script.

Stopping the Virtual Server Service refused to obey and the only way to fix the problem was to manually terminate the process and restart it. Since then VS has worked well.

However, this morning mail was not flowing internally or externally and was reporting Event 1009.

Event 1009 MSExchangeMailSubmiss

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.

The following error was also being reported:

Event 15002 MSExchangeTransport

The resource pressure is constant at High. Statistics:
Queue database and disk space (”C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue\mail.que”) = 82% [High] [Normal=75% MediumHigh=77% High=79%]
Queue database logging disk space (”C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue\”) = 82% [Normal] [Normal=93% MediumHigh=95% High=97%]
Version buckets = 1 [Normal] [Normal=40 MediumHigh=60 High=100]
Private bytes = 2% [Normal] [Normal=71% MediumHigh=73% High=75%]
Physical memory load = 21% [limit is 94% to start dehydrating messages.]

Inbound mail submission from other Hub Transport servers, the Internet, the Pickup directory, the Replay directory, and the Mailbox server, if it is on a Hub Transport server, has stopped.
Loading of e-mail from the queuing database, if available, continues.

Running the Exchange Mail Flow Troubleshooter seemed to fix the problem temporarily but an hour later the problem has returned. Email just sits in users Outboxes and Exchange refuses to play ball.

After some searching I found this Blog post by Mark Arnold that talked about being short of disk space and moving the Transport Queue Files, even though I had 3.5GB free on drive ‘C’ I edited the EdgeTransport.exe.config file as directed and repointed the two lines

add key=”QueueDatabasePath” value = “G:\Exchange\NewFolder”
add key=”QueueDatabaseLoggingPath” value = “G:\Exchange\NewFolder”

I restarted the Exchange Server Transport Service and the server bounced back into life. Stange? You Betcha. Related to the Memory Upgrade? Strangely Co-incidental is my best guess.