Upgraded our Server to R6 this weekend, now I’ve got an entire network full of disgruntled archive users. They can access their archives (thank God) but cannot add documents to it. They receive the error ‘Notes error: Archive Database format is invalid.’ I’m looking for an ‘easy’ fix that doesn’t require me to hit every single workstation and doesn’t require any work in Designer. Can anyone help???
Subject: 400+ broken Local Archives…HELP
From the 6.0.1 fixlist:
SPR# ACRS5EQH3Q
- Fixed “Archive Database format is invalid” error when archiving to an archive database created with Notes 5.x
Take cover from your users and pray that MR comes out soon. 
–
Martin
Subject: RE: 400+ broken Local Archives…HELP
Oh man you have got to be kidding!!!
I will be crucified long before then!
Subject: RE: 400+ broken Local Archives…HELP
Hmm… well, if your clients are all running R6 your could probably try upgrading the archive databases to the new design. Don’t know if this helps though (and worse: it may require work in designer or the good old “administration by gym shoe”).
If that’s not an option then maybe you should start looking for a good hiding spot. I can recommend a skiing holiday in the Austrian alps.
–
Martin
Subject: RE: 400+ broken Local Archives…HELP
It’s out today, go download it.
Subject: Repeat after me.
“I will test before I deploy. I will test before I deploy.”
Subject: RE: Repeat after me.
Try this one:
“After a year of beta you’d think they’d have it ******* fixed.”
Subject: RE: Repeat after me.
…not to mention the fact that this isn’t the ONLY problem we’re having. It’s pretty freakin hard to ‘test’ every scenerio you might encounter in Notes. I am thankful enough that mail even flows.
Subject: RE: Repeat after me.
"After a year of beta you’d think they’d have it ******* fixed."followed by
" It’s pretty freakin hard to ‘test’ every scenerio you might encounter in Notes. I am thankful enough that mail even flows."
Obviously from these statements you expect the developers to think up and test every scenario, yet you think its really hard and should not have to.
Subject: Ignorance is, well, just plain ignorant
What an ignorant thing to say. Expecting the Notes admin population to do the testing of a developer group is just as inane as expecting a Notes user population to do the testing of the admin group. It’s a one-to-many relationship where the tests of the one apply to the many. It’s a case of “It’s not my frickin’ JOB man”. The developer is supposed to make sure the program operates as defined, and the admin is supposed to make sure the program operates as expected. The admin has EVERY RIGHT to be annoyed at obvious bugs.