Hi All,
I have couple of problems in my resource reservations database.
When people create reservations for some resources, it generates reminders even after the meeting time/day is over.
On & off it creates Replication or Save Conflicts for some Resources. But it does not have any replicas anywhere.
Thanks & Best Regards,
Buwaneka
Subject: Thoughts
A couple thoughts related to your posting.
1: Reminders get sent by an Agent that runs nightly. The docs in the R&R dB that meet the criteria are ones that trigger a Reminder to be sent. It is likely that the entries are older (preexisting) entries that have instance dates yet to come.
Pre-R7 repeating entries use the R5 repeating format where 1 doc can represent multiple dates. That means that a repeating entry must stay in the dB until its last repeating date occurs (which can lead to view clutter, etc). R7+ repeating entries use the R4 repeating format where 1 doc represents 1 repeat instance. That means that single instance changes (eg: Transfer Reservation) can easily be done. It also means that there is less clutter in the views once each instance is past.
2: The only time I have been able to verify rep conflicts was when a Room Owner would repeatedly click on “Accept” of WFA requests. This means they are trying to update it while RnRMgr is trying to process it and one will have to become a rep conflict.
You can check this out by checking matching the info in the $CSTrack item with the doc modification times from the InfoBox. Be sure you factor in cluster replciation as well if the info shows RnRMgr and the user in question doing actions on different servers.
Bruce
IBM