Symetrik Domino Consulting

Posts Tagged ‘upgrade’

A few days ago, EOS (End of Service) was released for Lotus Notes/Domino 7.0x

I think the real issue is that Lotus Notes 6.5 expires in only 8 months.

the 7.0x EOS breaks the crutch of the upgrading from 6.5.x to 7.0.4

If an organization knows that they HAVE to upgrade, then they won’t simply upgrade servers to 7.0.4 and live with any clients issues to minimize any problems or logistical issues and cost of upgrading to 8.5.

Now there is a more solid business reason for upgrading to 8.5 and getting away from the old code and old client once and for good.

Have you ever seen this message when opening a mail database? From time to time we see this after an upgrade. Normal Fixup, Compact, Updall, and even template replace will not fix the issue.

However, Compact -D will do the trick.
The -D switch discards any built view indexes

You can try this for B-tree structure is invalid! errors as well.

For good measure you can run Updall -R afterwards to rebuild all the view indexes.

I’ve just upgraded some of our Domino severs from 6.5.6 FP3 HF63 to 7.0.3 FP1 HF517. I put alot of testing into it so it has been relatively smooth.

I did find that I had some template replication issues, so I went around, deleted every template in our environment except on one isolated 7.0.3 server. I then signed all the templates on that server and used the admin client to create replicas on our hub servers which had also been upgraded to 7.

I had real problems with the following templates: activity.ntf, admin4.ntf, certlog.ntf, dba4.ntf, and webadmin.ntf.

admin4.ntf, certlog.ntf, and dba4.ntf had a bad ACL set, so I couldn’t sign any of them, and the LocalDomainServers group couldn’t replicate. I fixed that and signed the templates and replicated them.

One of them was set to temporarily disable replication, and I fixed that.

All that was left was activity.ntf and webamin.ntf. For some reason, activity.ntf wouldn’t initialize. I had to try several times before I got it working through adminp.

I could never get webadmin.ntf to replicate because the error message that shows up when the temporarily disable replication tickbox is checked kept appearing, but the template did not in fact have that checked.

I starting looking through DDM today, and found that one template and one database generate errors when design runs.

Design error for database ‘help\readme.nsf’: Invalid collection data was detected.
Design error for database ‘dominoblog.ntf’: Invalid collection data was detected.

I looked in R7 admin help, Notes 6 and 7 discussion forums, and google, and “Invalid collection data was detected” appears nowhere.

These are all small things, but wouldn’t expect finicky templates from 7.0.3.

This weekend, I’ve upgraded 30+ servers in 10 countries. It’s been an all weekend affair, and I spent a pretty good time organizing myself last week.

First, most of our servers were 6.5.6FP2, and we wanted to apply FP3, the DWA for Windows Vista java hotfix, and 6.5.6 FP3 HF29 which fixes the Out of Office agent (OOO is enabled even after user disables it).
We had 4 servers that were 6.5.4, 6.5.5, and 6.5.4FP2. These servers were the only servers that really gave me any problem.
I also wanted to upgrade TrendMicro OfficeScan from 2.6 to 3.0 (only about 4 servers needed this).

I only ran into a couple of gotchas. Here’s how I did it. Read the rest of this entry »