Subject: RE: Attempt to reopen an open container
Hello
Iam very curious, how has it went so far?
/Christer
Subject: RE: Attempt to reopen an open container
We can now publish our findings, CA found the problem to be the inrouter not releasing the database. They have released a QO to resolve the issue.
The HF number we have is TF68178. I dont have the actual QO for it. The patch has been running successfully with no open containers at all now for two months. It has taken nearly two years to resolve, but at lease it is one.
If you email me, I can email the patches back.
Subject: RE: Attempt to reopen an open container
We’re using Domino 7.0 with eTrust 7.1 and having EXACTLY the same problem. I’m very interested in obtaining this patch. What’s your email address?
Subject: FIXED: Attempt to reopen an open container
gmoolenaar@repco.com.au
refer previous entry
Subject: RE: FIXED: Attempt to reopen an open container
Please dont email me any more. I have done the smartest possible thing to get around this problem. I left the company and went to one which uses exchange.
Subject: Attempt to reopen an open container
Well guys,The only way, other than restarting ther server, we fixed the problem by installing Patch for CA antivirus.
Thanks