Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 5000 Source: MicrosoftOffice12

EventType offdiag12 P1 f4d24103-ff6c-4a52-8866-8e88fbc6cde42851c652-94cb-4514-91e3-2d54a7223cf3 P2 NIL P3 NIL P4 NIL P5 NIL P6 NIL P7 NIL P8 NIL P9 NIL P10 NIL.
If you have the Skype or Google toolbars installed try removing them. Also this may be caused by an add-in that is misbehaving.
In my case, Outlook would not open for one user. I had the user log off which promted for a force close on the Outlook.exe file. When they logged back on it was runing fine.
We use MS Office 2007 sp2  in win xp sp3 desktops and we're starting to see this error more and more. We are centralized for Exchange and users in the remote offices get the error more often. I have people who get it daily.  Almost everyone has had it once. Once you get it any add-ins to Outlook stop working. The only option is to reboot. We have disabled all add-ins except Filesite (our document management system) and users still get it. We really can't disable our DM and say we're working). Users who proxy get it more and so do users who do 'advanced find'. We have opened tickets with MS and Autonomy and both pretty much say it isn't their issue.
EventType officelifeboathang, Application outlook.exe - In my case, Outlook freezes when sending a message and Event ID 5000 is created in Application log. Outlook may be started in Safe Mode and sends messages normally. Disabling Add-ins and re-enabling one by one to find the culprit may help.
EV100127 (a link to the "Officelifeboathang" thread on Microsoft's Office System Suites and Programs TechCenter) provides some details on what different people tried, what worked for some and what didn't.

I kept getting this only on some machines that would try to run the Office Enterprise 2007 setup.exe to install Office. It would fail almost immediately, generating an error report, and throwing this event to the event log.

After trying many things, I finally discovered there must be something wrong with the source files as I can run setup from an identical installation source copy on another server. I am also able to run setup if I remove the *.msp files for SP1 from the \updates folder. I'm currently running windiff to look for differences in the files, but there is nothing obvious wrong with the file sizes or date/time stamps that I can see, and will recopy to the source.
Sometimes, various add-ins may cause this. For example, if Outlook is the one affected by this problem, check the add-ins by goint to Tools, Options, Other, Advanced Options, Add-In Manager (these are applicable to Outlook 2003). Try disabling some of them (if there are any) and see if it improves its reliabillity.

On a support forum, a Microsoft engineer suggested that the Office installation was corrupt and recommended an uninstall and a clean reinstallation.

Types of events (EventType):
- office11shipassert
- office12asserttimer
- offdiag12
- clr20r3 (related to .NET)
- officelifeboathang
- mptelemetry (related to MS Windows Defender)
- bcm (related to Business Contact Manager)
- office12setup (appears during Office setup)
- crmmanaged (related to .NET)
This error might occur if you are trying to install Office 2007 on a server running x64 version of Windows Server 2003 with Terminal Services in relaxed security. For a workaround, see Microsoft ME927476.
A number of reasons can cause this problem. From a newsgroup post:

Reason 1: Large .pst or .ost file.
Are you using a large .pst or .ost file? If your .pst or .ost file is larger than 2GB, you may experience a performance issue in Outlook 2007. In order to accommodate new features Outlook 2007 introduced a new data structure for .pst and .ost files. In this new data structure the frequency of writing data to the hard disk increases as the number of items in the .pst or .ost files increases.

To resolve this problem use one of the following methods:
- Reduce the size of the Exchange mailbox.
- Use an online mode profile instead of a cached mode profile.
- Split your large .pst file into several smaller .pst files.
- Use a filter to restrict the items that you synchronized from Exchange into your .ost file.
For more information, please refer to ME932086.

Reason 2: Windows Desktop Search 3.0.
Have you installed any desktop search engine such as Windows Desktop Search 3.0? If this is the case, please temporarily uninstall it and then test the issue.

If this does not match your situation then please also try some suggestions below to narrow it down:
- Temporarily turn off/remove antivirus program. Many times such issue can be caused by the antivirus program currently running on the machine. Please temporarily turn off or remove antivirus application and see if this scenario is gone.
- Temporarily remove Adobe Reader. Sometimes Adobe Reader can also cause this issue. If you have this program installed on your computer please temporarily remove it and see if this issue can be resolved.
- Test in Outlook Safe Mode. Outlook Safe Mode can narrow down issues which are caused by any extensions corrupted resources files registries or templates. Click Start -> Run. In the Open box type: "Outlook /safe" (without the quotation marks).
From a newsgroup post: "I started Outlook with the /Cleanviews switch and disabled McAfee email scan. That fixed the problem". See ME197180 for information on Outlook command-line switches.
Outlook does not print if "Print Exactly One Month Per Page" is checked. To uncheck this option follow these steps:

1.On the View menu, point to Go To, and click Calendar.
2.On the File menu, click Print.
3.Click Monthly Style, in the Print style list.
4.Click Page Setup and deselect the "Print Exactly One Month Per Page" option.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.