Public calendar displays incorrect data

Public calendar displays incorrect data

Post by sfellma » Tue, 06 Apr 2004 23:42:45

| Content-Class: urn:content-classes:message
| From: "Jason" < XXXX@XXXXX.COM >
| Sender: "Jason" < XXXX@XXXXX.COM >
| Subject: Public calendar displays incorrect data
| Date: Tue, 23 Mar 2004 07:52:40 -0800
| Lines: 17
| Message-ID: <d69f01c410ee$df3b1ab0$ XXXX@XXXXX.COM >
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQQ7t87wWLrFql0Rvmivz+0ZJu6EQ==
| Newsgroups: microsoft.public.exchange2000.clients
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.exchange2000.clients:18666
| NNTP-Posting-Host: tk2msftngxa08.phx.gbl
| X-Tomcat-NG: microsoft.public.exchange2000.clients
| Hello,
| We have one central "company" calendar (Exchange 2000)
| which the entire company views, and one 2 Publishing
| editors creating/modifying said calendar. One client
| (Outlook 2000) has been displaying the data incorrectly
| for a few weeks. When an appointment is created, ie an all
| day sales meeting on April 2, it is displayed ON THIS
| CLIENT ONLY as 11:00 April 1 to 11:00 April 2. Also, it is
| displayed with clocks, and this is not the case on any
| other machine. Only NEW entries are displayed this way. I
| have compared the view settings to other machines without
| the problem, and ensured they match (field, etc..).
| Yesterday this happened to another client. How can I fix
| this??
| Thanks!
| Jason


Cases like yours are better handled by opening a support incident with us
- support details are at If you want to investigate
yourself before making that investment, I would look at the view - current
view menu for the affected user. Since the views for the folders are
published, and only a couple of folks are seeing problems, I would guess
that the view on the PF is OK, but again, this is an issue that may require
more that us posting back and forth.

Good Luck,

Scott Fellman