Outlook fails to open with error: 'Microsoft Outlook' exited without properly closing your Outlook data file

66

4

After shutting down Outlook forcefully and trying to restart it, the following error is displayed:

'Microsoft Outlook' exited without properly closing your Outlook data file. 'Microsoft Outlook' must be restarted. If this error message recurs, contact support for assistance.

Outlook then exits.

Christothes

Posted 2010-07-14T04:04:59.397

Reputation: 3 597

Answers

60

  • Run Process Explorer and choose "Find Handle or DLL" from the Find menu.
  • Search for '.ost'. This will display all open handles to your Outlook data file.
  • Choose to close all handles to your .ost file
  • Start Outlook again
  • optionally - run C:\Program Files (x86)\Microsoft Office\Office14\SCANPST.EXE

Christothes

Posted 2010-07-14T04:04:59.397

Reputation: 3 597

Both this and the other answer proved to be very helpful for solving my problem. – Ro Yo Mi – 2014-09-09T18:54:16.100

79

I've found that for me this occurs because Outlook crashed for some reason but the Lync 2010 client still has a handle to the .ost file. Exiting Lync completely allows Outlook to restart.

Tom Morgan

Posted 2010-07-14T04:04:59.397

Reputation: 891

Lync is such a sticky piece of crap. Somehow Sametime must have been contagious. – MonoThreaded – 2015-05-04T06:22:53.247

1Also applies to Cisco Jabber – Enilorac – 2016-01-18T16:47:21.960

Your solution worked whereas the accepted answer just told me: (1) The handle wasn't found (2) The .ost file was in use by another program - Lync, as it turns out. – B H – 2019-03-15T14:14:48.817

9I had this exact problem and closing Lync fixed it. – jamesbtate – 2011-08-23T14:14:52.957

4Ran into the same problem, Microsoft Communicator turned out to be the greedy file handler. – Dan Ling – 2012-06-21T14:20:01.197

0

I couldn't find any processes that had a lock on my OST. Further, closing Lync provided temporary relief since I actually need both programs running. I finally just threw in the towel and uninstalled both office 2010 and Lync 2013. I then re-installed office 365 (with Lync). After 2 days, I have yet to see this error again.

Brett

Posted 2010-07-14T04:04:59.397

Reputation: 271

1closing Lync provided temporary relief -- why didn't you just stop Lync, start Outlook, and then start Lync again? – ppeterka – 2016-09-21T07:26:54.950