This forum is no longer active. Reference only.

Coming week our DFN-ATC-er and me will fly a session and test ESJSF2018.

Perhaps is it an idea to make it visible which version of ESJSF2018 is used f.e. ESJSF2018 v2.1.0.0 and also let it know in the download and also a small manual.

We don't expect any (big) problems bus I'll let you know how the test session has been and when

the DutchFlightNetwork.nl has been transfered to the new programs

Regards

Hans

jopie_60 wrote:Coming week our DFN-ATC-er and me will fly a session and test ESJSF2018.

Perhaps is it an idea to make it visible which version of ESJSF2018 is used f.e. ESJSF2018 v2.1.0.0 and also let it know in the download and also a small manual.

We don't expect any (big) problems bus I'll let you know how the test session has been and when

the DutchFlightNetwork.nl has been transfered to the new programs

Regards

Hans

The latest version is always available from the download link in the first post.
I won't be updating it further as it works now and nothing more is needed.
The only exception is if something that makes the program unusable is found, then I would correct it and release a newer version.

I'm not sure a manual is needed as the tick boxes seem self explanatory?

The first post of this thread does provide basic connection instructions.

Last week we have done the last testing

There is difference between the flightplan (F6) generated by FSInn and JoinFS - ESJSF2018.

In the displayed flightplan generated by JoinFS -ESJSF2018 we missing the waypoints and the flightlevel, see screendumbs.

I'm not able to look in the whazzup.txt generated by FSInn to see is there any difference, I'll try to contact our servermanager and let tou know as soon as possible.

Regards

Hans

jopie_60 wrote:Last week we have done the last testing

There is difference between the flightplan (F6) generated by FSInn and JoinFS - ESJSF2018.

In the displayed flightplan generated by JoinFS -ESJSF2018 we missing the waypoints and the flightlevel, see screendumbs.

I'm not able to look in the whazzup.txt generated by FSInn to see is there any difference, I'll try to contact our servermanager and let tou know as soon as possible.

Regards

Hans

Hi Hans,

The ESJFS tools can only add the data that is available.

The flight plan Waypoints and Flight Level are not output from JoinFS at the moment.
Because of this Flight Level will be the current level the aircraft is at and the destination will display in the waypoints section.

Hope that helps.

DutchFlightNetwork is about to make a switch from FSInn-vPilot to JoinFS - ESJFS2018
However, with the implementation of ESJFS2018 v2.1.0.0, the following problem may occur, for example that ESJFS2018 may not start up on some machines.

The startup of ESJFS2018 on my desktop and some others works without problems, however, if I want to start the same version on my laptop, a report.wer and a crash dump are generated.

In the past, ESJFS2018 has run normally on my laptop.

On my desktop and laptop are windows version and the framework versions are equal to each others.

Two colleagues DFN-er have no problems while 2 others can not lauch ESJFS2018 either.

Is this problem known or is a solution for this

Regards

Hans

content report.wer

