Link to home
Start Free TrialLog in
Avatar of Jay Schwegler
Jay SchweglerFlag for United States of America

asked on

Calendar/Appointment Problems

Over the past 2 days, I've had two different instances of the following series of errors on my Exchange Server for the same person's mailbox:

Event Type:      Error
Event Source:      EXCDO
Event Category:      General
Event ID:      8239
Date:            4/17/2006
Time:            4:24:36 PM
User:            N/A
Computer:      <server>
Description:
An appointment with the subject "" was saved to mailbox <mailbox>. The start time is missing, so the calendaring agent cannot publish the free/busy

Event Type:      Error
Event Source:      EXCDO
Event Category:      General
Event ID:      8206
Date:            4/17/2006
Time:            4:24:36 PM
User:            N/A
Computer:      <server>
Description:
Calendaring agent failed with error code 0x80040229 while saving appointment.

Event Type:      Warning
Event Source:      EXCDO
Event Category:      General
Event ID:      8241
Date:            4/17/2006
Time:            4:24:36 PM
User:            N/A
Computer:      <server>
Description:
An existing appointment with the subject "" in mailbox <mailbox> was modified. The start time, or both the duration and end time of the existing appointment were missing.

ALL of the MS KB articles that I've read indicate that this is a virus scan issue (scanning the M drive), or that the MSExchangeFPBPublish reg entires are missing from the server. I know for a fact that neither are true, I'm not scanning the M:\ drive (my virus scan preferences have not changed in 3 years), and I have verified that the required reg entries are not missing.

What should I look for? I was thinking about running an ESEUTIL and ISINTEG to check for database problems.

These errors do not continually populate the event logs, it has occured twice, once Friday, once today.
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

As it is one user, I have to suspect the mailbox.

Try closing Outlook on the user's machine and then click start, run and type:

outlook /cleanfreebusy

That will flush the free busy information.

It maybe a single calendar item that is corrupt in the user's mailbox.

Simon.
Avatar of Jay Schwegler

ASKER

Indeed, I forgot about that nifty switch. I'll give that a shot tomorrow morning, observe for a day or two and report results.
No dice unfortunatley.

It went the entire day without error until 4:52 and 5:08. I have 2 more sets of the same errors. Just for the heck of it, I took the mail database down last night and ran [eseutil /g] and [isinteg], database checked out okay. Nobody else is reporting any issues.

I'm guessing that there are a few currupted calendar entires, but I have no idea how to locate and remove them.
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
When you say Folder, do you mean export the contents of the calendar object in Outlook, then re-import it all back in?

After the export, should I remove everything inside the calendar, or just re-import it? If so, how do I essentially clear the entire calendar without having to remove each entry?
After the export you need to remove what is left, otherwise the exercise is fruitless.
The quickest way to select everything is to change the view of the calendar to category. This turns it in to a list. You can the select everything and delete it.

Simon.
That sounds good, I'll give it a shot.

He won't be back for a few days, so I'll wait until he gets back since he generates appointments offline. I would rather remove everything clean without having to worry about anything he added offline.
I'm sorry that I'm dragging this out, this question has been open way to long, which is my fault.

I exported the calendar entries, imported them again, everything was fine for a few days. It happened again today, but I finally realized why. He uses ACT for contact management that sync's with his Outlook Calendar. Whenever he sync's his contact information, I get these errors on the Exchange Server. Guess I'll have to contact ACT tech support to see what they say.
I am seeing the same error on my email server. How do I know if the user's outlook is syncing with ACTS? ACTS was once the contact management software in the company before I joined. This is for Outlook 2003 and Exchange Server 2003.