Lapper won't start after a problem

[Yisc[NL]]

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.

[Gai-Luron]

Hello,

Try to rename your DBS and start again. If lapper create a new and start the reason is that your renamed database is corrupted

Gai-Luron

[Yisc[NL]]

Hello,

Try to rename your DBS and start again. If lapper create a new and start the reason is that your renamed database is corrupted

Gai-Luron

Okay, DriftDB is corrupt, trashed it and all is okay now.

[Yisc[NL]]

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:


12/10/2009 2:39:28 AM

Lapper Instance 127.0.0.1/29996 abort!

SQL logic error or missing database
LFSLapper
bij LFSDbs.DbsAccess.executeQuery2(String _command) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \DbsAccess.cs:regel 137
bij LFSDbs.DbsAccess.executeQuery(String _command) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \DbsAccess.cs:regel 98
bij LFSDbs.gripDbs.DriverLapEntry..ctor(DbsAccess dbCon, String uN, String nN, String cN, String tN, Int32 LapTimeUsedForPb) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 633
bij LFSDbs.gripDbs.retreiveRow(infoPlayer currInfoPlayer, String trackName) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 483
bij LFSLapper.LFSClient.managePacket(NCN newConnection) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\managePacket.cs:regel 56
bij LFSLapper.LFSClient.Loop(Connect insimConnection) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\loop.cs:regel 889
bij LFSLapper.LFSClient.doloop() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\lfsclient.cs:regel 629
bij LFSLapper.LFSListen.Listen.goWorkMode() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 85
bij LFSLapper.LFSListen.Listen.start() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 126
System.Data.IDataReader executeQuery2(System.String)
Closing Instance...

[Gai-Luron]

need previous sql line in log file. Do you try with fresh DBS?

[Yisc[NL]]

need previous sql line in log file. Do you try with fresh DBS?

Not tried fresh DBS.
Here's the full message and in the mean time another instance has crashed, message is also below:


12/10/2009 2:39:28 AM -> SQL COMMAND :
SELECT * FROM fi_epb WHERE carName = 'FBM' AND trackName = "BL1" AND userName = "elrudo03"

-----------------------------------------------------------------------------
12/10/2009 2:39:28 AM

Lapper Instance 127.0.0.1/29996 abort!

SQL logic error or missing database
LFSLapper
bij LFSDbs.DbsAccess.executeQuery2(String _command) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \DbsAccess.cs:regel 137
bij LFSDbs.DbsAccess.executeQuery(String _command) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \DbsAccess.cs:regel 98
bij LFSDbs.gripDbs.DriverLapEntry..ctor(DbsAccess dbCon, String uN, String nN, String cN, String tN, Int32 LapTimeUsedForPb) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 633
bij LFSDbs.gripDbs.retreiveRow(infoPlayer currInfoPlayer, String trackName) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 483
bij LFSLapper.LFSClient.managePacket(NCN newConnection) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\managePacket.cs:regel 56
bij LFSLapper.LFSClient.Loop(Connect insimConnection) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\loop.cs:regel 889
bij LFSLapper.LFSClient.doloop() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\lfsclient.cs:regel 629
bij LFSLapper.LFSListen.Listen.goWorkMode() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 85
bij LFSLapper.LFSListen.Listen.start() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 126
System.Data.IDataReader executeQuery2(System.String)
Closing Instance...
-----------------------------------------------------------------------------



-----------------------------------------------------------------------------
12/10/2009 4:15:14 PM

Lapper Instance 127.0.0.1/29989 abort!

Het wachten is voltooid wegens een afgebroken mutex.
mscorlib
bij System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
bij System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
bij System.Threading.WaitHandle.WaitOne()
bij LFSDbs.gripDbs.lockBase() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 352
bij LFSDbs.gripDbs.updateRow(Boolean immediateUpload, String userName, String nickName, String datePb, String timePb, String carName, String trackName, DriverLapEntry driverLapInfo) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 360
bij LFSDbs.gripDbs.updateRow(Boolean immediateUpload, infoPlayer currInfoPlayer, String trackName) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 339
bij LFSLapper.LFSClient.managePacket(SPX splitdec) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\managePacket.cs:regel 464
bij LFSLapper.LFSClient.Loop(Connect insimConnection) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\loop.cs:regel 920
bij LFSLapper.LFSClient.doloop() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\lfsclient.cs:regel 629
bij LFSLapper.LFSListen.Listen.goWorkMode() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 85
bij LFSLapper.LFSListen.Listen.start() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 126
Boolean WaitOne(Int64, Boolean)
Closing Instance...
-----------------------------------------------------------------------------

[Yisc[NL]]

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.


-----------------------------------------------------------------------------
12/11/2009 2:24:26 PM

Lapper Instance 127.0.0.1/29999 abort!

An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
Mono.Data.SqliteClient
at Mono.Data.SqliteClient.Sqlite.sqlite3_open16(Strin g dbname, IntPtr& handle)
at Mono.Data.SqliteClient.SqliteConnection.Open()
at LFSDbs.DbsAccess..ctor(Debug pmyDebug, String DbName) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \DbsAccess.cs:line 45
at LFSDbs.gripDbs..ctor(Debug pmyDebug, String puniqueConnectionId, String DbName, Int32 LapTimeUsedForPbPar, String FtpServer, String FtpLogin, String FtpPasswd, String FtpRemotePath, String dateFormat) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:line 72
at LFSLapper.LFSClient.init(String pip, Int32 pport, String pWorkingDir, String pIniFile, String pSuperUsers, Int32 timeOutScript) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\lfsclient.cs:line 479
at LFSLapper.LFSClient..ctor(String pip, Int32 pport, String pWorkingDir, String pInifile, String pSuperUsers, Int32 timeOutScript) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\lfsclient.cs:line 256
at LFSLapper.LFSListen.Listen.goWorkMode() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:line 82
at LFSLapper.LFSListen.Listen.start() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:line 126
Int32 sqlite3_open16(System.String, IntPtr ByRef)
Closing Instance...
-----------------------------------------------------------------------------

