My lapper crashed this afternoon and now I can't start it anymore.
As soon as I start Lapper.exe I get a fatal error and Lapper is closed.
I've restarted my dedicated server but that didn't solve the problem.
Since nothing has changed on my scripts for over a week, I guess the problem is with the database.
The problem is, I have no clue how to check that and if needed, how to fix it.
Help would be highly appreciated.
Well it seems the problem isn't gone after all.
Lapper (5.844) doesn't crash on startup anymore, but as soon as someone completes a lap, the following error is given and that instance of Lapper goes in standby:
Apart from the problem above, I also have another problem with the latest (5.910) version of Lapper. I've just downloaded it from the site, started an LFS server, opened the insim port, connected lapper and then it goes to standby within seconds with the following error in the log. I'm trying this on Windows 7 Ultimate (x64) so that might be the problem. In order to solve that I've enabled running the application as Windows XP-sp3 but without any luck.
Okay just to make sure, the problems I'm having are with Lapper 5.844 on a Windows XP-sp3 (x32) dedicated server. In order to find a cure, I tried the new Lapper 5.910 on my own pc which has Windows 7 Ultimate (x64).
Once more I closed down Lapper, renamed all DBS files to *.org and restarted Lapper.
Then I connected to one of my servers, Pitboard config screen came up, I saved my settings, all working as intended.
After that I picked the correct car for this server, clicked Join and bang, Lapper in standby with the following error:
So the problem isn't with the database, the problem isn't when someone completed a lap, but it's happening as soon as the first person is trying to get on track after Lapper has started.
edit: I tried with Lapper 5.846 and a clean DBS.
At first it seemed to work but then the same problem as above came up.
Sometimes on just entering the server, next time on entering the track.
I've switched Lapper off completely now.
Very strange, most server run with this version. Try with last version in XP with a clean folder and without change anything in config file. execpt connection id.
There is error on DBS and there is no reason. The SQL command seem clear
What is the database name? You can also send me all your LFSLapper folder to test it here
Here it work, but i can start only one instance. Do you try with only one instance? Put a # before rest of line. Maybe a deadlock. IF with one instance don't work, try to reinstall net framework.
What are the server using same database?
# Configuration of LFSServer to be Managed with LFSLapper # One line per server # Remote port is the port used to manage LFSLapper remotely, future extension # One remote port per LFSLapper on one machine, autoStart is optionnal #Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autoStart remotePort=3001; RR_XFG|gr1|127.0.0.1|29989|./RR|RR_XFG.ini|autowork #RR_PUB|gr1|127.0.0.1|29996|./RR|RR_PUB.ini|autowork #AB_MID|gr2|127.0.0.1|29991|./AB|AB_MID.ini|autoWork #AB_FOR|gr2|127.0.0.1|29993|./AB|AB_FOR.ini|autoWork #AB_END|gr2|127.0.0.1|29994|./AB|AB_END.ini|autoWork #AB_S2L|gr2|127.0.0.1|29995|./AB|AB_S2L.ini|autoWork #RR_L13|gr1|127.0.0.1|29999|./RR|RR_L13.ini|autowork #RR_BNG|gr1|127.0.0.1|29982|./RR|RR_Banger.ini #RR_S2L|gr1|127.0.0.1|29998|./RR|RR_S2L.ini|autowork
I already tried with one instance but same problem.
This afternoon I did a full new install of 5.846, started with the default script and that worked, then I made the modifications I need and it still worked with one instance. But as soon as 2 or more instances are running the problem comes up again.
Yes, all servers are connecting to the same database.
For now I'm really fed up with this so I decided to switch off Lapper and let it be that way for a while, I've had more then enough of this.
Maybe it has something to do with the latest Windows updates I installed in the beginning of this week, but I've no energy to go and search for that.
Thanks to Sumbeam, would didn't want to give up, the problems with Lapper are solved now.
She deinstalled the latest installed Windows updates and Lapper is running smoothly again.
Well done Sumbeam!
Witch update create this issue . I'm very interested for this. Maybe replace only sqllite3.dll ( download from the net ) with the last one can correct the issue.
I think one of these six updates, causes the problems. I think I'm going to sort that out this week, not tomorrow, because there are league-races on the servers. We will let it know if we can sort that out.
But, for now it is working, no problems at all. Thanks for your support Gai.
which windows version are you using?
My server runs at win2003 32 server.
Just in case if someone installs some windows updates and my server quits to.
I might have found the cause of the problems. Uninstalling the updates cured the problem in the first place, then we tried reinstalling them one by one but the problem wasn't returning then. A little later I added more servers to Lapper and the problem re-appeared again, so we decided to uninstall them again and leave it that way. All was working fine for two days, until the moment I added 3 more servers this morning. When I came home from work and checked the server, several instances of Lapper had crashed with the error provided earlier. I closed down Lapper by giving the 'quit' command, restarted it and until this moment everything is working fine again.
So my guess is that the problem has something to do with adding extra servers while Lapper is running. Could that make any sense?
. I'm very interested for this. Maybe replace only sqllite3.dll ( download from the net ) with the last one can correct the issue.