Exchange 2003 after a P2V migration is not delivering mail internally
Hello, and thanks for reading! I'm in need of quick assistance as we're having some problems with our Exchange server after a P2V migration. I'm not exactly sure what info you need, but here are the basics:
-Single Exchange 2003 server, running SP2
-Running on Windows 2003 32-bit, with SP2
-Was running on an old physical server
-New system is VMWare ESX 4.1
-Used VMWare Converter, installed directly on the server with almost all the default settings to migrate it to virtual.
-I found out today that the Information Stores were not shut down during the migration, but antivirus was
-Symantec Endpoint Protection 11.0, has been turned off during the troubleshooting.
There are about 150 users in the organization spread out across 4 Storage Groups. 15-20 of the users are not able to receive any emails. They are spread out across the Groups, so it's not a single database causing the problem. They can send email without problems, they just can't receive any internal or external messages. All emails to these users are sitting in the "Local Delivery" queue.
Their Outlook and OWA are showing changes correctly, so it doesn't appear to be a connection problem between Outlook and Exchange.
Here is a sample of the Message Tracking Log for an email stuck in the queue for an impacted user:
5/14/2011 11:43 am SMTP: Message Delivered locally to _______
5/14/2011 11:43 am SMTP: Message scheduled to retry local delivery
over and over again.
Other mail delivery on the server seems slow, occasionally no one receives email for 30 minutes, then it all comes in. I'm not having any problems Telnetting into the server, it looks like everything is just getting stuck in the queues.
I also don't see any relevant errors in the App or Sys event logs, but let me know if you'd like anything further from there.
Thanks again for any help you can provide,
Chris
-Single Exchange 2003 server, running SP2
-Running on Windows 2003 32-bit, with SP2
-Was running on an old physical server
-New system is VMWare ESX 4.1
-Used VMWare Converter, installed directly on the server with almost all the default settings to migrate it to virtual.
-I found out today that the Information Stores were not shut down during the migration, but antivirus was
-Symantec Endpoint Protection 11.0, has been turned off during the troubleshooting.
There are about 150 users in the organization spread out across 4 Storage Groups. 15-20 of the users are not able to receive any emails. They are spread out across the Groups, so it's not a single database causing the problem. They can send email without problems, they just can't receive any internal or external messages. All emails to these users are sitting in the "Local Delivery" queue.
Their Outlook and OWA are showing changes correctly, so it doesn't appear to be a connection problem between Outlook and Exchange.
Here is a sample of the Message Tracking Log for an email stuck in the queue for an impacted user:
5/14/2011 11:43 am SMTP: Message Delivered locally to _______
5/14/2011 11:43 am SMTP: Message scheduled to retry local delivery
over and over again.
Other mail delivery on the server seems slow, occasionally no one receives email for 30 minutes, then it all comes in. I'm not having any problems Telnetting into the server, it looks like everything is just getting stuck in the queues.
I also don't see any relevant errors in the App or Sys event logs, but let me know if you'd like anything further from there.
Thanks again for any help you can provide,
Chris
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Did you shutdown the Exchange Services and dismount the Stores before Converting?
ASKER
No, they did not shut those down. We went forward with it because most thing seem to be ok after the conversion.
It's not best practice to keep the services running, do you still have the old server?
ASKER
Yes, but now that server is over 24 hours out of date, which would definitely be a problem. Do you have any thoughts on troubleshooting the system we have?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When you P2V you lose your IP since it typically picks a new nic. Check your IP (make sure it's not dhcp with a new IP in DNS). Flush all the arp cache, dns cache, etc..
ASKER
Yes, we removed the old hidden NIC and set the new VMWare NIC up with the correct static IP. I hadn't cleared DNS or ARP, but did that now with no benefit.
viralrathod, I can try recreating a user's mailbox, will let you know how that goes.
viralrathod, I can try recreating a user's mailbox, will let you know how that goes.
check dns make sure you don't have a wayward entry for exchange that may have been generated if dhcp picked up the ip
ASKER
We were able to fix the problem by rebuilding the affected user's mailboxes, either through deleting/recreating or moving it to a different Information Store and then moving back again.
Thanks for the help!
Thanks for the help!
ASKER
We were able to fix the problem by rebuilding the affected user's mailboxes, either through deleting/recreating or moving it to a different Information Store and then moving back again.
Thanks for the help!
Thanks for the help!
You could probably have run Integrity Checking on the db, and it's propbably still worth compteing that, at the next scheduled downtime. (please note it takes a while to comeplete)
Probably corrupted buy a HOT P2V without services shutdown.
Probably corrupted buy a HOT P2V without services shutdown.