Domino @ Symetrik Design

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.

Have you ever seen this error message in your console or statrep.nsf?

I see hundreds in my statrep.nsf all the time.

The cause is that the user with mailbox called filename.nsf has mail rules set to file messages to a folder that doesn’t exist anymore.

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.

I’ve gone around turning on Message Tracking and enabling weekly and monthly reports for all of my servers. We’re running out of disk space fast and we’re trying a multiple prong approach on tackling the problem.

We’re looking specifically at exactly who is sending large attachments.

After the happy Halloween and end of the month, I went around this morning to build a spreadsheet from the data in the reports.nsf on all the servers for the Top 25 Monthly Senders By Size. On a couple of servers, the report only contained “Internal error, unable to open Reports database” Read the rest of this entry »

Today, I wanted to add a new field to our person document form in our directory for our internal VOIP telephone extensions. There are alot of people out there now using VOIP, but the problem is that our users don’t know what the extensions are for people in other sites/locations. If they would use the VOIP extension instead of dialing the long distance number, we could save alot of money.

I created a field called OnNet, refreshed the design of the NAB, populated the field with some actual data, and then went to test it out. Works great.

However, our corporate accessible directory is a web application on a Linux box that performs LDAP queries to Domino.

If I authenticated to LDAP, I could see all of the person document fields with a LDAP browser including OnNet and the data, but if I don’t authenticate, I can only see the domino fields (or LDAP attributes) that are specified in the * server configuration document. Read the rest of this entry »

Today is Tuesday, but it seems like Monday. Mostly, because I took a day off yesterday, but also because I’ve had problem after problem that seemed to have no simple solution:

First, there was a server that was upgraded over the weekend. For some strange reason, it had been generating false alarm HTTP probes.

The probe has timed out for the following statistic: QOS.HTTP.Pass2/Domain.PASS-5Q852E.ResponseTime

Second, a user was complaining that they received a “Mail Encryption Failure” popup box and with the error message “If you choose to continue sending, the following recipients(s) will receive an unencrypted copy of the message.” when trying to send encrypted messages.

Third, a regional admin was complaining that he didn’t have access to any of the mailboxes in a folder on a remote server. Read the rest of this entry »

I have just enabled Message Tracking on an R6.5.6 server.

All I had to do was to enable message tracking in the server’s configuration document.
I added LocalDomainServers to “Allowed to track messages” field, but left everything else as is.

Once that was enabled, I issued “load MTC” on the server in question.

I initially got these errors when the task loaded:

MT Collector: Initialization failed: File does not exist
MT Collector: Unable to use directory e:\Lotus\Domino\Data\mtdata: File does not exist

Read the rest of this entry »

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 »

When working on some new partitioned servers today, I saw this on the console of all three servers.

06/18/2008 04:41:03 PM Router: Connection from server NOTESVN1/DOMAIN not used; Server not found in Domino Directory.
06/18/2008 04:41:03 PM Router: Connection from server NOTESVN1/DOMAIN not used; Server not found in Domino Directory.
06/18/2008 04:41:03 PM Router: Connection from server NOTESVN1/DOMAIN not used; Server not found in Domino Directory.
06/18/2008 04:41:03 PM Router: Connection from server NOTESVN1/DOMAIN not used; Server not found in Domino Directory.
06/18/2008 04:41:03 PM Router: Connection from server NOTESVN1/DOMAIN not used; Server not found in Domino Directory.

I couldn’t quite figure it out because the 3 partitioned servers I was building/working on had nothing to do with this new cluster that another team member had just built for our Vietnam office. Read the rest of this entry »

We were getting a few strange sounding reports from a user who was trying to send email to 3 groups.

The first message was:
“A copy of this message was sent to 180 recipient(s), but the Internet format of this message was not sent to the following 34 recipient(s); <address@domain.com>, <address@domain.com> etc.”

The second message was:
“Document has invalid structure: mail.box”

We closed the client, deleted mail.box, opened the client, and let it re-create mail.box and all was fine.