locked V2.16.17 crashes after logging in HRD 6.7.0.323


DM1TS Torsten
 

Hi,
I had to do a complete change of my HAM software to a new PC. This worked well thanks to the backup options. Here runs now WSJT-X in V2.3.0, in addition JTALERT in V2.16.17 and HRD in V6.7.0.323.
As soon as I have made a QSO in WSJT-X the log window pops up and I confirm the log entry. HRD reports immediately afterwards that the QSO is also there in the log, I see the entry also immediately. At this moment JTALERT terminates without warning or indication of an error. This happens after every QSO. In the event log of Windows I find the following information:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-02-05T18:01:01.2573443Z" />
<EventRecordID>723</ EventRecordID>
<Correlation>
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</channel>.
<Computer>DESKTOP-9VEL535</Computer>
<Security>
</system>
- <EventData>
<Data>JTAlert.exe</Data>
<Data>2.16.17.0</Data>
<Data>5fcaecfc</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>05429b70</Data>
<Data>3834</Data>
<Data>01d6fbe80bcf1895</Data>
<Data>C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe</Data>
<Data>unknown</Data>
<Data>bee78c8a-bb85-41a7-9fc8-dd6c7df6da1b</Data>
<Data>
<Data>
</EventData>
</Event>

Is there any idea for this, unfortunately I can't work anymore.

73 de Torsten
DM1TS, JO61OB

Join Support@HamApps.groups.io to automatically receive all group messages.