Since I'n not a programmer I's like to be very carefulls with bug
reports, but after testing for a while, I belive this my be a bug or
something else:
I have 2 systems running ELOG 2.5.1:
1. uSE Linux 8.2, KDE 3.2 = NO problems at all! ELOG work's in every
function quiet well!
2. The Internet Server (of my friend): Windows 2003 Server, All MS paches
installed, Running IIS 6.0 Port 80) and ELOG 2.5.1 (Port 8080) under
FireDeamon 1.6GA (actual release) as a Service (Deamon).
Problem under Win 2k3:
This works very well, even with several users on the system and on ELOG
as long as there is not msg. threaded! Is a Msg. Treaded ELOG produces
the msg. showen in the attached Jepg-file below on Win 2k3.
The problem occurs as soon as Elog would change to the threaded display
or by clicking "Repaly" in the menu. Rights etc. are aleady checked on
the file system and are looking well. Everithing will work well as
nothing is thraded or testing locally under Linunx.
Does anybody
have an idea??? It my by a bog on Elog as well as from Microsoft or a
problem produced by a dummy user (me...!). Since Linux don't have the
problem and the same cfg-file and log-files are working well if I don't
use mode=threaded as well as Display mode = threaded I believe it my be a
realchance not to be the personal factor of the dummy user...
ThankX for every hint!
|