DAMO 6.5.4 'unable to update public free/busy data'

hcl-bot · April 15, 2005, 6:10am

Hi

Again, DAMO 6.5.4, Domino 6.5.3, Outlook 2003SP1.

When I send meeting requests, and acknowldge them, the diary changes aren’t beeing reflected in the public free/busy daata viewable when trying to scheudle meetings – also when i quit out of outlook (or possibly just when it tried to replicate), i get the outlook error: ‘unable to update public free/busy data. operation failed’. Any clues?

thanks

hcl-bot · April 15, 2005, 11:46am

Subject: Clustered? Stand alone? Corrupt?

Does BusyTime.nsf/CluBusy.nsf exist? Backing up or Transaction Logging these files can be a constant source of corruption making these file inaccessible. Below is an excerpt from TechNote #1086471.

How To Re-create Busytime.nsf File (applies to Domino 4.5x/4.6x, 5.x and 6.x Servers):

The Busytime.nsf file is the Free Time database on a non-clustered server. To rename the Busytime.nsf file do the following:

If possible, map a drive or FTP to the Domino Server’s \Data directory.
From the Domino R5 Administrator open the live console.
Issue the following commands:

tell sched q

tell calconn q

dbcache flush

Note: Several dbcache flush commands may be required, depending on the OS and the server’s load.

On the Domino Server’s \Data directory locate Busytime.nsf and rename it to something else, such as Busytime.old. Then move it out of any data or any reference to a database or directory link. DO NOT leave the renamed copy in the Domino server’s data directory hierarchy.
Issue the following commands:

load sched

load calconn

How To Re-create Clubusy.nsf File (applies to Domino 5.x and 6.x Servers only):

The Clubusy.nsf file is the Free Time database on a clustered server. To re-create (or restore) the Clubusy database, do the following:

Note: This process must be done to all servers in the cluster to avoid the replication of Clubusy.

If possible, map a drive or FTP to the Domino Server’s \Data directory.
From the Domino Administrator client open the live console.
Shut down the Sched and Calconn tasks on all clusters and flush the database cache.

tell sched q

tell calconn q

dbcache flush

Note: Several dbcache flush commands may be required, depending on the OS and the server’s load.

On the Domino Server’s \Data directory find the Clubusy.nsf and rename it to something else, such as Clubusy.old. Then move it out of any data or any reference to a database or directory link.

Important Note: DO NOT leave the renamed copy in the Domino server’s data directory hierarchy, or you may experience unexpected behavior. In addition, Steps 3 and 4 MUST be done on ALL clustermates BEFORE Step 5 is performed on ANY server. Otherwise, you may have old data added back into the busytime database invalidating what you are trying to do. If you do not do this correctly, you will have to restart the process all over again.

Start Sched and Calconn on all cluster mates.