Welcome to Radarspotting. Please login or sign up.

October 23, 2026, 07:29:24 AM

Login with username, password and session length

New Members

New Members

You should get an activation email when you join.  If not, please use the Contact option.

Market Place

13th Octoner 2026

For Sale

ProSticks and RPis

AD Pro seems to unable to load a new session

Started by Harpic, January 25, 2016, 09:50:54 AM

Previous topic - Next topic

0 Members and 0 Guests are viewing this topic.

Harpic

Hi Tristar,
Done what you asked and set the database path to the virtual store, and yes we thought we had cured the problem.
Ad load a new session although it was not showing that many contacts (See Screen Shot)
It turned out that I had connected the Antennas round the wrong way.
After changing them around we loaded AD and Basestation and everything seemed to be ok a Full screen of contacts. we let it run for a few minutes and powered down.

On restarting and pressing the AD start tab, AD loaded the session that can be seen in the screen shot, although a different session then we had before it is the same problem of trying to load an old session rather then starting a new one.

[Attachment deleted by Admin to save file space]

Tristar500

I'm struggling now !
Am I right in saying the screenshot in your latest post was taken before you changed your antennas around or was it after you had restarted Basestation & AD the second time, or are they one & the same ?
If you start Basestation & AD now, or if it is currently running, what number is the 'Current Session' showing as ?

Harpic

Sorry to confuse you that second screen shot is before I changed the antennas around and is also the session AD loads or is trying to load every time when click on start to start a new session.

The current session number  1694  27/1/2016 

Tristar500

It wasn't your post I was really struggling with, it was thinking of a cause & solution for your problem !
We know that AD worked correctly when you pointed it to the virtual store and again after you changed your antennae but after a further restart it reloads the pre-antennae change session.
So, a few questions:
1. Did you close down both Basestation & AD before changing the antennae over & restart both again afterwards ?
2. When you say you "powered down" when it ran correctly after changing the antennae did you close both programs down ?
3. Did you restart Basestation from the same icon or location in each instance ?
4. Could you look in BaseStation Reporter & see what the dates & times of the last sessions were ?
Sorry if I'm asking the obvious but I'm just trying to understand the exact sequence of events to find a way forward. If you did restart Basestation on each occasion you should now be on session 1696 (at least), so where are those sessions I wonder.
I'm beginning to wonder if you have multiple instances of Basestation installed which are writing to different locations.



Roadrunner

Just one thing, If you look in BaseStation reporter are the dates/times of the recorded sessions the same as listed in AD Pro on the delete sessions tab?

Harpic

Hi Tristar & Corsa,
in answer to your questions,

1. Did you close down both Basestation & AD before changing the antennae over & restart both again afterwards ?
1) yes. BS first then AD

2. When you say you "powered down" when it ran correctly after changing the antennae did you close both programs down ?
2) yes

3. Did you restart Basestation from the same icon or location in each instance ?
3) Yes

4. Could you look in BaseStation Reporter & see what the dates & times of the last sessions were ?
Sorry if I'm asking the obvious but I'm just trying to understand the exact sequence of events to find a way forward. If you did restart Basestation on each occasion you should now be on session 1696 (at least), so where are those sessions I wonder.
I'm beginning to wonder if you have multiple instances of Basestation installed which are writing to different locations.
4) we did on Sunday as the sqb file is the last known good database

Basestation is only installed in one location.
Basestation has not moved. Even as the problem started



I have had a look at the reporter log and these are the logs showing in it around the time of the problem.

Start Time                                                     End Time
27/01/2016  20.54                                        No time as still running
27/01/2016  15.01                                        27/01/2016   16.00
27/01/2016  14.51                                        27/01/2016   14.57
27/01/2016  14.16                                        27/01/2016   14.28
19/01/2016  21.04                                        19/01/2016   21.05
14/01/2016  14.23                                        15/01/2016   00.41

There is definitely some missing in between the 19th and the 27th


Having seen Corsa'a post I had a look at the Delete AD sessions list, and this is where I am now really getting confused as this list show all the sessions that I think you refere to as missing.

Start Time                                                     End Time
1666     16/01/2014  18.24                                        16/01/2014   18.27
1667     16/01/2016  12.26                                        16/01/2016   12.32
1669     16/01/2016  12.54                                       

