9 hours ago, funflyer66 said:

C:\Program files\LorbyAxisAndOhs_MSFS_Documentation.pdf

Is that really what it says? There is something missing from that path.

As for the error message itself, something is blocking access to the AAO user manual. This would happen if you have the PDF open on your computer, so another process is keeping it locked. I have no idea what that could be though. Maybe the virus scanner, a backup solution, some kind of preview app? Impossible to diagnose from the outside.

You could try and uninstall the previous version, then check if the installation folder is really gone. If not, delete it yourself, then install the new version.
The installation folder is here: C:\Program Files\LorbyAxisAndOhs_MSFS

Also, make sure to extract the installer exe first from the ZIP file (=pull it onto your desktop first). Don't just doubleclick it inside the ZIP.

Edited August 20, 20214 yr by Lorby_SI

The only thing that worked was removing the AxisAndOhs folder in the C:\Program Files. It installed fine after I did that and is working. Thanks for your help. Jack

On 8/18/2021 at 1:17 PM, FlyingJ said:

Dear Lorby_SI,
I'm trying the Axis And Ohs Demo (v2.10 b25). It's a great app, however I have problems with Web FIPs: I'm not able to connect from other devices on the same network using the correct link. It works on the same computer, but not from other devices.
I must say that I normally use such apps without any problems, for example WebFMC for X-Plane, it is not a port or router problem.

This is what I tried to do:
- completely disabled the Windows firewall, both on the Axis And Ohs computer and on the client device;
- changed the port, even using ports that work correctly with other apps;
- tested by connecting two computers directly via Ethernet.

I tried using two systems:
- Windows 10 21H1 64 bit + FSX Steam Edition + Axis And Ohs Demo for FSX-SE;
- Windows 7 SP 1 64 bit + FSX Gold + Axis And Ohs Demo for FSX.

Browsers used: Firefox and Chrome (the latest versions).

Does anyone have the same problem?

Any ideas why?

Thank you!  🙂

Any idea about this?

Thank you!

On 8/24/2021 at 2:24 PM, FlyingJ said:

Any idea about this?

Thank you!

Network security is tricky. This could be anything from a local firewall to settings on your router.

Make sure that the IP address that you call on the remote browser really is the primary IP of your computer. AAO is just showing the first one that it finds, but it listes to all of them. Don't disable firewalls, instead make sure that the TCP port is properly allowed through them. 

Edited August 25, 20214 yr by Lorby_SI

On 8/25/2021 at 9:53 PM, Lorby_SI said:

Network security is tricky. This could be anything from a local firewall to settings on your router.

Make sure that the IP address that you call on the remote browser really is the primary IP of your computer. AAO is just showing the first one that it finds, but it listes to all of them. Don't disable firewalls, instead make sure that the TCP port is properly allowed through them. 

Yes, the computer IP is correct, it is also set as static IP.
The port is open, all looks fine and with other similar apps everything works.
It is very strange, can you confirm that with the latest build it works for you?
I would like to buy Axis And Ohs mainly to use this function! 😁

11 hours ago, FlyingJ said:

It is very strange, can you confirm that with the latest build it works for you?

No problems here

HP laptop with P3D and Samsung smartphone, both connected to the same Huawei wireless router, I can stream a couple of WebFIPs just fine using the default port 8080.

On 8/27/2021 at 10:45 AM, Lorby_SI said:

No problems here

HP laptop with P3D and Samsung smartphone, both connected to the same Huawei wireless router, I can stream a couple of WebFIPs just fine using the default port 8080.

I eventually managed to fix the problem with WebFIPs. I am writing the solution here in case someone needs it.

On the computer where Lorby Axis and Ohs is running:
- do not disable Windows firewall;
- open WebFIPs port (default 8080) in Windows Firewall (TCP protocol) for all applications, not only for Axis and Ohs.

There is no need to open the port in the router, which makes sense since it is a local connection. However, the problem was that by deactivating the firewall the port remains closed (strange) and that it was not enough to open the port just for Axis and Ohs.