Version=1
EventType=CLR20r3
EventTime=131832140204641578
ReportType=2
Consent=1
UploadTime=131832140214235360
ReportStatus=268435456
ReportIdentifier=f4f1415e-6ae0-444b-b04d-164f5872a3c1
IntegratorReportIdentifier=22930ac9-d71b-4d57-ae3f-9c20a318d96b
Wow64Host=34404
Wow64Guest=332
NsAppName=ESJFS2018.exe
OriginalFilename=ESJFS2018.exe
AppSessionGuid=00003218-0004-002a-c694-bc0ba25cd401
TargetAppId=W:000634bfb638ae261318c35de239646090fe00000000!00007c7d8d32b9dd515d3e99f8acb444ae4f8b258a7a!ESJFS2018.exe
TargetAppVer=2018//05//21:19:09:07!0!ESJFS2018.exe
BootId=4294967295
ServiceSplit=14
TargetAsId=3879
IsFatal=1
Response.BucketId=fc5a83c38cacc5a96c61c8253c6f560e
Response.BucketTable=5
Response.LegacyBucketId=2045135768056190478
Response.type=4
Sig[0].Name=Probleemhandtekening 01
Sig[0].Value=ESJFS2018.exe
Sig[1].Name=Probleemhandtekening 02
Sig[1].Value=2.1.0.0
Sig[2].Name=Probleemhandtekening 03
Sig[2].Value=5b031953
Sig[3].Name=Probleemhandtekening 04
Sig[3].Value=ESJFS2018
Sig[4].Name=Probleemhandtekening 05
Sig[4].Value=2.1.0.0
Sig[5].Name=Probleemhandtekening 06
Sig[5].Value=5b031953
Sig[6].Name=Probleemhandtekening 07
Sig[6].Value=87
Sig[7].Name=Probleemhandtekening 08
Sig[7].Value=e
Sig[8].Name=Probleemhandtekening 09
Sig[8].Value=System.IO.FileLoadException
DynamicSig[1].Name=Versie van besturingssysteem
DynamicSig[1].Value=10.0.17134.2.0.0.768.101
DynamicSig[2].Name=Landinstelling-id
DynamicSig[2].Value=1043
DynamicSig[22].Name=Aanvullende informatie 1
DynamicSig[22].Value=2beb
DynamicSig[23].Name=Aanvullende informatie 2
DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46
DynamicSig[24].Name=Aanvullende informatie 3
DynamicSig[24].Value=b1f0
DynamicSig[25].Name=Aanvullende informatie 4
DynamicSig[25].Value=b1f0b380dbcd74b72a4df4e63607c2ae
UI[2]=C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\ESJFS2018.exe
LoadedModule[0]=C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\ESJFS2018.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNEL32.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\apphelp.dll
LoadedModule[6]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[7]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\System32\sechost.dll
LoadedModule[9]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[10]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[11]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[12]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[13]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[14]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[15]=C:\WINDOWS\System32\combase.dll
LoadedModule[16]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[17]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[18]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[19]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[20]=C:\WINDOWS\System32\USER32.dll
LoadedModule[21]=C:\WINDOWS\System32\win32u.dll
LoadedModule[22]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[23]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[25]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[27]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\399032397425364b053c532bbbeacc09\mscorlib.ni.dll
LoadedModule[28]=C:\WINDOWS\System32\ole32.dll
LoadedModule[29]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[30]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[31]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[32]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\6e52f5ddc8a0027c55a2c15df97d50a9\System.ni.dll
LoadedModule[33]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\aaa6eb8944c45fec21964e09ea5d8904\System.Drawing.ni.dll
LoadedModule[34]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\ff99a9d58626979ee9a1e49e9cb7f8c5\System.Windows.Forms.ni.dll
LoadedModule[35]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\2d2bc5d43039ac23595b27676dcfcd3b\System.Core.ni.dll
LoadedModule[36]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\ce7b3ccf1b67903e135f62bd847db8dc\System.Configuration.ni.dll
LoadedModule[37]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\536177f34c4c0eeb95bcccd76ca90847\System.Xml.ni.dll
LoadedModule[38]=C:\WINDOWS\System32\shell32.dll
LoadedModule[39]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[40]=C:\WINDOWS\System32\shcore.dll
LoadedModule[41]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[42]=C:\WINDOWS\System32\profapi.dll
LoadedModule[43]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[44]=C:\WINDOWS\System32\FLTLIB.DLL
LoadedModule[45]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[47]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[48]=C:\WINDOWS\System32\ws2_32.dll
LoadedModule[49]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\wldp.dll
LoadedModule[51]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[52]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[53]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[54]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=285
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1043
OsInfo[7].Key=geoid
OsInfo[7].Value=176
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=131177
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.285.17134.0-11.0.85
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=8082
OsInfo[19].Key=svolsz
OsInfo[19].Value=868
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.285.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[30].Value=5f17aaf3-a675-41fe-91df-9dcdccde4c34
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Werkt niet meer
ConsentKey=CLR20r3
AppName=ESJFS2018
AppPath=C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\ESJFS2018.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=E089C84DDE184E0731F34472923C4773
MetadataHash=-1056840896

I'm not near my PC at the moment.
But a quick look at that report seems to point to your version of .net.

Off the top of my head I think I wrote ESJFS with .net 4.5.

Try running Windows update and/or installing the latest .net currently 4.7.2.

Thank you for the quick response.

As written, the two installations of both my desktop and the laptop are the same. The same windows versions, the same Bitdefender Security. The same version of framework was installed on both computers (4.7.2 windows update April 10).
On my laptop I have removed Bitdefender as an ultimate attempt and when I start ESJFS2018 the hourglass disappears within a few moments.
A new report is generated in the Microsoft / Windows / WER / folder.
I have no idea what to look for to solve this problem, especially since ESJFS2018 does not want to run on two of our three ATCs.
If desired, I want to copy and paste the last report.wer.

Regards

Hans

I have some time later today and will be controlling on JoinFS using SIMCOM X for comms.

