We have a user that is not appearing in the busytime database. We have tried rebuilding the busytime/clubusy database several times without success. We’ve also tried re-installing her Lotus notes from scratch(i.e clean uninstall and re-install). We tried moving her to a different server as well, but nothing helped. Can anyone give me some help on what to do, because I’ve been struggling with this for about 8 weeks now.
Thanks,
Siya
Subject: 2 suggestions
1: Try using the tell sched validate Full/Notes/Name/Goes/Here console command on that users Home Server. The Schedule Manager will generally tell you why someone is not "valid’ (someone whose busytime should be updated on that server).
2: Do not spend so much time trying to resolve your issues on your own before asking. Even half as much time as you spent would be more than enough to say “Ok, time to call Technical Support” or just post a preliminary query in the forums.
Bruce
IBM
Subject: I’ve tried that already.
Victor I checked the person doc(all those fields) everything looks normal, even the mailfile itself(owner,Calendar settings etc) everything is right.
Bruce, I’ve already tried that comand, I get the 'Done validating user/**** ’ response on the console, but the user is still not appearing in the clubusy. I’ve also tried the other ones like tell sched check username/, tell sched list username/*. All of them didn’t help, I get the ‘user not in schedule database’ response on the console for all of them.
Subject: Process of elimination
I hope that by now you have opened a ticket with IBM …
However, to go down a path of elimination of potentials:
cut person document from names.nsf and paste into other dB for safekeeping. Then recreate that person document with all settings manually (not cut & paste). Now re-validate the scheduler
If that does not work, temporarily create a new mail dB for the user (do not copy/replicate the existing one) and make sure it has the latest (matching server version) stock template (in case you use a specialized/modified template) point the person document to this mail db, wait and then re-validate
You can also try a combination of these two. Frankly, I don’t think the person document is the culprit but rather the mail file.
Subject: Ok next steps
are to do as was suggested and open a support ticket so we can dive deeper on this since it really sounds like a configuration issue of some kind really. I will give you the basic steps to get started which L2 would ask give you but I cannot spend a lot of time going much deeper (thats what Technical Support does, not us mere developers)
The validate console command will first verify that Sched should be watching the user at all by validating the name you give it against the data in the NAB. If the system is able to verify that the server you are on is their Home Server and several other bits (eg: no Forwarding Address, Notes as the Calendar System, etc) then it will try to scan the dB and add their data to busytime.
So it could be that the data in the NAB is telling Sched that the user is not valid (see above) or the NAB data mismatches the actual dB on the home server (eg: misspelled path, etc).
You can set DEBUG_SCHED_ALL=1 before you try the validate command. If the validation check does not like what it sees it will log something to the console for you. For example:
SchValidateUser> NO matches for user Jane Doe in N&A Book
or
SchValidateUser> User Jane Doe’s mail is being forwarded to Janet Doe/Acme
You get the idea. A warning message from SchValidateUser will give you a big clue where to go looking.
You can also set DEBUG_SCHEDULE=31 and restart the Schedule task. Once it is “Idle” you can repeat your validate command. Then watch the console for
CheckDbForCalendarEvents> Checking database mail\jdoe.nsf
and any kinds of trace or warning messages after that. What you see should give you an idea of whats wrong or where to look closer.
Bruce
IBM
Subject: Calendar relies on mail file and person document
You need to first check the person document (mail domain, mail system, user hierarchical name, mail file name, etc.) and check especially for spaces that might have been input into fields.After that you need to look into the mail file - the scheduler that adds users into the busytime.nsf goes through mail files to get information: mail file owner, calendar settings etc.
Also, if you have been working for 8 weeks on this, have you opened a ticket with IBM yet? I am pretty sure your problem would have been cleared by now if you worked with them - this is a pretty basic issue.