Jump to content
The simFlight Network Forums
Sign in to follow this  
Kulbit

BETA Update V4.2.2018.26800 Client failed start...

Recommended Posts

Hi Simon,

after updating at STB Client BETA Update V4.2.2018.26800 for Prepar3D-V4.2 and V4.3 ,

the Client itself failed to start  without any error message..

I simply applied the update on the existing version but now it refuse to start.

What's wrong? How can I solve the problem ?

 Do I have to delete the program and reinstall from the beginning adding the update?

 

Many thanks for the help !!

Share this post


Link to post
Share on other sites

I don't think this is a problem with how the update was installed, but something else.

Can you check Windows event viewer please?  This is where error messages go now when STB fails before I get control to do anything useful.  It's usually a Windows or evnironment issue.

Thanks

Simon

Share this post


Link to post
Share on other sites

Simon,

Here the event viewer report...

please let me know if you need a translation from Italian...

 

Thanks

Max

 

1.jpg

2.jpg

Share this post


Link to post
Share on other sites

This is a new one....

Can you visit your STB Install folder, find "Utilities.dll", right click and tell me what it says please on the "Details" tab?

Also do you have Utilities.pdb in that folder also?

Thanks

Simon

Share this post


Link to post
Share on other sites

Thanks - your DLL appears to be correct.  Still not clear why this is happening, the Microsoft help for these exceptions talks in very vague terms.  Maybe next I'll try adding some debug code to help.

Thanks

Simon

Share this post


Link to post
Share on other sites

Thanks anyway Simon !!

I will try to re-install base program and update.

 

BTW if it could be of any help this is the full Windows Error Reporting :

Version=1
EventType=CLR20r3
EventTime=131866694928047123
ReportType=2
Consent=1
UploadTime=131866694929134216
ReportStatus=268435456
ReportIdentifier=7556f07e-2c2e-4517-94ca-e9525643544a
IntegratorReportIdentifier=7f7dcdaf-7e60-4c74-bc32-3914fc3a6925
Wow64Host=34404
NsAppName=TrafficBoardFrontEnd.exe
OriginalFilename=TrafficBoardFrontEnd.exe
AppSessionGuid=00003e44-0002-0044-5ace-ca740f7cd401
TargetAppId=W:0006bbb3e878d86cfdbd3300ad3be214cc5300000000!0000bd859cc746f310f4d20407a22df293777f28789d!TrafficBoardFrontEnd.exe
TargetAppVer=2018//09//25:19:25:01!0!TrafficBoardFrontEnd.exe
BootId=4294967295
TargetAsId=1408
IsFatal=1
Response.BucketId=5f8b711a72f83b592ad79bdc54ad5c19
Response.BucketTable=5
Response.LegacyBucketId=1934185935594675225
Response.type=4
Sig[0].Name=Firma problema 01
Sig[0].Value=TrafficBoardFrontEnd.exe
Sig[1].Name=Firma problema 02
Sig[1].Value=4.2.2018.13500
Sig[2].Name=Firma problema 03
Sig[2].Value=5baa8b8d
Sig[3].Name=Firma problema 04
Sig[3].Value=Utilities
Sig[4].Name=Firma problema 05
Sig[4].Value=4.2.2018.23800
Sig[5].Name=Firma problema 06
Sig[5].Value=5b823c90
Sig[6].Name=Firma problema 07
Sig[6].Value=fc
Sig[7].Name=Firma problema 08
Sig[7].Value=0
Sig[8].Name=Firma problema 09
Sig[8].Value=System.TypeLoadException
DynamicSig[1].Name=Versione SO
DynamicSig[1].Value=10.0.17134.2.0.0.256.48
DynamicSig[2].Name=ID impostazioni locali
DynamicSig[2].Value=1040
DynamicSig[22].Name=Informazioni aggiuntive 1
DynamicSig[22].Value=2c71
DynamicSig[23].Name=Ulteriori informazioni 2
DynamicSig[23].Value=2c717fdbb00716c893a6788ec1e1a043
DynamicSig[24].Name=Ulteriori informazioni 3
DynamicSig[24].Value=7c7b
DynamicSig[25].Name=Ulteriori informazioni 4
DynamicSig[25].Value=7c7b81e32a3f598b3bda119b30ddcf95
UI[2]=E:\FlyingWSimulation\SuperTrafficBoard Client V4 for Prepar3D-V4\TrafficBoardFrontEnd.exe
LoadedModule[0]=E:\FlyingWSimulation\SuperTrafficBoard Client V4 for Prepar3D-V4\TrafficBoardFrontEnd.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\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[11]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[12]=C:\WINDOWS\System32\combase.dll
LoadedModule[13]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[14]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[15]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[16]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[17]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[18]=C:\WINDOWS\System32\USER32.dll
LoadedModule[19]=C:\WINDOWS\System32\win32u.dll
LoadedModule[20]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[21]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[23]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[25]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\a6021ef6892ab519b334a17992542017\mscorlib.ni.dll
LoadedModule[26]=C:\WINDOWS\System32\ole32.dll
LoadedModule[27]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[28]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[29]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\8ff4bf965a60a85a0598226bf67e993a\System.ni.dll
LoadedModule[30]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Drawing\d56a87ba57efe8f63335298ab1cb8772\System.Drawing.ni.dll
LoadedModule[31]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\a8f8eef9e281ad0ac06dc269147ae72c\System.Windows.Forms.ni.dll
LoadedModule[32]=C:\Windows\Microsoft.NET\Framework64\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=407
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1040
OsInfo[7].Key=geoid
OsInfo[7].Value=118
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
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=257266
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.407.17134.0-11.0.95
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16314
OsInfo[19].Key=svolsz
OsInfo[19].Value=464
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.407.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[30].Value=F8EE1E09-5379-44DF-B86D-E49E70CBE43B.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:1679
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Ha smesso di funzionare
ConsentKey=CLR20r3
AppName=STBClientFrontEnd
AppPath=E:\FlyingWSimulation\SuperTrafficBoard Client V4 for Prepar3D-V4\TrafficBoardFrontEnd.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=85F2B163A638B6C6F6425E1CBEE08C21
MetadataHash=-1491954143

Share this post


Link to post
Share on other sites

This one is hard to debug, because I can't reproduce it and it happens so early in the life of STB the framework adds little value to the exception.

Can you also check the messages.dll and simulator.dll, and provide the same information as you did earlier for utilities.dll?

Thanks
Simon

Share this post


Link to post
Share on other sites

Simon,

this is it...  BTW even after a full vanilla reinstallation of STB plus the upgrade I've got the same. Clients don't start....

 

message.jpg

simulator.jpg

Share this post


Link to post
Share on other sites

The real challenge here is there is so little information (thanks Microsoft) about the actual cause, it could actually be many things.  What was the version number that last worked for you?  I can do a code comparison, but FileHelper (which is active at the time of the problem) hasn't changed much at all lately.

Simon

Share this post


Link to post
Share on other sites

The next beta will have some code to better detect this kind of error.  Meanwhile there's only been one report of this problem so far.

 

Simon

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.