Dear AllI’having a big problem with a new installation of Domino 6.5.1 on Win2003 with transaction logs enabled.
About one time a week the server goes into troubles in opening the address book.
One of the first messages is:
Unable to retrieve activity trends configuration.: Attempt to reopen an open container
After that every access to the address book (also from clients) gives the same error code
I run Fixup and compact on the database without any result
The only solution found since now is to restart the server (stopping about 3 hundred users), I think the operation does some fixup on the database because after that it works
I wasn’t able to find an answer in IBM support
Have someone already encountered this problem ?
Has someone an idea about how this problem could arise ?
Actually, we are not using Directory Assistance on this (or any other) server, so the problem is still there.
I believe the problem occurs somewhere during night-time. The next morning, I notice that some databases can no longer be opened. Only a server-restart then fixes the problem. From LOG.NSF I can not determine what the exact cause for this errormessage is. I still believe that some external task is running on the server : A backup-procedure (although they have been temporarily disabled now), or a compact-task, or a fixup-task, or maybe even an agent doing strange things…
Subject: Attempt to reopen an open container - Another fix
I have a similar problem with on of my users mail files. the problem is most likely caused by backup software of AV software.
The fix I have found is to go in to Administrator and choose the Manage Views section for the corrupted database, then keep purging indexes until the database can be opened safely.
This saves having to reboot the server during business hours and the loss of potential business.
Subject: RE: Attempt to reopen an open container - Another fix
If the problem is the virus, you must tell the virus don’t scan the notes database and buy an virus for Lotus NOtes. I think the problem is the virus review the database at the same time the people works and it’s a problem…I hope this solutions works well…
At our place, we have exactly the same problem : Running on 6.5.1 servers, we regurarly get message “Attempt to reopen an open container” in our log.nsf. No idea where it comes from…
When this happens we are unable to open certain databases : fixup, compact, refrsh/replace design,… does not fix the problem. Only a restart of the server helps. Where can I get more informatoin on this problem?
Subject: Update: Attempt to reopen an open container
Dear allI’m still trying to identify the problem
Since I’m not the only one with this kind of problem.I wish to set up a common platform for discussion so please can you confirm the following points or suggest others ?
The problem is related to LD6.5.1 on WIN2003
I’m suggesting this because I run for about 3 months LD6.5.1 on WIN2000 with quite the same configuration and I never had any problem
I’m currently using Transaction Logs on a separate array
(I don’t know if this could be the problem but in my previous configuration I was using transaction logs on the same array )
The problem is arising mainly at night time but I got it also during working hours
The problem is arising every two/three days
The server in my location is very busy exchanging e-mail and serving about 300 users
The server is busy but not out of resources (dual processor 2 Gb RAM , fast SCSI array)
I had also sometimes some suspicious problem (some database became corrupt) without any apparent cause.
Subject: RE: Update: Attempt to reopen an open container
All,We are currently running domino 6.5.2 with clients 6.5.1(mainly), 6(admin) and also 6.5.2(in testing). We have been speaking to the IBM support people(for one month) and they have no idea on how to fix the problem. We are currently trying to source someone to come on site and look at the problem however they are wanting a commission to do so.
There are only two ways we have been able to work around the problem.
As a further note: we have found the problem mainly occurs b/w 12:00 and 14:00 on a daily basis. I am not sure if there is a background task causing the problems or a lunchtime thing!!
Issue a RES SER command on the affected domino server. (Not the best solution during production hours)
OR
From the domino admin, go to the database users screen and boot everyone logged into the database out of the session. Once the everyone exits the system, notes appears to free up the error and the database can be used again. This has worked for us 99.99% of the time.
If the database is constantly open by domino then option 1 appears to be the only workaround.
Also we have scheduled a restart on the domino server every night and that appears to be reducing the problem from a daily occurance to a weekly occurance.
IBM have advised several possibilities to resolve the issue:
Issue the fixup and compact and design updates.
Recreate the affected databases using a fresh V6 template.
Neither of the above fixes work…
Has anyone tried a later version of the notes client/domino? I believe V6.5.4 is currently in beta testing and I cannot at this stage get my hands on it.
IBM have done some extensive testing at our site and found it to be the anti virus software. When we temporarily disable this the open container issue disappeared.
The AV software we are using is CA’s eTrust. We currently have a call logged with them and would appreciate it if you are using the same software if you could log a call with them.
Also if you are using different AV software try it out as well and let me konw how it goes.
I’m having a similar problemo with my recently installed 6.5 server running eTrust 7.1.
CA have advised us to exclude the domino directory and domino processes such as nlnotes.exe from the Realtime Monitor Options - (this is the normal eTrust scanner, not the mail scanner)
I’ve put this in place today - will have to see it works ok from now on - I’ll let you all know.