So I'll investigate this further.
Something that stands out from your log above is

Sig[8].Value=System.IO.FileLoadException

This means the app is trying to read a file that isn't there.

Have you you got a whazzup.txt file in your JoinFS folder?
C:\Users\jopie\AppData\Local\JoinFS

If you have...

What files do you have in
C:\Users\jopie\Desktop\JFS_ES\ESJFS2018_v2.1.0.0\

the content of the first lines op the whazzup.txt is
!GENERAL
VERSION = 1
RELOAD = 1
UPDATE = 20181006133121
CONNECTED CLIENTS = 1
CONNECTED SERVERS = 40
!CLIENTS
EHAM_TWR:EuroScope Hans U.:EuroScope Hans U.:ATC:122.800:52,3086128234863:4,76388883590698:0:0::::::::::4:40:::::::::::::::::::::::::::
!SERVERS
following with serverals servers.

The map contents:
esjfs2018.exe
ESJFS2018.exe.config
contents
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup></configuration>

METAR.txt
contents
$ARJoinFS:EGCC_APP:METAR:EGCC 031020Z AUTO 23010KT 190V260 9999 BKN033 12/04 Q1018 NOSIG

regards
Hans

I will investigate this properly in a few hours.

Until then I wonder if it's because you have a . After your username?

EHAM_TWR:EuroScope Hans U.

In my long career as an ITC man, since 1980, I learned that all problems are eventually solved.
Unfortunately, removing the "dot" did not bring any relief.
I am very grateful to you for the many efforts you have done and done for us.
Regards
Hans

I'll see if I can replicate the issue shortly.

Until then..
Maybe you can compare the files you have in the 2 folders mentioned above, with the files of somebody that has this working.

Im confident it should be an easy fix, once we find the issue.

The strange thing about the whole thing is that in the past ESJFS2018 ran on my laptop without any problems as easily as at the moment of my desktop.
I copied the files 1 to 1 to the laptop, unfortunately .......

I think the problem is deeper in Windows.

With the tool EasyClean I regularly cleaned the registers.

Tomorrow or the day after tomorrow I will put back a parents image of the made laptop and see if everything goes "normal" again.
I'll keep you informed

Have a nice weekend

regards

Hans

I wouldnt mess about too much with windows if everything else works.

ESJFS does not install anything.
It just needs 2 files to work.
1. ESJFS2018.exe
2. ESJFS2018.exe.config

There will be a registry entry for it once it is run, as with all programs.

I would try the following..
1. Delete the ESJFS folder and everything in it.
2. Run your registry cleaner (Ccleaner or similar).
3. Download ESJFS2018 again.
4. Extract to your desktop.
5. Try and run the app again.

I think this is an error reading a file.
This could be a file permission error (unlikely but possible) or more likely the file it's trying to read isn't there at all.
For Example the Latest MET file is downloaded from the internet.
I'm not sure if I added a check if that failed.

I'll perform some testing shortly.

I can't replicate it Jopie_60.

So I'm going to add an error message box which will pop up when there's an issue opening the app.

That should then tell us why you're having issues.

I'll post it here shortly.

I've uploaded a new version V2.1.01

This version is the same as the previous version, only it now logs errors in a log file.
The log file is situated in the same folder the app was started from.

A message box should also appear if the program fails to load for what ever reason.

Good morning,
Good news, bad news.
What have I done?
Everything removed with the help of REGEDIT from ESJFS2018 and Bitdefender.
Reboot laptop and a new download from ESJFS2018.
After installation of ESJFS2018 launch as admin.
This time the hourglass did not disappear after a few seconds but an error message appeared on my screen.
ESJFS2018 has to run stand-alone in combination with JoinFS and Euroscope, therefore WITHOUT a flight simulator.
Perhaps you can let your light shine on this.
I suspect that the disappearance of the hourglass after a few seconds lay in one of Bitdefender's registers and that they were not cleaned.

Succces and regards

Hans It's inpossible to upload the error.txt file, so I send a .jpg from the error

Ah haaa!

It's looking for Simconnect on load for some reason.

I've just removed simconnect from my system and got the same error, great.

You'll need to give me some time to look over the code and change a few things.

Until then you can install Simconnect Only with no need to install the whole simulator.

Simconnect Download.

Just run the SimConnect.msi installer in the XPACK folder to install SimConnect.

Together we are strong but above all patient.
This almost reminds me of 40 years ago:
Try and error.
I always found the worst when I could not reproduce an error.
Good luck