> I agree. It's most probably a stack overflow problem. The stack size must be 
less  
> on a win 2003 server compared to a xp machine. I know that the threaded display  
> requires some more stack space than the other displays. But unfortunately I have  
> no win 2003 server here to try. 
 
since the new server isn't standing here in my office i can not test if older elog 
versions don't have the problem too. but if your idea of stack or buffer overflow 
is right, i guess that hoping of the helpfull ms pach or a update of the compiler 
will be the only what we could do  :-(  it's always the same using software fom a 
company named "kleinstweich"...  ;-( 
 
is there a posibility in elog to switch off the threaded view or to say what kind 
of views are allowed? this would be helpfull in this case as well as it may be  a 
nice feature for other users too. elog is very powerfull, fo some users i think 
too powerfull with to many possibilities. i think about something like you made in 
the menu / guest menu option or maybe a flag to say "don't" make threaded dispaly 
possible", like e-mail formating or something else? 
 
 

> since the new server isn't standing here in my office i can not test if older elog 
> versions don't have the problem too. but if your idea of stack or buffer overflow 
> is right, i guess that hoping of the helpfull ms pach or a update of the compiler 
> will be the only what we could do  :-(  it's always the same using software fom a 
> company named "kleinstweich"...  ;-( 

;-))) like that one...

I tried to reduce the memory consumption in the threaded display, can you please try 
the modified version under

http://midas.psi.ch/elog/download/windows/elogd.exe

> > since the new server isn't standing here in my office i can not test if older elog  
> > versions don't have the problem too. but if your idea of stack or buffer overflow  
> > is right, i guess that hoping of the helpfull ms pach or a update of the compiler  
> > will be the only what we could do  :-(  it's always the same using software fom a  
> > company named "kleinstweich"...  ;-(  
>  
> ;-))) like that one... 
>  
> I tried to reduce the memory consumption in the threaded display, can you please try  
> the modified version under 
>  
> http://midas.psi.ch/elog/download/windows/elogd.exe 
 
just was back from work today! i have installed the new elogd.exe file (after a 
backup!  :-)  ) and restarted the service. there are basicalle two news, a really good 
one an a bad one: 
 
1. the bad: clicking for a threaded display of the logs will still produce an porobem 
as shown in the screendump of the win 2k3 remote controle console (jpeg-attachement). 
 
2. the really good one: the BIG difference to the original 2.5.1 elogd.exe are two 
points: 
2a) the elgog.exe no more hangs! after a while it comes back to the view before 
clicking threaded view. while trying to dispaly the thread it seems to hang, but just 
semms! (white browser, nothing to see) 
2b) after quitting the error it's bossible to use eleg as normal. no restart of the 
service is more needed. before, a restart of the service has to be done because elogd 
was hanging compleatly. 
 
as you tought, it looks like a stack problem ore someting else. sorry, didn't had 
time enough to find out detailed information of 2k3. also develeoper network from ms 
dosn't bring detailed information about memory handling to the public guys  like me. 
 
the other solution my be, as i wrote, to have a switch for switching of threaded 
display, even a treaded view may be very helpfull in an discussion forum. maybe the 
compiler may coming up with a new version or ms will make a pach, for someting 
absolutly different of course  ;-)  , solving this probleme... 
 
ueli 
 
 

Run into the same error on a windows XP & 2000 machine. Totally shuts down the elogd.exe 
when THREADED is selected. Have not tried your modified version after reading the posted 
results. Will run with summary view until fixed. Wish I could help but I'm not a 
programmer. Let me know if you want to test any new elogd.exe's.

> Run into the same error on a windows XP & 2000 machine. Totally shuts down the elogd.exe 
> when THREADED is selected. Have not tried your modified version after reading the posted 
> results. Will run with summary view until fixed. Wish I could help but I'm not a 
> programmer. Let me know if you want to test any new elogd.exe's.

This problem has been fixed now, it was a programming bug. New version under

http://midas.psi.ch/elog/download/windows/elogd.exe

Many Thank's to Stefan for his work!!! He's doing a great job and is offering a better 
service than most comercial programs! Thank you very much Stefan!!! 
 
The new elogd.exe is now runniung 24h on my Windows 2003 Server without any problems. I made 
a little "stress" test too and there wasn't any problems at all. Also threaded view is 
working stable now. 
 
Is seems, that the new eleogd.exe uses a litle bit less of system rescources especially in 
theraded view mode. 
 
System specification for test: Pentium 4 2,4GHz, ASUS Motherboard, 480 MB RAM, SWAP File 1,1 
GB, Windows Server 2003 Enterprise Edition 5.2 including all paches until 15.3.04, IIS 6.0, 
Mercure Mail Server 4, McAffee Virus Scan & Firewall, ELOG 2.5.1 with new eleogd.exe runnig 
as service (system righs) with FireDaemon Lite 1.6GE. 
 
Please note that this problem has been occured under windows (reported for XP, 2000, 2003 
Server) only. Windows NT 4.0 is working well without the new eleodg.exe as well. 
 
 
> This problem has been fixed now, it was a programming bug. New version under 
>  
> http://midas.psi.ch/elog/download/windows/elogd.exe 
 
 

Hey Terry,

I don't think this is possible, since in general you cannot define config settings in a way that it would only affect specific users. For example, you also cannot have different themes for different users (as stated here: https://midas.psi.ch/elogs/Forum/68112 )

Cheers

eddy

Hi Eddy,

Thank you for your response.  I had a feeling that was the case, but I had high hopes! :)  The reason I would like this feature is because I am trying to use ELOG as a software anomaly tracking log, where any user can create an ELOG and fill out "category", "computer" etc, but only administrators can fill out the "status" & "assignee".  If I am lucky, this will be an added feature in a future revision.

Thanks again,

-Terry