When you try to view an appointment in the Microsoft Outlook calendar, you may receive an error message, event messages may be logged in the event log, or the Microsoft Exchange Information Store service may not run

When you try to view an appointment in the Microsoft Outlook calendar, one or more of the following results may occur:

• You receive the following error message:
  Can't open this item. Network problems are preventing connection to the Microsoft Exchange Server computer.
• The Microsoft Exchange Information Store service does not run on the Microsoft Exchange 2000 Server computer.
• You receive the following event log messages on the computer that is running Microsoft Exchange 2000 Server:

  Event Type:	Information
  Event Source:	DrWatson
  Event Category:	None
  Event ID:	4097
  Description:
  The application, ApplicationName, generated an application error The error occurred on Date and Time. 
  The exception generated was C0000005 at address MemoryAddress (FunctionName) 
  

  Event Type:	Error
  Event Source:	EXCDO
  Event Category:	General 
  Event ID:	8206
  Description:
  Calendaring agent failed with error code 0x80040229 while saving appointment. 
  

  Event Type:	Warning
  Event Source:	EXCDO
  Event Category:	General 
  Event ID:	8230
  Description:
  An inconsistency was detected in UserName@Domain.com: /Calendar/Appointment.EML. 
  The calendar is being repaired. If other errors occur with this calendar, 
  please view the calendar using Microsoft Outlook Web Access.
   If a problem persists, please recreate the calendar or the containing mailbox. 
  

A calendar entry contains a time zone value for the appointment that is not incorrectly formatted. This calendar entry causes the Microsoft Exchange Information Store service to crash.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.This hotfix will stop the appointments that are created without the carriage return and line feed characters.

To remove the entry that is incorrectly formatted, you can use the Information Store Viewer (Mdbvue32.exe) that is located in the \SUPPORT\UTILS\I386 directory of the Exchange Server CD. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Note Because of file dependencies, this update requires that you install the Exchange 2000 Server Post-Service Pack 3 update rollup. For more information about the latest Exchange 2000 Server service pack, click the following article number to view the article in the Microsoft Knowledge Base:

The following Web site describes the format that should be used to create the time zone value for the appointment:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.