hello stefan
sorry for the delay, was out of the office today. i had tested the same config
and logbook under a "pseudo" win nt installation (suse linux 8.2 with vmware
4.01 (virtaual pc simualtion) and a nativ win nt 4.0 sp6a: there is no
problem! as well as this configuration works under linux as daemon.
the problem only ocures on win 2003 server. I d'dn't test it under xp, 2000,
2002 beause i don't have any of this systems. but it looks that no one else
has this problem. would be helpfull to know if there anybody out in
cyberspase using elog 2.5.1 with win 2000 or 2002 or even better with win
2003 server? or do you have a 2003 server at psi?
for me it looks like a incompatibility of a stack, boffer overrun or somethin
in the memory. for me it really only occurs under win 2003. thats what i'm
wondering. the system memory test of the server was ok (no virus, non
controller problem or something, else, checked the hole stuff agian, just to
be really shure!) , other apps don't have any problmes (it isonly iis 6 and
mercure mail server runnig on this system with about 20gb free disk and about
500mb ram totally and a pentium 4).
if you think you have a chance to reproduce the problem i can zip the config
file and the log for you. but in my opinion, you will need a win 2k3.
i'd chdcked the file system rights again to be shure that they are ok. also
i'd checked that elog run as a system service under win 2k3. it should have
all rights. changing to run eleog with administrator rights didn't change
anything.
would be great to find out what's happen. in the mean time i let it untreaded,
hoping no one will click treaded view... ;-) for security, the servie is
configured to restart if it hangs and to boot the system in an emergency, but
it shouldn't happen evry hour...
thakX!
ueli
> All I can offer is send me your config file for the problematic logbook, and
> I will try to reproduce the error.
|