c141fe Posted July 5, 2018 Share Posted July 5, 2018 Get error message regarding NATS "Could not parse NATS tracks due to: An item with the same key has already been added." 1. updated Navigraph data to 1807 2. ran DbBuilder 3. started EFB2 Server 4. started EFB2 Client 5. checked "Use Organized Track Systems (NAT,... 6. clicked Apply 7. Got the following 2018-07-04 23:19:18.727 Debug : Start downloading AUSOTs data 2018-07-04 23:19:18.727 Debug : Start downloading NAT data 2018-07-04 23:19:18.728 Debug : Start downloading PACOT data 2018-07-04 23:19:19.138 Debug : NAT data download complete 2018-07-04 23:19:19.248 Debug : PACOT data download complete 2018-07-04 23:19:20.442 Debug : AUSOTs data download complete 2018-07-04 23:19:20.608 Error : Could not parse NATS tracks due to: An item with the same key has already been added. Confirmed the 3 html files are present in .../Documents\AivlaSoft\EFB2\Server\Downloads Current UTC is July 5, 2018 @ 0625. There are several Eastbound NATs valid at this time so they should be appearing. Have completely uninstalled and then reinstalled EFB2 with same results. Running Windows 10 64-bit P3Dv4.3 Windows Defender AV EFBv2 Server=2.0.52.0 Client=2.0.70.0 Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted July 5, 2018 Share Posted July 5, 2018 Yes, I can confirm the same issue here. I have however run Server Build #52 already yesterday and no such warning appeared. We have to wait until investigating further. It has happened in the past already a few times that the NAT track server had a "hickup" delivering wrong data for some period. The last valid NAT track download I received with Build #52 was 5th of July, at 00:55. Quote Link to comment Share on other sites More sharing options...
Jason Posted July 5, 2018 Share Posted July 5, 2018 I'm also getting the same error message, very strange as this wasn't happening with the previous version. Hopefully they'll be able to find a solution. Thanks Jason Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted July 5, 2018 Share Posted July 5, 2018 We found the reason: for no apparent reason the NAT tracks were issued twice today! We will nevertheless introduce countermeasures for that. Who knows how many times this can and will happen (I've never seen that before though). This issue will be addressed with the next update. Quote Link to comment Share on other sites More sharing options...
alpha117 Posted July 5, 2018 Share Posted July 5, 2018 How many time a day did you think NATS were issued? Typically, the time of publication of the daytime (westbound) OTS is 2200 UTC and of the night-time (eastbound) OTS is 1400 UTC. Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted July 5, 2018 Share Posted July 5, 2018 4 hours ago, alpha117 said: How many time a day did you think NATS were issued? Typically, the time of publication of the daytime (westbound) OTS is 2200 UTC and of the night-time (eastbound) OTS is 1400 UTC. Oh come on, we are aware of that! They were issueing twice the same tracks!! (allow me to write this a bit bigger and more emphasized...) We may be stupid, but not THAT stupid! Edit: Ok, I can reduce the fontsize again. The impact created was as expected...? Quote Link to comment Share on other sites More sharing options...
alpha117 Posted July 5, 2018 Share Posted July 5, 2018 ..issuing twice the same track...........now that make more sense and hence the error now than saying 'tracks were issued twice today'. If I have miss read you first post my apologies Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.