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.

More Domino 7.0.3 upgrade fun

I'm not sure if it's a coincidence or not but I had another issue pop up today. This time, I had a user that was not able to get any messages delivered to their inbox. The error message that kept appearing on the server console was:
11/12/2007 05:27:27 PM Invalid Time or Date Encountered
and then the next line had the information for the user that the mail message was going to. So, it was off to search support for an answer and I found one, but it was missing the one step that really got it working. The tech note suggests that on top of doing a fixup, to also replicate the mail database. Since the mail file is in a cluster, the replication didn't fix it right off the bat. I cleared the replication history on both cluster copies, replicated the database doing a push/pull, then ran the fixup and the mail started flowing.
Could have just been a corrupt database to begin with, but I thought it was worth noting.

(Finally, back to some serious Domino blogging around here ;-) )

Domino 7.0.3 upgrade and LDAP

If you're like me and are using LDAP for address verification, or for any other nefarious reasons for using LDAP, then you'll want to read this technote from IBM:
Doc #:1256436 Domino LDAP server returns 'Invalid DN Syntax' message for previously working searches
Seems that in Domino 7.0.2 FP1 there were some changes to how Domino uses LDAP. Of course, I found out about this the hard way and mail flow into my one anti-spam server stopped because it couldn't verify the email address off of the updated 7.0.3 server.
Oh the fun we administrators have!