[Yisc[NL]]

;1327410']Not tried fresh DBS.

Tried a fresh DBS put problem is the same.
I'm getting desperate :(

[Gai-Luron]

Lapper don't work on X64 system. momo DLL is in 32 bit

[Yisc[NL]]

Lapper don't work on X64 system. momo DLL is in 32 bit

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

[Yisc[NL]]

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:


12/12/2009 12:50:14 AM -> SQL COMMAND :
SELECT * FROM fi_epb WHERE carName = 'FXR' AND trackName = "BL1R" AND userName = "yisc[nl]"

-----------------------------------------------------------------------------
12/12/2009 12:50:14 AM

Lapper Instance 127.0.0.1/29994 abort!

SQL logic error or missing database
LFSLapper
bij LFSDbs.DbsAccess.executeQuery2(String _command) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \DbsAccess.cs:regel 137
bij LFSDbs.DbsAccess.executeQuery(String _command) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \DbsAccess.cs:regel 98
bij LFSDbs.gripDbs.DriverLapEntry..ctor(DbsAccess dbCon, String uN, String nN, String cN, String tN, Int32 LapTimeUsedForPb) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 633
bij LFSDbs.gripDbs.retreiveRow(infoPlayer currInfoPlayer, String trackName) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\Dbs \gripdbs.cs:regel 483
bij LFSLapper.LFSClient.managePacket(NPL newPlayer) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\managePacket.cs:regel 105
bij LFSLapper.LFSClient.Loop(Connect insimConnection) in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\loop.cs:regel 897
bij LFSLapper.LFSClient.doloop() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Client\lfsclient.cs:regel 629
bij LFSLapper.LFSListen.Listen.goWorkMode() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 85
bij LFSLapper.LFSListen.Listen.start() in D:\Dev\DevInsim\lapper\LFSLapper\LFSLapper\src\LFS Listen\Listen.cs:regel 126
System.Data.IDataReader executeQuery2(System.String)
Closing Instance...
-----------------------------------------------------------------------------


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.

[Gai-Luron]

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

Gai-Luron

[Yisc[NL]]

I've emailed you my whole Lapper directory.

[Gai-Luron]

Hello,


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

[Yisc[NL]]

Hello,


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?


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.

[Yisc[NL]]

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!

[Gai-Luron]

Witch update create this issue :Looking_a. I'm very interested for this. Maybe replace only sqllite3.dll ( download from the net ) with the last one can correct the issue.

http://www.sqlite.org/download.html

(take only the windows dll )

Gai-Luron

[SumBeam]

I also want to know which update it was. There were 7 updates I have deinstalled today. One IE6 update and six security updates.

KB955759
KB970430
KB971737
KB973904
KB974318
KB974392

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.

[Gai-Luron]

Ok ,thank you very much

Gai-Luron

[nl2dav]

*decided to post this in the bug report thread*

[Tim NL]

I also want to know which update it was. There were 7 updates I have deinstalled today. One IE6 update and six security updates.

KB955759
KB970430
KB971737
KB973904
KB974318
KB974392

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.

Hi Sunbeam or Yisc,

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

[Yisc[NL]]

Hi Sumbeam or Yisc,

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

Windows XP-SP3 x32

[Yisc[NL]]

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?

[Fire_optikz001]

how many servers do u have with out the 3? i have about 7 :P

[Gai-Luron]

Hello,

Do you have 2 LFSLapper.exe using same database? In this case crash can occur!

Try this crashTest programm. This app simulate 40 instances of Lapper with concurrent acces on DBS. Here no crash. Send me your report

Gai-Luron

[Yisc[NL]]

how many servers do u have with out the 3? i have about 7 :P

At the moment I have 11 servers running 24 hours a day, 7 days a week.

[Yisc[NL]]

Hello,

Do you have 2 LFSLapper.exe using same database? In this case crash can occur!

Try this crashTest programm. This app simulate 40 instances of Lapper with concurrent acces on DBS. Here no crash. Send me your report

Gai-Luron

No, I have one LFSLapper.exe (5.846) connecting to 9 servers and they are all using the same databases.

[Gai-Luron]

Hello,

I do a little modif in 9.1.3 to DBS access.

if you can migrate to this version.

Gai-Luron

Attached a 846 with this modification

[Yisc[NL]]

Hello,

I do a little modif in 9.1.3 to DBS access.

if you can migrate to this version.

Gai-Luron

Attached a 846 with this modification

I tried the new EXE but the problem is the same.
After some more research I found out that the problem plays up when Lapper connects to a server with people already on it.
Even a total shutdown and restart of Lapper can't solve that problem, so you have to wait until all servers are empty and then start Lapper again.
Does that ring any bell?

[Gai-Luron]

Hello, no reason to have this issue when on servers there are people.
Because i request all connection at this time.

If i can reproduce it, i try to solve, but without this, i can't do anythings