KiloJuliett

Remove the scenery entry pointed out by Urs from your scenery.cfg Open the DBbuilder Remove any existing databases Create a new database Select the new database for use Upload the latest support files

Frans, did you launch the application with admin rights?

Looks like the VATSIM URL is deleted somehow. Maybe you have some anti virus software installed that is changing the file this URL is saved in? The servers settings file is Documents\AivlaSoft\EFB2\Server\Settings\serverSettings.txt If the problem returns, can you check this file or the respective dialog of the EFB Server and let us know, what the VATSIM URL field shows?

I may be wrong, but I thought the TCP Listener is part of the .NET Framework used for EFB. Usually, a reboot of the computer clears such issues. Did you reboot after installation or when this issue happened?

Happy to hear it worked. However, we have to be aware that this is not a permanent solution and the issue will most probably return once you change sceneries or update the nav data set and as a consequence re-run the database DBbuilder. Hopefully we can find some other ideas how to fix this issue permanently until then.

Mike, you shall NOT remove the file in the server folder. Otherwise the client has no file to compare with and won't complete the file database synchronisation. The idea of the work instruction I gave you is to overcome the issue on your system of the unzip process of your client. The desired outcome is that the client recognizes the manually extracted file as already available and won't try again to extract it from the server location (because he recognizes they are the same version). If you delete the server file, this won't work.

Yes. Those file are copied into the client folder by the client application. According to the log, there is an issue while unzipping that file. So I thought you might at least temporarily bypass this by unzipping the file yourself. Can you post again the latest support files?

Ok. Try this: Close EFB Server and Client Navigate to Documents\AivlaSoft\EFB2\Server\DbBuilder\Ready\FSXSENG\ Open the file airports.bin.zip and extract the file inside (airports.bin) to Documents\AivlaSoft\EFB2\Client\Database Run EFB Server and Client Any success?

Hi Mike There seems to be an issue with the zipped airports database. This can have different reasons. Can you first try to recreate the database in the DBbuilder again? Best delete all existing databases and start creating a new one again. Is the result still the same?

Hi Jirka Thanks for reporting. The port 13 issue is limited to the demo version.

Can you try once to start EFB Server and Client before you run the simulator?

Hello Jirka Where do you get this message from? EFB Client or Server? I can't find traces in the log files that you run Server and Client in parallel after you re-created the database yesterday. Upon launching the Client the first time after a new database has been created, the client will update its local databases, which also should be logged in the Server log. There is no trace of this either.

Hi Chris What about the options TRFC and T/LBL? Are they activated? Did you check the traffic monitor of EFB Server?

Is there any traffic in your area at all? Check the traffic monitor of the EFB server if there is any traffic (ref. Manual 5, $7.1.4). Are you connected to VATSIM? Maybe it is out of range (filtered)?

To me, it looks there are two different kind of issues. The error you get seems related to the weather information received. When exactly do you get these kind of error message? What is your interaction with the application right before? Still can't find a reason why VATSIM data should work. Do you have TRFC, T/LBL and O/BND activated?

Hello Volker What is the error you get? Eventually, we require also the support file of your client to better understand what is going on. But from the server file, I can't see that there is an issue with the VATSIM file. Make sure you have the relevant display options TRFC, T/LBL and O/BND activated according your preferences.

Hi Jake X-Plane is currently not supported. Thanks for reading the specifications: http://aivlasoft.com/specifications/index.html. You can subscribe to the Announcements forum to get a notification when news (such as X-Plane compatibility) are posted: https://forum.aivlasoft.com/forum/18-announcements/.

Hi John No need for a new profile. Follow the manual instructions in 5 Client, §12.2 Profiles Editor, especially the subsection about Airfile names.

Michael, then you saved the route accidentially with the SID/STAR waypoints included. Revise the route so it doesn't include SID/STAR waypoints and you will be able to use it with successive AIRACs (if the routes and waypoints remain the same).

Maybe an issue of zoom? Do other traffic show a label? Did you check your settings for the label?

The V2 from aerosoft: https://www.aerosoft.com/de/flugsimulation/flight-simulator-x/szenerien/909/mega-airport-oslo-v2.0?number=AS12892

ENGM looks fine on my installation with the latest Oslo scenery installed. It's as Oski said, it only depends on the sceneries you have installed. So if you have done this properly, everything is fine.

Happy you got it working. FSX:SE sometimes has it's small differences from the "original" FSX. As far as I know, EFB is looking into the registry to determine the main sim and cfg file folder. Do you remember if you set the scenery.cfg in the EFB DBbuilder yourself or was it detected automatically? The latter would actually point to an issue in the installer of FSX:SE (writing not the actual used scenery.cfg folder to the registry), which I hope does not exist. Just out of interest, what is the folder your actual scenery.cfg is saved now?

Hey Dave As you have found the log file, why didn't you have a look into it to notice that every single scenery listed in your fsx.cfg generates the warning: FOLDER DOESN'T EXIST!. The paths given for the scenery indeed don't look the way they normally do. Or do you have all sceneries in your documents folder? A significant issue is the missing magdec.bgl in the folder base\scenery. Please check your folder structure. Can you confirm that your FSX is actually using the file C:\ProgramData\Microsoft\FSX\scenery.cfg for saving/changing your scenery list? You might check this by adding a new scenery and check whether it is listed in this file afterwards. Does your FSX run fine? No issues with sceneries?

Traffic display via EFB is not dependent on any account from one of the networks. You always can select one of the ressources to turn EFB into a traffic map. So you can easily also test VATSIM as I can test IVAO, even though I have no account there. The client you are connected to the network is responsible only to feed the traffic from around your area.