We help IT Professionals succeed at work.

Outlook email message body empty after migrating to Exchange 2010

Kirchtoe
Kirchtoe asked
on
I am currently upgrading from Exchange 2003 to Exchange 2010.  When I migrate an email box using the Exchange 2010 EMC the mailbox migrates from the 2003 database to the 2010 database OK but noticed that after the migration, email headers are OK but the message content is blank.  Mail clients are Outlook 2007 and Outlook 2010 and both behave the same way.
Comment
Watch Question

Alan HardistyCo-Owner
CERTIFIED EXPERT
Top Expert 2011

Commented:
Do you have AV on the Exchange 2010 server and if so is it ESET Nod 32 by any chance?
Manpreet SIngh KhatraSolutions Architect, Project Lead
CERTIFIED EXPERT
Top Expert 2013

Commented:
Do you see the same behaviour with OWA\Webamil ?
What is the AV and do we have ExchangeForefront enabled on the HUB ?
What if the users sends an email to Himself ?

- Rancy

Author

Commented:
alanhardisty,

We are using AVG Business Edition 2012.  I'm not sure what you are referring to with ESET Nod 32.

Author

Commented:
Rancy,

I don't yet have OWA configured on the new server so I don't know at this point.
AVG is installed on clients and 2010 Exchange server.  Exchange Forefront is not enabled.

Author

Commented:
For all:

If I move my mailbox to the new Exchange server and receive a new email, I DO see the message body when I get my email notification in the lower RH corner of the screen.  But, when I open the email or look at it in the preview pane, it is blank.
Co-Owner
CERTIFIED EXPERT
Top Expert 2011
Commented:
Most blank email body messages are caused by AV and according to this previous EE question, AVG Business seems to be the cause:

http://www.experts-exchange.com/Software/Internet_Email/Anti-Virus/Q_27314454.html

I would uninstall it and see if the problem goes away.  Disabling it isn't an option as it still has its hooks into Exchange.

ESET Nod 32 is another AV program with known problems relating to blank email bodies.

Alan

Author

Commented:
Removing AVG from the Outlook client computer fixed the problem.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.