Hi Guy.
Can anyone help ? I have got a problem with AD Pro.
When I start up Ad fires up all ok but when I click on the start button to start a new session AD loads an old session instead of a new session.
All the entries from an old session show on the screen but that as far as it goes
The process bar say's that it is Loading but nothing else happens.
Under the loading bar is the message saying Current session 2291 19/1/2016 - Latest.
This date has since changed I was originally 15/1/2016.
When you go to shut it down/stop you get the normal message of do you want to Backup your Basestation Database, to which I reply No.
I then get a message saying "Unable to Deleate Session Route and Callsign Date from Aircraft Records"
Pressing the OK button which is the only option you get Shuts AD down.
But of course when you try to reload AD you get the same scenario start all over again.
My friend who is pretty handy with computers has had a look for me and we have re-installed both fresh Current Basestaion and AD programes and we had checked the Sqb Database is not the session that is showing and AD is pointing to the correct SQB database.
Database path is C:\Program Files (x86) Kinetic\Basestation.
We done this at my friends using my SBSer etc only using his internet connection and everything seemed to run perfect with a new session loading and adding data, so we thought a re-install has cured the problem.
I returned home connected everything up and fired it all up and I get the problem of loading this old session as mentioned above.
The only thing that is different from being at my friend is that I run my internet connection by tethering off my mobile which is Vodafone as my boy works for them and the usage is dirt cheap.
I have been running this way for 5 months with no problems at all until this.
As I said the other day in a thread on the forum. I am a Numpty when it comes down to the workings of Computers but my friend is ok and it is part of his normal work so he knows a fair bit but not the finer points of Basestation and AD.
We both cannot seem to get our heads around this problem as we can not see where AD is getting this old session from as we removed all previous backed up SQB files when we done the fresh installs.
Even more of a puzzle to us, is why would it appear to have ran ok at his place and then 30 min later go tits up.?
Guy's any help or being pointed in the right direction would be greatly appreciated.
Thanks Guys in anticipation.
Harpic
When it worked OK at your friend's place, were you using the same PC that you use at home and the same data files?
Was the only difference his SBS and Internet connection?
Yes Mike my lappy.
Took the lappy and the SBs to his place so we could do it all on his super fast internet connection.
Thanks. And did you leave AD Pro running at his place for long enough to have replicated the issue?
Can you run Control Panel and check you only have one instance of AD Pro installed?
Check control panel only one AD running installed 24/1/2016
We installed ran Ad it seemed to be working all ok, so we shut down and restarted all was working fine. we done this a third time a left for for about half an hour never showed the problem at his place ran as sweet as a nut.
Mike I have to shoot out for an appointment so i'll check any reply's you make when I return cheers mate.
Thanks.
The SBS should not be an issue.
Can you try using a normal Internet connection, just to eliminate your Vodafone option?
That was going to be our next option just so we could eliminate a Normal connection Mike.
only problem is that I don't think my mate is available till Wednesday so i'll have to wait.
Will let you know as soon as we try what the result is.
Cheers Mate
I don't think the internet connection is an issue here, once AD Pro has opened it should operate without a connection, it just won't populate anything from the GAS database.
I tend to think that there might be a virtual store type issue involved here. The 'Active' session is created each time Basestation creates a new session and the data is held in a temporary 'Active' table in the sqb file. If Basestation is writing to a different sqb file location than the one you directed AD to look at it will never replace the 'Active' table used by AD, that will always remain as the last session created in that particular sqb file.
As a matter of interest if you go to the 'History' - 'Select Old Session' option on AD Pro do you see any sessions created after the one it loads ?
I don't think the Internet connection is an issue either but would like to eliminate it, especially if AD Pro "behaved" with the same installation but different connection.
There may be a sql "journal" file lurking somewhere that might need to be deleted. I've been trawling through old emails between Gary and I to try and find a clue. No luck so far.
Tristar,
Thanks I think you may be on to something.
As I have just done what you asked and looked in the history old sessions and yes I do see old session in fact it looks like there are every session since I had the sbs.
Sessions No1 to 2291
2291 looks to be the one its is trying to load as the session number and the file date match that what is showing on the AD screen.
If you have run Basestation since session 2291 on 19/01/16 (I take it from your post you have) & those newer sessions are not listed then that confirms an sqb file issue.
To see if AD is looking in the right place open the Aircraft Display window (i.e. the Kinetic logo, marked 'open SBS window', top left of the main AD screen); select 'Data' then 'Delete Sessions'. Does the list show any sessions since 2291 on the 19th ? (click 'close' & not 'Delete' to exit !)
This option looks directly at the 'Sessions' table of the Basestation.sqb file rather than the 'Active' table used by AD so, if newer sessions are present, then AD is looking at the correct file, if not then you probably have duplicate Basestation.sqb files.
From the information in your original post I suspect that Basestation is writing to an sqb file in the 'Virtual Store' rather than the location you have pointed AD to.
Hi Tristar,
Thanks for this info, have looked and done what you have asked and there were no enteries after 2291 19/1/2016 the file was removed and the next file under was 14/1/2016
on running AD the file 2291 was loaded and checking back doing what you asked the 2291 file has reappeared into the data list.
As this file has re appeared I take it that as you say there must be a copy being written to the virtual store?
as I said i'm a bit of a numpty as regards computers files and there locations.
Is there an easy way of looking at the virtual store to check if not then I will have to wait for my mate to have a gander at it.
Really appreciate the help you are giving. without it all running which is basically my life now.
Im sitting around like a Bulldog Chewing a Wasp especially when there is lovely clear skies as well
Harpic
I have looked at Chris Taylors Video on the forum and found how to look for the Virtual store,
From what I can make out, it looks like it is looking at the Correct SQB file 26/1/2016 but I have noticed the User Data file is showing the date of 19/1/2016.
Could this be where the problem is inside this data folder?.
There are 2 files Temp1 24/1/2016 and Temp2 22/1/2016 xml files inside this folder.
[Attachment deleted by Admin to save file space]
Don't worry about the User Data folder as I don't think it's relevant. Your screenshot confirms that Basestation is writing to an sqb file in the Virtual Store, however you've set your AD program to look at an sqb file in C:\Program files (x86)\Kinetic\Basestation directory (from your original post), which is, of course, not being updated by Basestation.
Setting the AD Database path to point to the Basestation.sqb file in the Virtual Store should theoretically enable AD to run correctly but, I seem to recall from previous posts that there have been problems in running this way; try it though and see what happens.
Personally I have managed to avoid the Virtual Store issue by having my Kinetic Basestation folder (& PlanePlotter folder) located in the route directory.
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 loaded 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 (In the previous screen shot) 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]
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]
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 ?
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
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.
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?
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
Sorry Roadrunner what made me say Corsa
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 ?
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
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]
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 !).
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
That is why I love (Not) computers !!!!!!!
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
Glad to hear it !