I am using Lorby Live Traffic 3_02_b06_Install_P3D_V4 in P3D v4.5 with HF3, on Windows Version 21H1 (OS Build 19043.985).

Live Traffic has worked flawlessly for me for ages.  I have been very happy with it.  But, in a recent Windows Update I noticed there was a .NET update.  Since then, Live Traffic does not start correctly.

I am getting the following error:  System.Net.WebException: The operation has timed out.

Other Lorby programs (Addon Organizer 1_55_b10 and Flashlight 1_05_b01) are working fine.

 

 

This error takes quite a while to appear (ie, it's waiting for a timeout, obviously). But, once it does appear and I click the "Continue" button, the program does appear to run.  I use the program solely to inject AI helicopters in to my sim, and, after clicking the "Continue" button, it does appear to still be doing that.  However, despite that, is it really running properly?  I also notice that despite the "Connect Automatically" check box being checked, it is no longer connecting automatically and I now need to manually press the Connect button at the top left of the program.

I tried to download and reinstall the .NET 4.8 runtime, but got a message telling me that the installation would be halted because .NET 4.8 was already installed.

I reinstalled Lorby Live Traffic. No difference. The timeout error still occurred.

I am not sure how to copy-and-paste the full error details as a <code> snippet, so I apologise for pasting it here in its entirety and, thus, the length of this post.

 

=========================================================

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.WebException: The operation has timed out
   at System.Net.HttpWebRequest.GetResponse()
   at LorbyLiveTraffic.FaaNatClient.RequestNats()
   at LorbyLiveTraffic.MainDialog.MainDialog_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

Edited May 28, 20215 yr by Lorby_SI

8 hours ago, freddy_ said:

the length of this post.

All that is needed is the stack trace at the top, I've removed the irrelevant part.

This sounds more like the web service that was providing NAT data is no longer available. The Windows update may be a conincidence. 

I will check.

Edit - no problems here. The webserivice answers just fine. Check if you can open the URL in your browser: https://www.notams.faa.gov/common/nat.html

If not, then there seems to be a network security issue on your end?

 

Edited May 28, 20215 yr by Lorby_SI

You just need to the stack trace at the top?  Noted for next time.

Yes, I can go to the following URL in my browser: https://www.notams.faa.gov/common/nat.html.

When the Windows Update occurred, there were changes to the behaviour of the Microsoft Edge browser (which I didn't ask for and did not change myself).  Therefore, your responses that "the web service that was providing NAT data is no longer available" and "there seems to be a network security issue on your end" do make sense.

Interestingly, Live Traffic is working fine today. It's loading in a timely manner with no .NET error.  Why it is working today, and not yesterday?  I can only guess that yesterday the URL was timing out, for whatever reason. Considering this, I would agree that me doing a Windows update the day before appears to be a coincidence. But, as it was the only recent "change" made to my system, I drew the conclusion that it might have been a contributing factor.  That said, the changes to Edge's behaviour, from that Windows Update, may (still) have something to do with it.

Regardless, Live Traffic is working now.  So consider this matter resolved.

If it occurs again, I now have an idea of what to look for and will (re)check the network security settings etc.  (If it occurs again consistently, and I remain unable to solve it, then I will re-post here.)

Thankyou for your response.

 

Edited May 29, 20215 yr by freddy_