Name of the module that generated the error: OUTLMIME.DLL, version. Name of the application that generated the error: OUTLOOK.EXE, version. The best way to do this is to take a look at the Windows Event Log ( Control Panel> Administrative Tools> Event Log), which should present the following error entry within the “Applications” panel: Needless to say, since there is a ton of other common scenarios that could cause such kind of crash, the first thing to do is to make sure that we’re actually dealing with this one. Not surprisingly, the problem tends to occur in all scenarios where there are a lot of different IMAP accounts installed on the system and/or with a large number of e-mails (and/or used space). This is a rather common issue that occurs in most pre-365 versions of MS Outlook (up to Outlook 2016 included): in all these versions the IMAP protocol has been implemented, to put it mildly, in as rather “problematic” way, which often causes synchronization issues and other nasty bugs. The problem, as you can easily guess by the post title, is that MS Outlook abruptly crashes during the startup (either immediately or after a short while), with the typical error popup message warning the user that “Microsoft Outlook has stopped working”: Has anyone experienced this before and if so can you help me fix it please? Is this a bug with Outlook or Exchange? I am going to test the same scenario on a machine running Outlook 2010 to see if the same issue still persists.In this post, we’ll address a common issue occurring with most versions of MS Outlook with one or more IMAP accounts configured locally ( IMAP is an acronym for Internet Message Access Protocol – for more info, read here). 1000, time stamp: 0x531f9fbaįaulting application start time: 0x01cf6453441df03bįaulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXEįaulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll 1503, time stamp: 0x52b0b282įaulting module name: mso.dll, version. This is the error logged in event viewer:įaulting application name: OUTLOOK.EXE, version.
Using OWA, things seem to work as expected.
We are running Exchange 2013 CU3 with no other versionsĮverything works fine until the user attempts to use the Scheduling assistant, as soon as they do, Outlook promptly crashes. I have a very annoying problem with Outlook 2013 that occurs when a user attempts to create a meeting, inviting and external attendee and uses the Scheduling Assistant to help them organise timings.
0 kommentar(er)
