Invalid Time or Date Encountered - The Sequel!

Back in November shortly after I upgraded to Domino 7.0.3, I ran across the problem that others were also experiencing with the upgrade. Mail would queue up for individuals and not deliver to their mail files. The message on the server console would always be:
11/12/2007 05:27:27 PM Invalid Time or Date Encountered
I had blogged about what I did to fix it, but this time those fixes didn't fix it. Had to take further steps to get things working. Support says that running fixup on the database will resolve the issue. Not always so. If you are running on a clustered environment with transaction logging and the users have a laptop with a local replica of their mail, you then have several other layers of "stuff" working against you. While you can get a hotfix from support, I am doing the following to fix this error. Since it's happened to two users within the past 24 hours.
1. Delete all other replicas of the mail file. Both on the laptop and the cluster server.
2. Run fixup without the -J switch even though it's using transaction logging. I tried several time with the -J and it did not fix it until I ran fixup without the switch.
3. Once mail is flowing to the mail file, then recreate the replicas.

I was on with support yesterday about this issue and it will be fixed with FP1, 7.0.4 or with the for mentioned hotfix . For now, it's just a pain in the butt.

I'm sooo ready to head to Orlando

Okay, so I thought that today was going to be a nice smooth one. Leaving for Lotusphere on Saturday, so I'm taking tomorrow off to run errands and spend time with my beautiful bride. I was wrong. About the easy day that is.

I was in a training class all morning, that went fine, but it was after lunch is when things started to go downhill. The Help Desk reported that someone couldn't reserve a room in the resource database. As soon as I opened the server console, I saw errors like this:
01/18/2007 01:37:56 PM SchedMgr: Error adding busytime entry to schedule database for user xxx/xxx/xxx: Database is corrupt -- Cannot allocate space

Okay, I start seeing A LOT of "Database is corrupt" errors. I'm thinking every mail database on the server has gone south. So I shut down the Domino server, set the service to manual so it won't start up after reboot and wait. While rebooting, I recall seeing something about clubusy.nsf being corrupt. Put 2 and 2 together and start with that database first. Ran a compact -C, did an updall -R on the clusbusy.nsf and restarted Domino. All of my problems have gone away. Never seen that one before. I probably should have rebuilt the clubusy, but I'll watch it from the hotel.
So after that mess, I head home to play with my NEW Canon Rebel XT. 8 mega pixels of fun! I decided to get the body only since I had a "regular"Rebel and was going to use that lens. All excited, I get home, toss the battery and memory card in and start snapping! First round of pictures look good, but then I start getting an "Err 99" on the back of the camera. After doing some Google-ing, I come to find out that older Sigma lens don't work with the new Canon digital SLR's. Grumble grumble grumble. So, back in the box it goes and I've already requested a return from where I bought it from. Guess I'm going to get the credit, then turn around and buy the one that comes with the Canon lens. Sure, it's $80 more but with what I was able to play with the camera, it's worth it.
With all of todays fun behind me, I have a new episode of Smallville to watch, (the one with Flash, Green Arrow, Cyborg and Aquaman, I'm such a geek), and then packing for Lotusphere. Okay, I'll do the packing tomorrow. Tonight, I'm taking it easy.