We have a domino server that was recently upgraded from Notes 6.5 to Notes 8.02. There is a reservation database which has a problem. We upgraded the template to 8 and ran the “Ugrade” action. Most of the rooms work fine. We have one room (which has “None” in “Owner Restrictions” and is available “24 hours every day) which causes problems for some (most people).
If you try to book from the calendar you get an email message that says “Insufficient access: xxxxx” where xxxxx is the reservation description. If you open the email, the document says “Meeting Resource Not Reserved yyyyy is unavailable” where yyyyy is the resource name. The above problem can occur even if the person has manager access. The reservation is booked on the calendar, but does not show up within the reservation database.
If you try to book from within the reservation database, the reservation very briefly shows up in the view and has an hourglass by the reservation. The reservation then disappears. No error is received.
If I look in the log.nsf file, I see no errors at the time the reservation is made. There is an error that periodically shows up, “07/07/2009 04:29:59 PM RnRMgr: Error processing calendar profile document (NoteID: NT00004CCE) in database Resource.nsf: Can’t find $BusyName field on profile”
Making a reservation works fine for other rooms on the reservation database. Some people can book a reservation to the “problem” room. One of the “successful” people only has author access.
This is an old database that was created back in 2001.
The client that is being used is Notes 6.5.4 and 6.5.6.
Recreated clubusy.nsf and that did not help.
Does anyone have any ideas? Your help would be appreciated
Subject: One more option
When I rescanned your posting I noticed you said some folks could book it and others could not. That could be due to some stale access info being stored on the room doc itself. Did the room have owner restrictions before?
DB level access is separate from room access so roles, etc are not in play here. It could be old owner data hanging around messing with you. Do a “tell rnrmgr list FULLROOMNAME” console command and see what it says. The info in the response will help:
RnRMgr: Profile for FULLROOMNAME (Busytime restricted: Yes, Details restricted: Yes, Opt out details: No, Profile last updated: Unavailable)
If it says “Busytime restricted: Yes” then that would be why some of your users get rejected
Bruce
IBM
Subject: Ideas
First off the easy stuff. “Upgrade” is left over from the R4->R5 days when it was needed. Any R&R dB created using R5 or later does not need to run that. At some point Im sure Ill be able to convince the Template team we can safely remove it…
The "Can’t find $BusyName field on profile” console message is because the R&R template will create an extra profile doc that has no name on it when the first room is created. This is not a fatal thing, merely a warning. Anyone who has some Agent coding skills can make an Agent to run and remove the bogus profile doc from the dB. Just fine the one without a $BusyName item and delete it. Or just ignore it for now and some day the RnRMgr may do it for you (but no idea when…)
Now for the real issue: the reservations are being declined for a seemingly valid room. Normally I would have you enable some INI to get some info but I do not think we have many that you can use in production builds. So the next best I can suggest is to either open a support call so we can dive deeper with your OR since you found that it works ok in a replica copy you could make a copy and then replace the ‘bad’ replica with that one (although I am curious how that would fix anything).
Have you tried running fixup on the dB??
Bruce
IBM
Subject: Additional Info
If I copy the database to a test server in another domain, the problem disappears.