Error when accessing Exchange 2007 via Outlook web access

We had complete hardware failure on an SBS 2008 box.  Could not do bare metal restore, so we did a complete reinstall, recreated all users and did a file level restore.  All is well except for exchange.  We had a backup offline at Ibackup.  We restored this and we were unable to see old emails.  We purchased Ontrack’s Powercontrols  and were able to retrieve all of the emails from the old .edb file. Outlook Web Access was working then after restore of the mailboxes it has stopped.  We are receiving “The item that you attempted to access appears to be corrupted and cannot be accessed.” with additional info that I will post below.

I have run ESEUTIL with /p and /d and I have run ISINTEG -s ServerName -fix -test alltests.  This did not correct the problem.

Please help

Additional Error Info:


Request

Exception
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.Core.UserConfigurationUtilities.GetFolderConfiguration(String configurationName, UserContext userContext, StoreId folderId)
Microsoft.Exchange.Clients.Owa.Core.UserContext.GetAllFolderPolicy()
Microsoft.Exchange.Clients.Owa.Core.UserContext.OnPostLoadUserContext()
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
cooperrdAsked:
Who is Participating?
 
Exchange_GeekConnect With a Mentor Commented:
Issue seems to be more of a corruption of users mailboxes. My best bet if you create a new mailbox - it would absolutely fine.

If the new users work fine work towards removing corruption from existing users, run the following command on a work station of user

Outlook /resetfolders
Outlook /clearnreminders
Outlook /cleanfreebusy

if the above commands doesn't help use MFCMapi to delete reminders

Resolution
- Using MFCMAPI (downloadable from Google)search for Reminders folder in order to delete them.

1-Run MFCMAPI
2-Go to Session->Logon and Display Store Table
3-Select your users profile
4-Select users Mailbox
5-Expand "Root Container"
6-Right click  "Reminders" and select "Open Contents Table"
7-New Window Launches with Title Reminders
8-Select all the reminder items listed there, Right click and select "Delete Message"
9-Close MFCMAPI

- Using MFCMAPI deleted the Reminders folder using the below steps.

1-Run MFCMAPI
2-Go to Session->Logon and Display Store Table
3-Select your profile
4-Select Mailbox
5-Expand "Root Container"
6-Right click  "Reminders" and select "Delete Folder"
7-Check the box "Hard Deletion" and OK
8-Close MFCMAPI
9-Launch outlook with /resetfolders switch
10-Test owa

If the above also doesn't help - worse case scenario, export data to PST for affected users - create new mailboxes and provide PST to attach in OL (DO NOT IMPORT PST FILES)

Wow, that is a pretty long action - plan, hope it helps :)

Regards,
Exchange_Geek
0
 
omprakash_nathCommented:
Do you get this error with both Outlook and OWA ??
0
 
cooperrdAuthor Commented:
omprakash_nath  - it is only in OWA.

Exchange_Geek - Do I run this at the server level or at each work station (40 work stations)?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Exchange_GeekCommented:
Start off with one of them and check if it works for you OR Not.

Regards,
Exchange_Geek
0
 
cooperrdAuthor Commented:
The outlook commands did not work - is MFCMAPI a server process or workstation?
0
 
Exchange_GeekCommented:
Work station process.

Regards,
Exchange_Geek
0
 
ExchangePanditCommented:
Try creating a new Database and then move one affected user to that new DB. See if that helps.

Regards
0
 
cooperrdAuthor Commented:
I used the process that you outlined earlier. Except there was no reminders folders.  So I did the following based on additional research;

"Ok, we had the same problem after a huge database issue. What I finally found to work was to use mfcmapi.exe and open that user up in there. If you right click on the inbox, you can choose open associated contants table. This sill show you a bunch if junk. For us, this was the corrupted data in question. If you sort by subject and remove all of the rules labelled as Err:0x8004010F=MAPI_E_NOT_FOUND this will resolve your problem. We also found that for at least one user, their OOF didnt work either. We had to do the same thing in the calendar to resolve this issue"


 It worked on one mailbox only.  I am installing updates and service packs now.  I guess the next step is to push out to .pst files and create a new mail store.  I really believe the attempted restore of the IBackup files really corrupted the file beyond repair.

The weird thing is that it works internally with Outlook.
0
 
Exchange_GeekCommented:
I'd agree on the point where you got the data imported - you ideally shouldn't ever import such files, provide the data using PST to all the users and ask them not to fiddle around importing such data into the Exchange stores.

Fair enough, MFCMapi is my best friend on such issues and i'm glad it did help you too.

Hoping to hear from you soon.

Regards,
Exchange_Geek
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.