The Sessions then run from session 1669 to 1694 showing a lot of session that do not show in the BS log.
I have not got a clue why all the 2015 sessions are not showing as logic tell's me they should be in between session1666 and 1667

Harpic


Tristar500

Hi Harpic,
Many thanks for your answers, from the data you've given I'm positive that you have several sqb files in use in different locations. In the screenshot you posted it was session 1694 on 27/01/16 with entries timed between 1406 & 1408, however there is no session covering these times listed in Reporter. The sessions listed from 1416 onwards on the 27th probably equate with those I thought were 'missing' though, which suggests some sort of file location change has happened
Can you do a search for files named Basestation.sqb (including hidden files) & let us know the result ?

 

Roadrunner

No problem, the reason I asked the question was I have had what appeared to be open sessions so I just deleted then and for me that solved the problem but not sure how if why. The loss of a session is probably better then a few days data.


Mike

Harpic

Update as to what is going on.

Mike,
Managed to connect to a virgin fiber connection and it still loads the same session so think we can defo rule out the Mobile connection as the problem.

Tristar.
I think I have this right these are the results for the search of Basestation.sqb files i'm not sure how you do hidden files.
I spoke to my mate before I did this search to let him know what you all are suggesting and he was saying if the search does not reveal anything then we might do a road Runner has said and deleate the session files as i'm not really concerned about those it's the main Database that i'm more worried about.
we are thinking as a last resort of doing a total fresh install again on a completely new Hard drive and a fresh install of Windows 7 but will probably update to Windows 10 as I have been thinking of renewing the drive for sometime now.
I am hoping if we do this that as it would be a new hard drive and a clean OPS, it will be like starting from Scratch and should only be reading the one Sqb which we want it to. The Sqb file would be the first one that is showing in the search list.





[Attachment deleted by Admin to save file space]

Tristar500

Harpic,
I wouldn't go down the re-install road just yet as I'm not sure it will solve your problem. From the info' you've given us I don't think there's anything wrong with AD, it's just the location of the sqb file that's the problem. Basestation is writing the sqb file to 2 different locations on a 'random' basis (the 'Basestation' folder in Program files and also in the 'Virtual Store' folder) whilst AD can only look at one specified location.
I would point the finger at the Windows 'User Account Control' settings (I assume Windows 7 has UAC ?), my understanding of this is that running Basestation (from the Program files folder) with it OFF will cause the sqb file to be written to the 'Basestation' folder whilst if set to ON will cause it to be written to the 'Virtual Store'.
Moving your entire 'Kinetic\Basestation' folder from the Program files folder to a new folder on the root (C) drive, then resetting the AD Database path to point to this new location should avoid any problems from UAC in the future. I have always had mine setup this way and have had no problems with it (so far !).       

Harpic

Well guy's I don't know what to say, The Men in the White Coats are coming tomorrow   ;D

After Tristar's last post I showed my mate his reply and as my mate said we have done everything that was suggested before so we were at ends wits.
I was also having problems with the phones connection having content blocked by Vodaphone, so I popped into my local store and got them to check to see if the blocker was off, it turns out that it was on, but this could not be the problem as AD & Bastation had been working ok for sometime.
The only problem I had was not being able to connect to Airframes.org when using the phone as internet connection.
Well about 7.15 tonight I was thinking what Tristar had put in his last post and thought lets give it a go and as my mate had said as the UAC was off let's direct the path back to the programX86 Basestation instead of the Virtual store.

Well would you believe it the old session what was being loaded never appeared and AD loaded as session from yesterday saying updating and was populating all the new enteries this then stopped and was saying Real Time.
As Basestation was not running  I take it no information would be going to AD so I switched AD down, saved the database.
I then loaded Basestation and when this was running I then loaded AD pressed the Start button and Wam Bam thank you mam a new session was running and populating it is still running as I type this post.

So as I say the White coats are coming, because Christ knows why all of a sudden everything seems to be back working.
I'm not counting my chickens just yet, but if everything works fine over the next few days.
then I would just like to thank Mike, Roadrunner and Tristar for all the help and guidance over the last 2 weeks.
Thanks and Cheers Guys your all Stars.

Oh well let see what's about on the SBS tonight (I have been having withdrawal symptoms) it's back to watching the screen and the airways.

Regards
Harpic

Roadrunner


Harpic

Quick update,
just to let you guy's know it's still all running and all seems to be working fine even after daily shut downs.   ;D ;D ;D ;D