Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I shutdown all Exchange services on the physical box and did a convert. Everything converted fine. Server booted up no issues and I could receive email from the outside world with no issues. But I am unable to send emails internally or externally. They just sit in the Outbox.

I also disabled the DHCPClient service as I didn't want the server to get an IP address from DHCP when it first came online. It came online with no IP, then I used console to assign the correct static IP address (same one on the physical server) and rebooted.

I ran the Exchange Troubleshooting Agent and it gave me the following errors:

The value for the '\MSExchangeIS Mailbox\Messages Queued For Submission' counter on server exchange is greater than zero (average value is 8.8) and it appears that 'MSExchangeMailSubmission' is failing to submit messages to at least one computer with the Hub Transport server role installed over the last minute.

Found 1 computers with the Hub Transport server role installed in the same Active Directory site as server exchange using local Active Directory site GUID 'ce8a4367-1bf6-4825-9cac-c4e2b115c450'.

Check Local Active Directory Site Hub Transport Server Role Health (Mailflow_CheckLocalBhHealth1.

I have one Exchange server with all the roles on it.

Has anyone see this before when doing a convert? Please help :(

share|improve this question
Have you checked the IP addresses that your send and receive connectors are listening on? – Sam Mar 2 '10 at 13:28
Did you remove the original NICs from the system? Directions:… – Chris S Jul 2 '10 at 1:32

Turn the DHCP Client service back on. It is used to register DNS records as well as DNS lookups.

With that service off, you shouldn't be able to resolve any DNS names from that server, which would explain why no mail could be sent from it.

share|improve this answer
Can I +5 this? :-) – Jason Berg Jul 2 '10 at 3:54

After hours of trying tons of difference fixes online I was finally able to resolve my exchange 2010 issue after migrating to vmware esxi 5. E-mails would go to drafts and I could also not delete them. E-mails were coming in fine but could not send. After several reboots and "fixes" I finally restarted the service "Microsoft Exchange Mail Submission" and all e-mail in queue started sending. Everything is working ok now and didn't even have to reboot.

share|improve this answer

Stop all exchange services on the vm. Rename your log directories, ex mine were first and second storage group, i renamed them to ORIGFirst Storage group and ORIGSecond storage group. I then re-created the Folders First and Second Storage group with nothing in them. Restarted all exchange services and mail started flowing.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.