• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Problem with Active Sky 2016

Navy Chief

Senior Member
On the recommendation of someone, I bought Active Sky 2016, but am having a problem with errors, as shown when it boots up. Not able to fix so far. Here are screenshots. Note: I only have FSX SE installed, but for some reason, I have two directories for appdata.... NC

attachment.php


attachment.php


attachment.php
 

Attachments

  • AS2016a.jpg
    AS2016a.jpg
    62.1 KB · Views: 0
  • AS2016b.jpg
    AS2016b.jpg
    63.3 KB · Views: 0
  • appdata Roaming Microsoft FSX AND FSX SE.jpg
    appdata Roaming Microsoft FSX AND FSX SE.jpg
    92.4 KB · Views: 0
Hi NC:wavey:

AS16 (like ASN) writes an entry to exe.xml. This is what it added to mine:

<Launch.Addon>
<Name>as_btstrp_config_manager</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp_config_manager.exe</Path>
</Launch.Addon>
</SimBase.Document>

It's possible that you don't have an exe.xml present or.. it's garbled in some way. Not many programs write to exe.xml.. most add bits to dll.xml so unless you've used a program that actually needs it, you may not have noticed.

EDIT: I see you have both FSX and FSX SE installed. Depending on which one you're using, check to see if exe.xml is present. It's possible AS16 doesn't know where to look.

ATB
DaveB:)
 
Hi NC:wavey:

AS16 (like ASN) writes an entry to exe.xml. This is what it added to mine:

<Launch.Addon>
<Name>as_btstrp_config_manager</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp_config_manager.exe</Path>
</Launch.Addon>
</SimBase.Document>

It's possible that you don't have an exe.xml present or.. it's garbled in some way. Not many programs write to exe.xml.. most add bits to dll.xml so unless you've used a program that actually needs it, you may not have noticed.

EDIT: I see you have both FSX and FSX SE installed. Depending on which one you're using, check to see if exe.xml is present. It's possible AS16 doesn't know where to look.

ATB
DaveB:)


I only have FSX SE installed. NO idea why there are two directories. I have tried "pointing" AS16 to the SE directory, but it is not recognizing it...:dizzy::banghead: NC
 
Hmm..

Looking at the date on your FSX folder (not SE).. something has written to it today. The date on your SE folder is 7th March. I get the feeling that this is the cause of your problems. Did you actually uninstall FSX? MS programs are notorious for not removing everything and FSX is a pig!

ATB
DaveB:)
 
Hmm..

Looking at the date on your FSX folder (not SE).. something has written to it today. The date on your SE folder is 7th March. I get the feeling that this is the cause of your problems. Did you actually uninstall FSX? MS programs are notorious for not removing everything and FSX is a pig!

ATB
DaveB:)

A long time ago. The thing is, my FSX Steam works just fine; no problems. Am somewhat leary of messing with anything, but just unsure how to proceed. NC
 
Yep.. and I feel your trepidation. I'm a big fan of 'if it aint broke, don't fix it'!!

Wish I knew what to suggest for the best. It certainly looks like AS16 might be writing to the wrong place but it knows your install is SE so the program isn't seeing the exe.xml file. Do you have an exe.xml file in the FSX SE folder? If you don't or if the one there is blank.. it may be worth copying the one from your FSX folder to the SE folder. Have a look at it first to check there's nothing that may cause SE to trip up. The only things you should be seeing are the executable for exe.xml itself and the as bootstrap entry. There may be an AICarriers entry too if you've had that 'auto load'. Tread carefully and you might get away with it. Doesn't explain why AS16 might be writing to the wrong place though.

ATB
DaveB:)
 
Active Sky is capable of dealing with installations of FSX and FSX-SE together, whether they
actually exist or whether they are there because the registry still says that they are.

You could always try following what it says on the screen and back up and then delete
the file it's having trouble with, as it is asking you to do.
 
That is true but why is AS trying to write to it anyway?

Pete.. open the FSX folder, locate exe.xml and rename it to exe.bak then see what happens.

ATB
DaveB:)
 
That is true but why is AS trying to write to it anyway?

Pete.. open the FSX folder, locate exe.xml and rename it to exe.bak then see what happens.

ATB
DaveB:)


Will try that and get back to ya....! NC

UPDATE: Dave, your suggestion worked, THANK YOU!! And everyone else who made suggestions as well. You folks, as always, are the best! NC
 
OK mate.. it should do no harm as the FSX folder is, to all intents, inactive. Renaming the exe.xml folder in there will at least stop AS16 seeing it;)

ATB
DaveB:)
 
Hello,
Renaming the file has of course the same effect as deleting it.
I would expect that Active Sky has now written
a new exe.xml file into the apparently redundant FSX folder.
I would think that it will continue to check that location.
While it should do no harm, it does suggest that the windows
registry has FSX recorded in it as well as FSX-SE.
 
Is it a case of the folder is there so AS is writing to it or AS is expecting it to be there because it's still in the registry.. or a combination of both? If it's advised to leave FSX in the registry even if FSX SE is installed and FSX isn't, then surely.. this is a vicious circle. If AS is writing to it because it's a legitimate folder (even though the host program no longer exists) perhaps renaming the old FSX folder would stop it. Question is though.. would it complain if it wasn't there?:dizzy: It all seems rather too clever for it's own good.

Still.. we've yet to learn if renaming the exe.dll has worked. Fingers crossed it will have but I have my doubts.
ATB
DaveB:)
 
Is it a case of the folder is there so AS is writing to it or AS is expecting it to be there because it's still in the registry.. or a combination of both? If it's advised to leave FSX in the registry even if FSX SE is installed and FSX isn't, then surely.. this is a vicious circle. If AS is writing to it because it's a legitimate folder (even though the host program no longer exists) perhaps renaming the old FSX folder would stop it. Question is though.. would it complain if it wasn't there?:dizzy: It all seems rather too clever for it's own good.

Still.. we've yet to learn if renaming the exe.dll has worked. Fingers crossed it will have but I have my doubts.
ATB
DaveB:)


Oh yes it did work! I had replied almost instantly, but you missed reading that. Thank you! NC:encouragement:
 
New glasses and I STILL missed it:banghead:

Thanks for posting NC.. glad you're up and running:encouragement:
ATB
DaveB:)
 
Back
Top