Constant Crashing

Background:

Intel 1GHz CPU, 384 Mb SDRAM

Windows 2000 Server (fully updated/patched)

Lotus Domino 6.5.4

Lotus Team Workplace (QuickPlace) 6.5.1

Lotus QuickPlace Patch for 6.5.4/6.5.1

This is a totally fresh install of all software on a newly formatted hard drive.

Issue:

An MS Visual C++ Runtime Error is causing nHTTP.exe to crash a few hours after booting.

Temporary Solution:

Scheduled reboot every three hours during workday and every six hours during off-time.

Help?

I cannot understand why this is happening. This is the second machine to have this problem. s there something wrong in QuickPlace? There are no technotes nor any forum posts on point.

This is really crippling me-- please advise if you can. Thank you.

Subject: Constant Crashing

Have you looked at the NSD and the log file; they will tell you why the server crashes.

//Kjeld

Subject: RE: Constant Crashing

Yes, nothing in them to explain the cause. No instance of “FATAL” in the NSD/logs-- nothing on the console logs either. Its not the whole server that crashes, just the HTTP server portion-- Domino thinks HTTP is still running (shows up in running processes), though it doesn’t respond to anything and it will not gracefully shut down during an attempted server restart.

Any more ideas?

Subject: Constant Crashing - get rid of 6.5.4

Since upgrading from 6.5.3 to 6.5.4, I have had nothing but an endless stream of crashes, “red deaths” etc. My first suggestion to you is get away from 6.5.4 and go back to 6.5.3. I never saw a single problem with it. I’ll see you there!

Subject: RE: Constant Crashing - get rid of 6.5.4

I was advised by an IBM guru to do a new install of 6.5.4 rather than an upgrade, and so far that has worked much better, although there’s a bug in it that I found when trying to compress my old desktop - “red death”.

Apart from that, this looks the way to go …

uninstall 6.5.4 (backup,backup, backup!!!)

rename the old directory (to make sure the uninstall was complete)

install 6.5.4

if, like me, you want “belts and braces” security, then install into a different directory.

Subject: RE: Constant Crashing - get rid of 6.5.4

I’ve never wanted/needed to go backwards on upgrades before, how do I do that? Of course, my other challenge is that my install media was/is 6.5.4.

Subject: I don’t believe downgrading is the proper answer, finding out what is wrong is.

Did you read the release Notes for 6.5.4 before installing? For example, you mention using QuickPlace. Have you installed the required fixpack? (which is covered in “Things you need to know” section)

http://www-12.lotus.com/ldd/doc/domino_notes/6.5.4/readme654.nsf

http://www-1.ibm.com/support/docview.wss?rs=855&uid=swg24009334

Team Workplace 6.5.1 Fix Pack for Domino 6.5.4

Abstract: Fix packs to allow Team Workplace 6.5.1 to run on Domino 6.5.4 under Windows, Solaris, or AIX.

The fix packs linked below are necessary to allow Team Workplace 6.5.1 to run under Domino 6.5.4 on Windows, Solaris, or AIX.

Subject: RE: I don’t believe downgrading is the proper answer, finding out what is wrong is.

Yes, as I indicated in my original post, I did install the fixpack. A previous “doh!” expereince taught me to always read release notes, etc. :slight_smile:

I agree that downgrading is never a preferred option.

The thing that’s driving me nuts is that the only indication of the problem is a Windows eror box (the runtime error box)-- nothing in Domino itself.

Subject: RE: I don’t believe downgrading is the proper answer, finding out what is wrong is.

“Visual C++ Runtime Error” usually means an unsatisfied class dependancy – a missing DLL in System32, for instance.

Subject: Which way to tell which DLL is missing?

Is there a way to tell which DDL is missing?

Subject: RE: Which way to tell which DLL is missing?

I’m sure there must be an easy way, but I’ve just done a directory print on the broken machine and a working one and compared manually (it was a one-time deal, and buying or writing a tool would have taken longer).

Subject: Sorry, I missed that you had already installed the Fixpack.