• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1612
  • Last Modified:

Outlook 2013 crashing for one user in particular - mailbox corrupted?

We recently migrated our mailboxes from Exchange 2003 to Exchange 2010, while also updating Office from 2003 to 2013. Everything worked fine with the exception of one single user. His mailbox will open fine in Outlook 2003, but crashes Outlook 2007, 2010, or 2013.

I've tried different PCs, tried Safe Mode, Outlook still crashes on "Processing". Interestingly, if I go to Start > Outlook 2013 > New Email Message it will open the New Message and even send it. If I then open Outlook by right clicking in the system tray and selecting Open Outlook, it will then crash, although the window will open and I can see the Mailbox and folders listed.

My assumption is that something is corrupted in his mailbox. I was recommended to try MFCMAPI, but I'm not sure what to do with that tool once I'm viewing the mailbox data.

Has anyone seen a problem like this before? Any advice or direction would be appreciated.

I've listed below what I'm seeing in the Event Viewer.

Log Name:      Application
Source:        Application Error
Date:          4/10/2014 1:01:54 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ABL120901
Description:
Faulting application name: OUTLOOK.EXE, version: 15.0.4569.1503, time stamp: 0x52b0b282
Faulting module name: OUTLOOK.EXE, version: 15.0.4569.1503, time stamp: 0x52b0b282
Exception code: 0xc0000005
Fault offset: 0x0008bce5
Faulting process id: 0x56c
Faulting application start time: 0x01cf54f7b0b704c1
Faulting application path: C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
Report Id: f64d5265-c0ea-11e3-9541-534e57000000
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-10T20:01:54.000000000Z" />
    <EventRecordID>54548</EventRecordID>
    <Channel>Application</Channel>
    <Computer>ABL120901</Computer>
    <Security />
  </System>
  <EventData>
    <Data>OUTLOOK.EXE</Data>
    <Data>15.0.4569.1503</Data>
    <Data>52b0b282</Data>
    <Data>OUTLOOK.EXE</Data>
    <Data>15.0.4569.1503</Data>
    <Data>52b0b282</Data>
    <Data>c0000005</Data>
    <Data>0008bce5</Data>
    <Data>56c</Data>
    <Data>01cf54f7b0b704c1</Data>
    <Data>C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE</Data>
    <Data>C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE</Data>
    <Data>f64d5265-c0ea-11e3-9541-534e57000000</Data>
  </EventData>
</Event>
0
altshuler_tech
Asked:
altshuler_tech
  • 2
  • 2
1 Solution
 
BembiCEOCommented:
If you move mailboxes from 2003 to 2010, the move will usually fail if the mailbox is corrupted. Nevertheless if I follow your description, you tried to use a different PC and the same error comes up there.

First at all makes sure, your Office is up to date.

What he could observe in the past was an issue, which comes up with older items in the calendar. We had recuring calendar items which produced trouble in newer version.
This also can impyl, there there are other items in the mailbox, which may not to be regognized by the movement process but comes up now in outlook.

You may acces the mailbox via OWA and tr to identfy items like calender recuring items, invitations, invitation confirmtiones etc, which are still in the mailbox.

You may also try to export the mailbox into a PST (EXMERGE / EXFOLDER) to see, if there are errors during the export what can give you a hint, which items are corrupt.

As mailbox items from older exchange may have a lot of MAPI tags including permissions, such MAPI tag may produce some trouble, if something went wrong in the past.

Another option to identif items is to move them into a different folder. THis assumes that you have a chance to start outlook. If you moe items and outlook crashed, you can at least identify where to search.
0
 
altshuler_techAuthor Commented:
Bembi,

Thank you for pointing me in the direction of the older calender items. I did find several of those dating back to as far as 2001. It appears that they were long ago synced from a Palm Pilot. Unfortunately deleting these items did not solve the problem. I'm wondering if maybe there are some Contacts that were created then as well that are creating the issue, but I'm unable to tell at the moment.

I'll be working on this again today and will update.

Thanks
0
 
BembiCEOCommented:
At least it is a point to search. As mail items are using a lot of MAPI tags, which are added by any kind of clients, a disruption of the MAPI tags or the permission set of an item can produce strange errors.

What is a try is to create a second mailbox, create a profile for this mailbox, give permissions for this account to the old mailbox and move items from the old to the new mailbox. If outlook starts to make trouble with the new mailbox, you can possibly localize the source to the items you moved. Or Outlook produces an error when you try to move it.
0
 
altshuler_techAuthor Commented:
Thanks Bembi. Sorry I was out of the office unplanned. I ended up just having to create a new mailbox and it solved the Outlook issue.
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.

Join & Write a Comment

Featured Post

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.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now