EumetCastViewer crashes
|
Hartmut Schulla
Hi folks!
I downloaded and installed EumetCastViewer 64Bit from Github on Win10 64bit. It crashes immediatly after the start on both machines (Server2008r2 64Bit and WIN10 64Bit). There is one message: „Need the Sentinel-3 TLEs“ before the crash. An very early old version runs smoothly. The Application Error Log shows the following:
Name der fehlerhaften Anwendung: EUMETCastView.exe, Version: 0.0.0.0, Zeitstempel: 0x61a8d143 Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000000000 ID des fehlerhaften Prozesses: 0x4858 Startzeit der fehlerhaften Anwendung: 0x01d8053eb30a5d48 Pfad der fehlerhaften Anwendung: D:\Tools\DeployEUMETCastView\EUMETCastView.exe Pfad des fehlerhaften Moduls: unknown Berichtskennung: 2ae2e7f7-7132-11ec-b750-ffffffffffff
Any idea?
Regards Hartmut
Von: MSG-1@groups.io <MSG-1@groups.io>
Im Auftrag von Philip Robinson
Ernst Please dont give up on me. I have sorted it all out i hope I have not gone out today to try and get my head around this and it all boiled down to something incredibly simple. i knew it would be. when i right clicked on my properties icon on all my Tellicast icons the target was still to my C: drive. So obviously I have now altered all the targets to D:drive. So a lot of the work i was editing in my D: drive clients folders was a waste of time. I then had to go through all my cast-client.ini files and do some very careful editing of them to ensure i had all the correct interfaces and target paths because they were now messed up. Restarted all my clients again and hey presto EVERYTHING IS WHERE IT SHOULD BE and it works. I am receiving all my HVS-2, HVS-1 and BAS files and the logs are where they should be. Davids programmes seem to be fine. As Ernst said it was a mess. I dont want to know what "Wer nicht hören will muss fühlen!" means but I feel its not pleasant i am off to a dark room now regards Philip
Just double checked and all is good. "Those who refuse to follow rules shall feel the consequences". Too right.
------ Original Message ------
From: "Ernst Lobsiger via groups.io" <ernst.lobsiger@...> To: MSG-1@groups.io Sent: 08/01/2022 11:10:00 Subject: Re: [MSG-1] FY-3D
|
||
|
|
||
|
Hugo
Hi Hartmut,
Just after the pop-screen "Need the Sentinel-3 TLEs", you can add at least the TLE file "weather.txt" to EUMETCastView. There is already an old "weather.txt" in the distribution. For that you click the button "Add TLE File" in the "Satellite Setup" screen. It is not necessary to select one of the satellite entries in that file. To update that file just click the "Update TLE's" button. Regards, Hugo
|
||
|
|
||
|
Hugo
Hartmut,
Another thing, the program shouldn't crash for missing the TLE files. Do you have OpenGL on Windows machines ? grts, Hugo
|
||
|
|
||
|
Hartmut Schulla
Hi! I think, OpenGL ist active, because I use Nvidia Graphics Card. H.
Von: MSG-1@groups.io <MSG-1@groups.io>
Im Auftrag von Hugo
Hartmut,
|
||
|
|
||
|
Hugo
Hartmut,
I found the following on error code 0xc0000005....(https://www.stellarinfo.com/blog/how-to-fix-error-code-0xc0000005-in-windows/) Probably some missing or corrupted dll's ? grts, Hugo
|
||
|
|
||
|
Hartmut Schulla
Hi Hugo! OK! But on 2 different Machines with completely different operation systems (WIN10, Server2008r2) and different HW? As I posted, an „ancient“ version runs. Regards Hartmut
Von: MSG-1@groups.io <MSG-1@groups.io>
Im Auftrag von Hugo
Hartmut,
|
||
|
|
||
|
Hugo
Harmut,
EUMETCastView is written in the Qt API . The dll's included in the zip file are the ones that are needed to run the software.Do not use dll's that are from an older version. Use a new directory when you unzip the files. The program will look first for dll's in the working directory. I tested the program on 3 different systems, but not on a server :). And of course there are other users that installed the latest version on their system .... grts, Hugo
|
||
|
|
||
|
Hartmut Schulla
Hi! It’s amazing! Today, EumetcastView runs on all machines (Server2008r2 (Win7) 64Bit and Win10 64Bit). It seems there were some DLLs loaded from an old Version. I think, reboot was the solution. Regards Hartmut
Von: MSG-1@groups.io <MSG-1@groups.io>
Im Auftrag von Hugo
Harmut,
|
||
|
|
