B
BennyGW
Guest
Upgraded from Office 2010 to 2016 (365 subscription). Outlook lasted about 3 minutes before it crashed (Error 1 below). It managed to corrupt one of my mailbox pst files. SCANPST did not fix the issue and had to use Systools to recover the mail box. Recreated the mail box and then imported the mail into the mail box. AT some point Outlook crashed for a second time (error 2), and pointed to an add-in (warning 1) causing issues. Managed to finish the importing of the emails, and guess what Outlook crashed for a 3rd time and corrupted yet another pst file (error 3 below) - looks like the same bug as before. All I did to cause outlook to crash this time was to change the sort order of received mail.
At this point outlook refused to open at all. Used Systools to fix the latest corrupted pst file. Managed to get outlook open now, and all I get on the PST files is 'Cannot expand the folders. The set of folders can not expand. the file ......pst cannot be opened.'. I guess this on all my active email accounts. I have 2 very old pst files that are no longer associated with an email account that do expand.
I feel very entitled to a serious rant at this point, but I don't really have time. I am in the process of trying to meet a very important deadline and this is needlessly sucking up too much of my time. What I would like is a definitive solution that is not going to take hours and hours to fix. I just don't have time.
Error 1
Faulting application name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Faulting module name: ucrtbase.dll, version: 10.0.10586.0, time stamp: 0x5632d166
Exception code: 0xc0000409
Fault offset: 0x00083472
Faulting process id: 0x3d04
Faulting application start time: 0x01d1b27d4efa16b6
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ucrtbase.dll
Report Id: 0ec39e24-1398-4e22-bd68-a64e42745ece
Faulting package full name:
Faulting package-relative application ID:
Error 2
Faulting application name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Faulting module name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Exception code: 0xc0000005
Fault offset: 0x00702dfe
Faulting process id: 0xb2e8
Faulting application start time: 0x01d1b3d1573366e9
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Report Id: bd0b5b96-1fda-11e6-9bea-50e549e5e1ec
Faulting package full name:
Faulting package-relative application ID:
Warning 1
Outlook disabled the following add-in(s):
ProgID: Fuze.Outlook.AddIn
GUID: {00000000-0000-0000-0000-000000000000}
Name: Fuze
Description: Fuze integration for Microsoft Outlook
Load Behavior: 3
HKLM: 0
Location: file:///c:\users\ben\appdata\local\fuzebox\fuze\outlook add-in\fuze.outlook.addin.vsto|vstolocal
Threshold Time (Milliseconds): 1000
Time Taken (Milliseconds): 1375
Disable Reason: This add-in caused Outlook to start slowly.
Policy Exception (Allow List): 0
Error 3
Faulting application name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Faulting module name: ucrtbase.dll, version: 10.0.10586.0, time stamp: 0x5632d166
Exception code: 0xc0000409
Fault offset: 0x00083472
Faulting process id: 0xb7ec
Faulting application start time: 0x01d1b3e802ee09ac
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ucrtbase.dll
Report Id: dcb6a69f-854e-4e02-9ab7-1f0a6366b422
Faulting package full name:
Faulting package-relative application ID:
Hi Ben,
From the description, I understand that you’ve encountered an Outlook 2016 client crashing issue.
Since this is a pure client side issue, please try the following suggestions to see if there is any improvement:
1. Based on my experience, the faulting module name: ucrtbase.dll may have something to do with an add-in called “SharePoint Export Database Launcher”. In addition, from the second error, there is a warning pointed to an add-in that causes the issue. So, please try starting the Outlook 2016 in safe mode to help us eliminate the add-in. You can refer to this article for more information about how to do it.
If you are using Windows 10, please refer to the following steps:
Start Outlook in safe mode Win 10:
Sometimes add-ins can conflict with Outlook. Starting Outlook 2016 in safe mode, which launches Outlook without add-ins loaded, can tell you if this is the problem:
In Windows 10, there is a search box on the Taskbar by default but if you have set to hide this, it will automatically show when you start typing after opening the Start Menu as well. Here type: outlook.exe /safe
If Outlook launches in safe mode:
1. Click File, then click Options, and then click Add-Ins.
2. Select COM Add-ins, and then click Go.
3. Click to clear all the check boxes in the list, and then click OK.
4. Restart Outlook, but not in safe mode.
2. Try running a clean boot to help eliminate the third-party software conflicts.
support.microsoft.com/.../929135
3. Try repairing the Outlook 2016 client.
support.office.com/.../Repair-an-Office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b
4. There is a tool called Office Configuration Analyzer Tool (OffCAT) which can help to identify and resolve known cause. You can refer to:
How to resolve crash and stability issues in Office programs by using the OffCAT tool
support.microsoft.com/.../2939112
If the issue persists after performing the above suggestions, it’s recommended you post a new thread at our Outlook IT Pro Discussions Forum, which is dedicated to dealing with Outlook client side issues. Thanks for your understanding.
Best regards,
Mouran
A bit more information. I did a repair on office and it managed to expand the files after that, I disabled all add-ins, except for microsoft VBA for outlook and Nortons Antispam. There were some share point add-ins, but 'SharePoint Export Database Launcher' was not one of them. This briefly worked, then I got the same error with ucrtbase.dll. Again corrupted a pst file and outlook would not open at all.
Did yet another repair with systools. Uninstalled office 2010, then did another repair (advanced this time). Outlook would still not start, so I renamed the pst file and got it working (if it cant find the pst file it lets ,me select it and outlook starts), except I am back in the place where it can not expand the folders again.
I will try the Office Configuration Analyzer Tool and see if that throws up an issue.
I will also do a reboot, but I really don't have the time to waste on a reboot when win 10 does its updates.
Tip for Microsoft.... it is called 'fault tolerance' - Outlook is a critical tool and more effort from MS to prevent this. It is complete cop out to say something like 'add-ins can conflict with Outlook' or it is a local environmental issue -this is a design issue that MS has not addressed. If I released software that corrupted my clients data I would be sacked.
Ran the Office Configuration Analyzer Tool and it found nothing of interest. A few warning - no red flags.
Running in safe mode has no effect.
Did another repair on Office as well and that had no impact. Outlook well and truly broken.
Continue reading...
At this point outlook refused to open at all. Used Systools to fix the latest corrupted pst file. Managed to get outlook open now, and all I get on the PST files is 'Cannot expand the folders. The set of folders can not expand. the file ......pst cannot be opened.'. I guess this on all my active email accounts. I have 2 very old pst files that are no longer associated with an email account that do expand.
I feel very entitled to a serious rant at this point, but I don't really have time. I am in the process of trying to meet a very important deadline and this is needlessly sucking up too much of my time. What I would like is a definitive solution that is not going to take hours and hours to fix. I just don't have time.
Error 1
Faulting application name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Faulting module name: ucrtbase.dll, version: 10.0.10586.0, time stamp: 0x5632d166
Exception code: 0xc0000409
Fault offset: 0x00083472
Faulting process id: 0x3d04
Faulting application start time: 0x01d1b27d4efa16b6
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ucrtbase.dll
Report Id: 0ec39e24-1398-4e22-bd68-a64e42745ece
Faulting package full name:
Faulting package-relative application ID:
Error 2
Faulting application name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Faulting module name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Exception code: 0xc0000005
Fault offset: 0x00702dfe
Faulting process id: 0xb2e8
Faulting application start time: 0x01d1b3d1573366e9
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Report Id: bd0b5b96-1fda-11e6-9bea-50e549e5e1ec
Faulting package full name:
Faulting package-relative application ID:
Warning 1
Outlook disabled the following add-in(s):
ProgID: Fuze.Outlook.AddIn
GUID: {00000000-0000-0000-0000-000000000000}
Name: Fuze
Description: Fuze integration for Microsoft Outlook
Load Behavior: 3
HKLM: 0
Location: file:///c:\users\ben\appdata\local\fuzebox\fuze\outlook add-in\fuze.outlook.addin.vsto|vstolocal
Threshold Time (Milliseconds): 1000
Time Taken (Milliseconds): 1375
Disable Reason: This add-in caused Outlook to start slowly.
Policy Exception (Allow List): 0
Error 3
Faulting application name: OUTLOOK.EXE, version: 16.0.6868.2062, time stamp: 0x5727d1e7
Faulting module name: ucrtbase.dll, version: 10.0.10586.0, time stamp: 0x5632d166
Exception code: 0xc0000409
Fault offset: 0x00083472
Faulting process id: 0xb7ec
Faulting application start time: 0x01d1b3e802ee09ac
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ucrtbase.dll
Report Id: dcb6a69f-854e-4e02-9ab7-1f0a6366b422
Faulting package full name:
Faulting package-relative application ID:
Hi Ben,
From the description, I understand that you’ve encountered an Outlook 2016 client crashing issue.
Since this is a pure client side issue, please try the following suggestions to see if there is any improvement:
1. Based on my experience, the faulting module name: ucrtbase.dll may have something to do with an add-in called “SharePoint Export Database Launcher”. In addition, from the second error, there is a warning pointed to an add-in that causes the issue. So, please try starting the Outlook 2016 in safe mode to help us eliminate the add-in. You can refer to this article for more information about how to do it.
If you are using Windows 10, please refer to the following steps:
Start Outlook in safe mode Win 10:
Sometimes add-ins can conflict with Outlook. Starting Outlook 2016 in safe mode, which launches Outlook without add-ins loaded, can tell you if this is the problem:
In Windows 10, there is a search box on the Taskbar by default but if you have set to hide this, it will automatically show when you start typing after opening the Start Menu as well. Here type: outlook.exe /safe
If Outlook launches in safe mode:
1. Click File, then click Options, and then click Add-Ins.
2. Select COM Add-ins, and then click Go.
3. Click to clear all the check boxes in the list, and then click OK.
4. Restart Outlook, but not in safe mode.
2. Try running a clean boot to help eliminate the third-party software conflicts.
support.microsoft.com/.../929135
3. Try repairing the Outlook 2016 client.
support.office.com/.../Repair-an-Office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b
4. There is a tool called Office Configuration Analyzer Tool (OffCAT) which can help to identify and resolve known cause. You can refer to:
How to resolve crash and stability issues in Office programs by using the OffCAT tool
support.microsoft.com/.../2939112
If the issue persists after performing the above suggestions, it’s recommended you post a new thread at our Outlook IT Pro Discussions Forum, which is dedicated to dealing with Outlook client side issues. Thanks for your understanding.
Best regards,
Mouran
A bit more information. I did a repair on office and it managed to expand the files after that, I disabled all add-ins, except for microsoft VBA for outlook and Nortons Antispam. There were some share point add-ins, but 'SharePoint Export Database Launcher' was not one of them. This briefly worked, then I got the same error with ucrtbase.dll. Again corrupted a pst file and outlook would not open at all.
Did yet another repair with systools. Uninstalled office 2010, then did another repair (advanced this time). Outlook would still not start, so I renamed the pst file and got it working (if it cant find the pst file it lets ,me select it and outlook starts), except I am back in the place where it can not expand the folders again.
I will try the Office Configuration Analyzer Tool and see if that throws up an issue.
I will also do a reboot, but I really don't have the time to waste on a reboot when win 10 does its updates.
Tip for Microsoft.... it is called 'fault tolerance' - Outlook is a critical tool and more effort from MS to prevent this. It is complete cop out to say something like 'add-ins can conflict with Outlook' or it is a local environmental issue -this is a design issue that MS has not addressed. If I released software that corrupted my clients data I would be sacked.
Ran the Office Configuration Analyzer Tool and it found nothing of interest. A few warning - no red flags.
Running in safe mode has no effect.
Did another repair on Office as well and that had no impact. Outlook well and truly broken.
Continue reading...