Hi Xuan,

Sorry for the delayed response.  I just got back from my travel.  I tried your solution, but in my system I don't see elogd.h in the src folder.  Here is what I see and also I don't see any "make" binary in the folders.  I'm running the Windows version.

Thanks.
Illam

My apologies for posting this question. I have found the solution.

We had two log books each with the same variable called "Ticket" but different values. When an entry from one was Moved to the other the counter was confused. I had to manually change the value of "Ticket" to match the convention of the log book that the entry was now in.

Thanks

All I can offer is send me your config file for the problematic logbook, and 
I will try to reproduce the error.

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. 
 
 

> 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.

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.

> 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