Virtual Radar Server Daily log

[ratchet]

This log has been working perfectly every day for last six months.Switched on two days ago to find log is showing one aircraft multiple times whether there were fifty aircraft or five hundred aircraft.the log is fed from Kinetic SBS3 and i note Basestation reporter is also only logging one aircraft.SBS3 is picking up normally and VRS is showing all aircraft normally.Any ideas guys?Tearing my hair out to fix

[Anmer]

Welcome.

Are you running Basestation off the SBS-3 or just VRS?

Is the SBS-3 running and is Reporter linked to an active sqb file?

And has anything changed recently?

[ratchet]

Thank you Anmer.

 Basestation is running off the SBS-3.

 SBS-3 is running normally showing everything it should.

 Reporter is linked to basestation sqb.

 Nothing to my knowledge has changed.Reporter however is only showing one aircraft out of however many may be visible on sbs-3.

 When i look at vrs, all relevant aircraft are visible but when i look at the days report there are multiple copies of only the one aircraft picked up by reporter.If there were twenty aircraft expected in the log it shows one aircraft twenty times.

[Anmer]

Thanks for that information.

If we put the VRS log issue to one side for a moment, is BaseStation Reporter showing all the aircraft that you see on the BaseStation map?  Can you see your recent sessions with the expected aircraft?

[ratchet]

No it is showing one aircraft out of however many may be on screen.If i look again in say anhour it still shows one aircraft but the info will have changed to an aircraft that is currently being picked up.

[Anmer]

Thanks.

On your Reporter launch icon or shortcut, right mouse click to find Properties and let me know the target directory.

[ratchet]

C:\Kinetic\BaseStation

[Anmer]

Thanks.  And now can you do the same for the BaseStation shortcut.

I'm trying to get a clue as to why Reporter's not showing current aircraft data.

[ratchet]

C:\Kinetic\BaseStation\BaseStation.exe

[Anmer]

Once again, thyanks.

Can we arrange a remote session whenever it's conveninet so I can take a look with you?

[ratchet]

yes.using what software? Teamviewer perhaps

[Anmer]

Not Teamviewer as they want to charge me a very expensive, annual licence fee.

I've sent you a PM.

[ratchet]

Evening Mike

I wanted to thank you for your offer of assistance re my basestation reporter prob.After much headscratching it is all up nd running again minus my main sqb file.Starting afresh all works great.

Re-installing my original basestation .sqb file reporter goes mentaladding wrong aircraft data and time.I will just have to bite the bullet and go with the fresh install i think.

Txs again

[Anmer]

Thanks for the update.

In nearly 20 years, I don't recall anything similar to your experience.

I can only assume the sqb has been corrupted somehow?

Many years ago a Kinetic Forum member suggested a routine that could (possibly) fix a corrupt sqb file.  I've not tested this myself but if you want to give it a try, here it is.  Obviously backup relevant files beforehand!

Use this possible sqb file repair at your own risk, and only work with copies of your Basestation.sqb file.

Create a new folder on your PC that you have full read-write access to I've called mine c:\SQBRepair

From the SQLite3 website download the command-line shell program for accessing and modifying SQLite databases.

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

look for the file sqlite-shell-win32-x86-3070701.zip and download.

from the downloaded zip extract Sqlite3.exe and place it in c:\SQBRepair or whatever you have named your folder

==
Open Windows Notepad and copy the following lines into notepad and then save the file as SQBfix.bat into the same folder c:\SQBRepair or whatever you have named it.

rename basestation.sqb basestation.old
sqlite3 basestation.old < repair1.txt
sqlite3 basestation.sqb < repair2.txt

===
Again using Notepad copy these lines and then save the file as repair1.txt and save again in the same folder. The leading full stops/periods are necessary.

.echo on
.output repairdb.txt
.dump
.exit

===
Once more for the following lines saved this time as repair2.txt note the Pragma line does NOT have a leading full stop.

.echo on
.read repairdb.txt
PRAGMA integrity_check;
.exit

===

You should now have in your folder these 4 files

SQLite3.exe
SQBfix.bat
repair1.txt
repair2.txt

Now copy your Basestation.sqb file into the folder, make sure that you have plenty of free diskspace on the drive I suggest at least 2 times the size of the sqb is a minimum.

Double click on SQBfix.bat and the repair process should start to run in a CMD window.

The Basestation.sqb file is renamed Basestation.old and is then dumped as text into a file named repairdb.txt this can take a while depending on sqb file size.
This text file is then read into a new Basestation.sqb file and the process will take even longer as the text is read back in to create the rebuilt sqb file.

As the process runs the CMD window should scroll as statements are executed. If successful then a integrity check is run on the new sqb and this should return OK. You can then close the CMD window.

If things stop and stall for a long time (say 5 minutes of no activity) then Ctrl+C should abandon things when the focus is on the CMD prompt window or try to close the CMD prompt window with the 'X' button at the top right.

This repair uses SQLite3's ability to dump a database and read it back in as SQL statements - it probably will only fix simple errors and does not guarantee a fix. Copy and keep your original sqb safe before trying anything.

As I noted in my opening, trying this is at your own risk - it worked here but that was using an undamaged sqb 100mb in size.

Finally I can't remember where I first came across this method on the web and it also has appeared on this forum and elsewhere, so apologies for not crediting those individuals.

==
Sabrejv

[ratchet]

Thanks for the info Mike.I had trawled the site for info and found this a couple of days ago.

On reflection i think the sqb file had not been totally correct for a while as when i used sqlite the details were different to what i had logged,i.e. much less info appearing on sqlite than in the log.many aircraft missing and yet the flights section was complete.i just have the laborious task now of starting again.

Thanks anyhow for the help.It is appreciated.

AA