"SchedMgr: Error processing calendar profile document (NoteID: NT000020FA)
in database mail/gordons.nsf: Appointment record not found"
The user in question is experiencing some flaky behaviour with his mail
database. My guess is that the database is corrupt and I should copy it and
then he should use the new copy. However, I am not so familiar with the
Calendar Profile Document ( I read what it is in the Lotus 4.6 book, but
that didn't really help).
Does anyone have any ideas?
Regards,
Bryan S
Troubleshooting Schedule Manager Errors in C&S with Notes/Domino 4.5x/4.6x
Problem:
What do the Schedule Manager ("SchedMgr") errors mean in the Notes/Domino
4.5x/4.6x log file?
Solution:
The Schedule Manager errors in the Notes log file report information about
certain databases that may have a mismatch of a certain field in a calendar
entry, with respect to the name that is listed in the Busytime.nsf file and
the Public Name & Address Book (NAB). This does not necessarily mean that
the Calendaring & Scheduling system is not working.
The proper way to troubleshoot these errors is to analyze the database by
looking at the Note ID which Schedule Manager is reporting the error on. To
do this you need to create a new view in the database that is receiving the
error. If you are not going to create this new view on the server, you must
make a copy of the database at the operating system level. Do not pull a
new replica or a new copy of the database; doing so will change the Note ID
stated in the error message, and the problem will therefore be impossible to
troubleshoot.
To create the view, do the following:
1. Open the database in question on the server (or make a copy of the
database at the operating system level).
2. Select Create, View.
3. Give the View a name, such as NoteID.
4. Make it a shared view and select OK.
5. Select the Design view.
6. Double-click the new view that was just created.
7. Select the column and select Design, Column Properties.
8. Type in a name for the column, such as NoteID.
9. In the formula pane, select Formula.
10. Delete anything in the Formula pane and enter the formula: @NoteID
11. Press ESCAPE and select Yes to save the design.
Now refresh the view and you will see all of the Note IDs in the database.
Match up the Note ID that the Schedule Manager is reporting an error on in
the log and analyze the document properties of that note ID. The field to
look for would be $BusyName. Check to make sure that that name exists in
the Busytime.nsf file and the Public NAB.
Use this procedure for Schedule Manager errors that point to a Note ID and a
database.
Known Schedule Manager Errors
"SchedMgr: Error processing calendar profile document (NoteID: NT00xxxxxx)
in database xx.nsf: Appointment record not found"
The appointment record or resource/room in the Resource Reservation database
has been deleted. This issue has been reported to Lotus Quality
Engineering.
A calendar entry is deleted in Organizer . This issue has been reported to
Lotus Quality Engineering.
"Can't Find User in Name and Address Book"
The $BusyName in the Note ID does not exist in the NAB for some reason.
Usually the user actually left the company and physically does not exist in
the Public NAB any longer.
This can happen if an Administrator deleted a user from the Public Address
Book and did not choose to delete the mail file. AdminP will remove the
person document but not the mail file.
"SchedMgr: Error processing appointment document (NoteID: NTxxxxxx) in
database mail\xx.nsf: Can't find appointment end time"
A reminder was created; reminders do not contain an end time.
"SchedMgr: Error processing appointment document: Can't find appointment
start time"
First, make sure that user name in the Calendar Profile matches the user's
name in the public NAB. If not, check the All Documents view in the mail
file for the Calendar and Delegation Profile documents. These two documents
should show in the view as draft documents with no subject and no author.
Once these are found and identified they can be deleted. Once these
documents are deleted, restart the server and the error should not occur
again.
Supporting Information:
Regards
Andrew Wale
Bryan Schmiedeler wrote in message ...
Bryan Schmiedeler a écrit: