Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1000 Source: Microsoft Office 11
|Source: Microsoft Office 11|
|Maintenance: Recommended maintenance tasks for desktop applications|
Faulting application <application> version <version> stamp <stamp> faulting module <module> version <module version> stamp <stamp> debug 0 fault address <fault address>.
|English: This information is only available to subscribers. An example of English, please!|
I had this problem with Outlook 2003. I fixed it by deleting all content: Documents and Settings/username/Application Data/Microsoft/Outlook/ directory.
In my case, deleting/removing outcmd.dat (located in :\Documents and Settings\<your profile>\Application Data\Microsoft\Outlook fixed the problem. Close your Outlook before removing this file.
I had this issue with office 2003 Pro, Excel 2003 crashing and not saving files. Each time I opened and a spreadsheet and made changes. When I went to save the excel spreadsheet it would crash Excel and open it in a recovery window. Event ID 1000 The local computer may not have the necessary registry information or message DLL fils to display messages from the remote computer. To resolve this issue I installed Office 2003 Service Pack 3 which has resolved the issue.
Module sonichddemuxer.dll - Associated with the sonic / roxio video codec pack.
Faulting module: mshtml.dll. In our case, this error was caused by editing corrupt text after it had been pasted from another source into an email. Resolved by copying into a new Word document, amending it and pasting finished product into a new email.
In my case it was the "outllib.dll" in "c:\Program Files\Microsoft Office\OFFICE11\". Re-installing Office didn't fix the problem, but replacing the file fixed it.
I had an issue while opening PowerPoint files (this would show up in the EventViewer):
Faulting application powerpnt.exe, version 11.0.8334.0, stamp 4d6ea32b, faulting module msvcrt.dll, version 7.0.2600.5512, stamp 4802a188, debug? 0, fault address 0x00037fd4.
I found the security update KB2454588 for PowerPoint under Office Update and removed it using Add /Remove Programs. Rebooted the system and the problem was gone.
In my case, with Excel 2003 SP3, this fix worked for me:
1. Close all open programs.
2. Open Registry Editor (Start > Run > Regedit).
3. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Office\Excel\Addins\BtOfficeAddin.BtOfficeIntegration.x
4. Change the value of LoadBehavior to 0.
Word always started in Save mode. Reinstalling Office didn’solve the problem. The solution that worked for me was to delete normal.dot file.
For me, to fix this problem, I had to reinstall the printer driver.
In my case, all other suggested fixes failed. This fix worked for me:
1. Close Word and open Registry Editor (regedit)
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\ Word. Inside the Word folder, you will see a folder called "Data". Delete this Data folder and relaunch Word. Just like with the global template, Word will look for this Data folder and recreate it fresh if it cannot find it.
TIP: Be warned that this key holds all your toolbar settings and therefore, deleting it will set your toolbars back to the way they were when you first installed Word, so you will have to recreate the customizations from scratch.
I do not remember where I found this info, but it worked perfectly, and my Data folder was automatically regenerated. (I did backup the original key before deleting it though, just in case).
Word or Powerpoint might crash when the registry path to your Temporary Internet Files contains non-english charset characters. Solution: Create a temp folder, e.g. c:\temp, then run "regedit" and edit HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders. Rename the "Cache" key to "Cache2" (just in case something goes wrong) and create a new REG_SZ key "Cache" with value "c:\temp".
I resolved this problem by disabling the Zimbra Client add-in in Outlook.
In my case, the problem was caused by "recent files" with long path/filename. Deleting HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List made the problem go away.
I had problems with Excel crashing when I tried to save. I installed Office 2003 SP3 and the problem disappeared.
In my case, the Outlook add-in "Caesar Client Extension" (caeexclt.dll) caused the failure while closing Outlook. Disabling the add-in resolved the problem.
See ME931270 for a hotfix applicable to Microsoft Dynamics CRM 3.0.
This problem occurs if you click one of the Microsoft Dynamics CRM folders in the Microsoft Dynamics CRM laptop client for Outlook before you click "Go Offline". For example, you click the "Account" folder before you click "Go Offline". See ME928272 for a hotfix applicable to Microsoft Dynamics CRM 3.0 and Microsoft CRM client for Microsoft Office Outlook, when used with Microsoft Dynamics CRM 3.0.
As per Microsoft: "This problem occurs because of a difference between the ReplidMap table in the memory on the server and the ReplidMap table in the Jet database. This difference causes a stack overflow that causes Outlook 2003 to crash". See ME922617 for a hotfix applicable to Microsoft Exchange Server 2003.
See ME912805 for additional information about this problem.
I had a user who was going through a continous shutdown and restart of Outlook 2003. The culprit in my case was a software called "SnagIt". Removing SnagIt 7.0 solved the problem.
Printing from PowerPoint 2003 resulted in the application crashing as soon as CRTL+P or File/Print was licked. The setup was Xerox Workcenter Pro 45 with a PCL6 driver. This was also the default printer. After changing the default printer, I was able to choose from the printers and they all worked except for the Xerox printer. Removing and re-installing the Xerox printer solved the problem.
In our case, we were using a Linksys Print server USB adapter to put an Epson 9650 on the network. When each Windows XP Professional machine was set to use that as the default printer, Office 2003 would crash repeatedly. Setting the default printer to the "Microsoft Office Document Image Writer" fixed our issue.
Follow the link to "EventID 1000 from source Microsoft Office 10" for information on this error.
From a newsgroup post: "In my case, this problem was caused by Snag-It, an add-in for Outlook. I had to disable the add-in for the problem to go away. Make sure all your add-ins are compatible with Microsoft Office 2003".
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 1000 from source Microsoft Office 10, Office 2003 Service Pack 3|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated