Problem Event Name: APPCRASH
Application Name: OUTLOOK.EXE
Application Version: 14.0.4760.1000
Application Timestamp: 4ba8ff82
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18869
Fault Module Timestamp: 556366f2
Exception Code: c0000005
Exception Offset: 000000000005107c
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033
Additional information about the problem:
LCID: 1033
skulcid: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflp
Problem signature:
Problem Event Name: APPCRASH
Application Name: OUTLOOK.EXE
Application Version: 14.0.4760.1000
Application Timestamp: 4ba8ff82
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18869
Fault Module Timestamp: 556366f2
Exception Code: c0000005
Exception Offset: 000000000005107c
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033
Additional information about the problem:
LCID: 1033
skulcid: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflp
Hi,
I have noticed the issue occurred on one specific user.
So I think the issue is related to the outlook side.
Please also run outlook under safe mode and online mode ,then check if the issue persists.
Regards,
David
- Edited by David Wang_Microsoft contingent staff 4 hours 7 minutes ago
Hi,
I have noticed the issue occurred on one specific user.
So I think the issue is related to the outlook side.
Please also run outlook under safe mode and online mode ,then check if the issue persists.
Regards,
David
- Edited by David Wang_Microsoft contingent staff Wednesday, August 05, 2015 3:18 AM
NO issue is not related to the outlook side, I tried on many desktop with diffident version on outlook but no luck, also tried by running outlook under safe mode and online mode but same issue.
So I think issue is only with user's AD account or mailbox.
Sounds like it could be a corrupted mailbox or corrupted item in the mailbox.
Try a mailbox repair job with New-MailboxRepairRequest:
https://technet.microsoft.com/en-us/library/Ff625221(v=EXCHG.141).aspx
If that doesn't work, then try to Export the mailbox to PST through New-MailboxExportRequest:
Then Disable(Don't delete) the exchange user and recreate the mailbox. Try to access the account through Outlook after that. If that works, then try to import the PST into the mailbox and try to access the account again.
- Proposed as answer by David Wang_Microsoft contingent staff 6 hours 30 minutes ago
Thanks for your suggestion, I was also thinking to go with second option...
Now I will try first option... and ll update the same ...
Thanks again, hope this will resolve issue.
I would. It's the least invasive option. All it will do is check the mailbox for any issues and fix them if there is.
If the repair doesn't work, then recreating the mailbox is the big hammer approach, but will point you to where the problem is. If the issue still occurs after the mailbox recreation (before importing the PST back into it) then there's a problem with the AD account. Usually if there are corrupted items in the mailbox, the PST export will give an error indicating what item it encountered a problem with.
I configured user profile in such a way that email will delived to Personal folder instead of .ost server inbox.
and that work here and when I tried to set back deliver location to Inbox it again started giving same issue.