Michael Schönbauer
Michael Schönbauer
if a reinstall solved it it was probably a mistake in the configuration file, (i.e timeframe too big) could also have been a discrepancy between server time and event log...
i wouldnt know. do try it out tho
Oh, I've been searching this little bug for a while now, currently think the frameworks `EventLogReader` might produce that problem. May I ask you some questions: - What was the...
hi thanks for the logs, ill look into it ( btw: if you mean that `26.01.2024 15:10:46 - [Debug]: Booster: 131 26.01.2024 15:10:46 - [Debug]: Booster not in XML, aborting.`...
#126 to locate it better
added code so i can locate this bug in .61. lets hope we get the stacktrace next time this happens. closing this, and hoping the bug reoccurs with stacktrace
thank you for running .61 and help me locate this! with your help i finally have the stacktrace so i can remove this bastard. will fix that today
 there it is, it was there all the way , i just didnt see it. also, it seems that this bug only occurs exactly one hour after manually removing...
closing this now
#53 being fixed soon