We have a situation where calls to NotesSQL are causing Domino to “crash” on all of the Domino servers in our environment. Has anyone else been experiencing anything like this.
The issue began occuring a couple of months ago and is reproducable on any Domino server running NotesSQL.
In the typical case, a Crystal Report is executed via a URL call. The resulting ODBC query to NotesSQL causes an attempt to read data from a Domino database.
This causes the Domino service to immediately and completely crash to the “Desktop” (i.e., the Domino Server console no longer exists).
General notes regarding what we are seeing:
-
Of special note, when Domino “crashes” the Windows Event Log shows that “The Lotus Domino Server (LotusDominodata) service entered the stopped state”. The Domino service can be immediately restarted and does not behave as if it has “crashed”. The Domino service is defined to restart on failure, but it is not restarting. The only “issue” Domino seems to have is that, as if you killed the server without stopping it first, some databases will go through a consistancy check.
-
The Notes log files do not show any fatal threads, etc., as if you had actually just stopped the server.
-
Every Domino server can be repeatably “crashed”, but not necessarily with the same report/query on each machine or database. On some machines/databases a report that accesses “View A” will always “crash” Domino. On other databases “View A” might be accessible but a query to “View B” will always cause a “crash”.
-
Other than “regular” Microsoft updates, none of the servers were upgraded, neither Domino, NotesSQL, nor the OS prior to this issue arising. Obviously something in the environment changed, but what could change across the entire environment that could cause such crashes?
-
We scanned all the machines for viruses, ran fixup on the databases, made new copies and replicas of the databases to no avail.
Our current environment
We are running Windows Server 2003 (32 bit). Only “regular” Microsoft updates have been applied in recent past.
We are running Crystal 8.5, but the issue can be reproduced by making an OBDC call to NotesSQL from Excel or through our EasySoft JDBC-ODBC bridge.
We are running Domino 8.5.1 (no fix packs). Upgrading to 8.5.2 has not solved the problem.
We are running NotesSQL 3.02g. Upgrading to 8.5.1 did not solve the problem.
We are running the latest version of Vipre Enterprise anti-virus, but actually uninstalling Vipre on one of the servers did not resolve the problem.
If anyone has seen anything like this please let us know.