We are running into an issue where whenever we change the reservation time of an approved reservation, the system creates another reservation for the modified time, but it does not approve it. The new reservation just sits in a “Waiting for Approval” state. The old reservation is still there and approved.
Has anyone else experienced this and is there a fix?
Thanks in advance.
Subject: Troubleshooting tips
Not a ton of info so Ill put out some generic tips and let you start there. It would really help to know some info like:
Is the server clustered or not?
Have you made sure that RnRMgr is running on the server (Yup, some folks have turned it off and still tried to use R&R…)
Did this just suddenly start to happen?
Did you recently upgrade anything?
Are you using a custom R&R template or the stock one?
Does it happen to all rooms in the same dB or just a particular one(s)?
Assuming your RnRMgr is up, try using the validate console command on the room in question. Does it return any error or warning?
If you are clustered then try the whoowns console command to see if a clustermate has control (and then check to make sure RnRMgr is actually running on that server now…)
Bruce
IBM
Subject: We are experiencing this too
A user reported this to us yesterday and said it started happening months earlier. We guess it must have started after we upgraded the server from 7.0.2 to 8.5.2 last fall.
A week ago, in response to other problems we were experiencing with RR, we noticed that the RRDB was still using the 7.0.2 design template, so we upgraded the design to the 8.5.2 design template. Doing so resulted in the disappearance of some action buttons for -Default- users. We fixed this by enabling [Write Public Documents] in the ACL. (But all this appears to be unrelated to our user’s problem with time edits.)
Other details:
The server is not clustered.
RnRMgr is definitely running all the time.
The template was and is stock.
This appears to happen in all rooms. The user who reported it normally only works with rooms she owns. But she tested on an unowned rooms. Same result. I created test rooms, one owned by me, the other unowned. Created reservations in both. Within seconds RnRMgr approved them (green checkmarks replaced the hourglasses). Then I edited the times. A new doc was created for each room with the new time, pending approval (hourglass). The orig doc with the old time remained in place, still approved (green checkmark). I waited awhile. Tried F9 a few times to refresh the view. I tried going into the new doc in the owned room and clicking the Accept action. The doc went into and out of edit mode. But back in the view it was still pending approval. The user tells me she has tried waiting for days for the new doc to be approved, but approval never comes. She has been working around the problem by manually deleting the old res and creating a new one.
All rooms pass validation check.
I tried recreating busytime.nsf, which had no effect.
A quick look at the code suggests that, when you edit time on an existing reservation, a new doc is supposed to be created and then the original one deleted. Seems like it’s hanging partway through. Hmm.
UPDATE: This bug was fixed in either FP1 or FP2.
Subject: This is still happening…
The reminder email lists both the old appointment and the new appoinment. Am I really the only one experiencing this?