Exchange 2007 OWA when using IE returns corruption error in preview pane only

I have a client with an SBS 2008/exchange 2007 environment. All of a sudden one user receives the following error ONLY when accessing OWA using IE (in full interface mode). Folders tree, Contacts, Calendar lists (but not body preview) etc all work fine.

Also, if you reply or forward the message you can read the body (HTML and text only) fine.

Just to confirm, OWA light works fine (using any browser) as well as Outlook 2007 client and iphone.

So far we can only find one user that this applies to.

I've read a number of forum responses to similar issues as this that suggest to re-create the users mailbox but I think that's a little crude. Would appreciate an elegant solution to this one.

The exchange database looks fine, backups are truncating logs and no other events or issues indicating corruption at the database level.

If you look at the call stack it refers to categories. I wonder if there is something in how categories are used in OWA/IE (ReadMessage.aspx)?

User host address: <IP>
User: <USER>
EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=<USER>
SMTP Address: <email>
OWA version:
Mailbox server: <SERVER>.<DOMAIN>.local

Exception type: Microsoft.Exchange.Data.Storage.CorruptDataException
Exception message: The configuration object data is corrupted. Field = UserConfigurationType.

Call stack

Microsoft.Exchange.Data.Storage.UserConfiguration.BuildConfigurationFromQueryItem(Folder folder, Object[] row)
Microsoft.Exchange.Data.Storage.UserConfiguration.GetIgnoringCache(UserConfigurationManager manager, Folder folder, String configurationName, UserConfigurationTypes freefetchType)
Microsoft.Exchange.Data.Storage.UserConfigurationManager.InternalGetUserConfiguration(StoreId folderId, String configurationName, UserConfigurationTypes freefetchDataType)
Microsoft.Exchange.Clients.Owa.Premium.Controls.CategorySwatch.RenderCategories(OwaContext owaContext, TextWriter writer, Item item)
ASP.forms_premium_readmessage_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
System.Web.UI.Page.Render(HtmlTextWriter writer)
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tried disabling and re-enabling OWA for the user? you may also want try moving user to another SG?
kobalt_systemsAuthor Commented:
thanks kpa, I tried disabling and enabling OWA, dice

I then moved mailbox to another SG, dice
Madan SharmaConsultantCommented:
how about owa light access it that working fine  ?this issue with particular user or with all the users ?

if this issue is with all the users then try removing owa virtual directory using exchange powershell and then create new one this will solve your issue.
for more details check this link:-

to remove :-
to create new again:-
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

kobalt_systemsAuthor Commented:
Hi akicute,

Owa light is fine on all browsers even IE.

Just one user (so far) so not sure if I should recreate owa vd...

Madan SharmaConsultantCommented:
did you check on another pc there may issue with particular pc or ie
kobalt_systemsAuthor Commented:
Yes, have tried different machines (windows 7 and windows server 2008)
Madan SharmaConsultantCommented:
As it is only with single user So we have work only for single user. Follow these steps to fix up this issue:-

Suppose your user name is so

1. Create a new user as and test it for owa access as well as outlook after successful testing proceed to next step
2. Go to the property of => Email addresses tab => Uncheck Automatically update email addresses based on policy then change his default email address as
3. Go to property of => Email addresses tab => uncheck automatically update email addresses bases on poilcy then add new email address as and make it default e-mail address Not this will be the active mailbox for your user.
4. Now export your old mailbox to pst and import it to new mailbox.
and you have done the process.

This process may be lengthy and complicated but it will fix up your issue and you don't need to mess up with complete server settings

Good Luck.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kobalt_systemsAuthor Commented:
Hi Akicute,

Thanks for that....I was trying to avoid re-creating the mailbox and pinpointing the underlying cause in case there is something else going on with the database/exchange that I need know about.

If no-one else has any suggestions I'll run through yours and let you know how I go.

thanks again
kobalt_systemsAuthor Commented:
I used a different technique to re-create the mailbox but it worked OK after the re-creation
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.