logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Latest JTALERT causes Logic to crash
4x1ru
#1 Posted : Saturday, December 11, 2021 5:12:30 AM(UTC)
Rank: Member

Groups: Registered
Posts: 28
Location: Israel

Thanks: 3 times
Was thanked: 5 time(s) in 5 post(s)
Something has changed between JTALERT 2.50.7 and 2.50.8. After a QSO is concluded, logging causes Logic to crash.
After restarting Logic I can then manually use the longing window of WSJT-X to log the last QSO. This problem also
exists in all later updates to JTALERT including 2.50.9. I am currently running Logic 10.0.3 and WSJT-X 2.5.2.

Anyone else run into this.

Jim 4X1RU
Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
WN4AZY
#2 Posted : Sunday, December 12, 2021 11:25:30 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Hi--

I understand that JTAlert monitors the ADIF file created by WSJT-X, just like LOGic does. Is this correct? Then there is no connection between JTAlert, and LOGic?

Do you get an error in LOGic? What does it say? If you take JTAlert out of the picture, does LOGic and WSJT-X then work?

I am guessing that JTAlert is locking the ADIF file and not allowing LOGic or anything else to share it. I would notify the JTAlert authors if you haven't already.

Tnx & 73,

Dennis WN4AZY
4x1ru
#3 Posted : Monday, December 13, 2021 6:26:53 AM(UTC)
Rank: Member

Groups: Registered
Posts: 28
Location: Israel

Thanks: 3 times
Was thanked: 5 time(s) in 5 post(s)
Shalom Dennis,
I am uploading one image (WSJT-X Logging Error.jpg) which shows the error message received from “Logic”.
Another 2 files:
(wsjtx_log - Error.ADI) which is the file used by WSJT
(Complete - Error.ADI) which is the file used by JTAlert
There are 3 entries that are included. The first is a QSO with S01WS which was logged successfully into Logic when using JTAlert v2.50.7. The last 2 were with SQ7BCB and were not recorded in Logic when using JTAlert v2.50.8.
I am using Logic v10.0.3 and WSJT-X v2.5.2.
I hope this helps you out.

I sent the following message to VK3AMA 6/12/2021 but have not had a reply:
Shalom Laurie,

I've been trying to figure out how to use Groups.io but I don't seem to be able to "break the code" on how to use it.
I am using "Logic" logging software for many years and it have been working smoothly logging FT-8 QSO's made on WSJT-X/ JTALERT.
However, when version 2.50.8 of JTALERT was installed, LOGIC crashed when writing the log entry. It is still a problem with 2.50.9.
I remember that to get Logic to work with WSJT-X/JTALERT, some special software implementation was required on LOGIC to make it compatible.
Something changed between 2.50.7 and 2.50.8 that directly effects how LOGIC interacts with WSJT-X/JTALERT.
Do you have any idea what that could be.
73,
Jim 4X1RU
File Attachment(s):
WSJT-X Logging Error.jpg (34kb) downloaded 57 time(s).
wsjtx_log - Error.ADI (1kb) downloaded 43 time(s).
Complete - Error.ADI (2kb) downloaded 51 time(s).
1 user thanked 4x1ru for this useful post.
WN4AZY on 12/13/2021(UTC)
WN4AZY
#4 Posted : Tuesday, December 14, 2021 10:56:12 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Thanks!

Unfortunately the LOGic error doesn't tell us a lot. There might be something in the Windows event viewer.

I will install JTAlert and try to learn more. It will take a few days unfortunately.

How do the three programs interact? Why does JT-Alert have its own ADIF file? Why doesn't it use the same file that WSJT-X makes, which LOGic uses?

Tnx & 73,

Dennis WN4AZY
4x1ru
#5 Posted : Friday, February 18, 2022 8:30:30 AM(UTC)
Rank: Member

Groups: Registered
Posts: 28
Location: Israel

Thanks: 3 times
Was thanked: 5 time(s) in 5 post(s)
Latest version of JTAlert (2.50.0) no longer causes Logic to crash when logging QSO's.
Thanks,

Jim
1 user thanked 4x1ru for this useful post.
WN4AZY on 2/18/2022(UTC)
WN4AZY
#6 Posted : Friday, February 18, 2022 3:56:38 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Thanks for letting us know, Jim!

73,

Dennis WN4AZY
K8ZT
#7 Posted : Friday, February 18, 2022 5:17:12 PM(UTC)
aluscre

Rank: Advanced Member

Groups: Registered
Posts: 46
Location: Stow, OH

Thanks: 1 times
Was thanked: 8 time(s) in 8 post(s)
I tried installing latest version today- 2.51.0 and it is still crashing LOGic.
I then tried 2.50.9 and still crashes.
Back to 2.50.7 and it is not crashing
4x1ru
#8 Posted : Saturday, February 19, 2022 8:33:59 AM(UTC)
Rank: Member

Groups: Registered
Posts: 28
Location: Israel

Thanks: 3 times
Was thanked: 5 time(s) in 5 post(s)
When I first tried JTAlert 2.51.0 it worked. The next day it was the same problem again. Still not out of the deep water.

Jim
1 user thanked 4x1ru for this useful post.
WN4AZY on 2/21/2022(UTC)
4x1ru
#9 Posted : Thursday, April 7, 2022 3:22:27 AM(UTC)
Rank: Member

Groups: Registered
Posts: 28
Location: Israel

Thanks: 3 times
Was thanked: 5 time(s) in 5 post(s)
I tried using JTAlert 2.51.2 and LOGIC still crashes.
File Attachment(s):
Logic Stopped working.jpg (34kb) downloaded 49 time(s).
Restart after error.jpg (39kb) downloaded 43 time(s).
K8ZT
#10 Posted : Wednesday, April 13, 2022 2:40:14 PM(UTC)
aluscre

Rank: Advanced Member

Groups: Registered
Posts: 46
Location: Stow, OH

Thanks: 1 times
Was thanked: 8 time(s) in 8 post(s)
Newest Version 2.51.2 still causing LOGic to crash

Last version that does not cause LOGic crash appears to be 2.50.7 (which is also the last version that was downloadable as either 64 or 32 bit versions)- https://hamapps.com/JTAlert/
1 user thanked K8ZT for this useful post.
WN4AZY on 4/18/2022(UTC)
4x1ru
#11 Posted : Friday, April 22, 2022 3:24:34 AM(UTC)
Rank: Member

Groups: Registered
Posts: 28
Location: Israel

Thanks: 3 times
Was thanked: 5 time(s) in 5 post(s)
Just installed JTAlert 2.5.3 and Logic still crashes when trying to log a QSO.
1 user thanked 4x1ru for this useful post.
WN4AZY on 4/25/2022(UTC)
WN4AZY
#12 Posted : Wednesday, June 29, 2022 10:17:35 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Ok, I got around to checking this out again.

Several months ago I could reproduce the error and it showed an error in the Windows event log. However, I could not easily find any way to contact JT-Alert, and it got set aside, and life intervened.

I installed JT-Alert 2.51.5 (telling it I am using WSJT-X) and WSJT-X version 2.5.4. When I log a Q in WSJT-X, I get an error about the call not matching my partner, but LOGic logs the QSO without incident.

One other change--I am running Windows 11.

So, I will assume this is fixed until I hear differently.

Tnx & 73,

Dennis WN4AZY
K8ZT
#14 Posted : Wednesday, June 29, 2022 11:12:04 AM(UTC)
aluscre

Rank: Advanced Member

Groups: Registered
Posts: 46
Location: Stow, OH

Thanks: 1 times
Was thanked: 8 time(s) in 8 post(s)
I tried installing JT Alert (2.51.5) and it crashed LOGic as soon I tried to log a QSO.
Running LOGic 10.7 and Windows 10 here.
Reinstalled old JT Alert 2.50.7 and retried LOGic did not crash.

Here is Microsoft Event-

+ System

- Provider

[ Name] Application Hang

- EventID 1002

[ Qualifiers] 0

Version 0

Level 2

Task 101

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2022-06-29T15:54:53.2092447Z

EventRecordID 237826

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel Application

Computer aal64

Security


- EventData

LOGic.exe
10.0.7.0
37a4
01d88bd02442887e
5
C:\LOGic9\LOGic.exe
485931b1-d3ed-4526-b95e-c7c1ccb21fe2


Unknown
55006E006B006E006F0077006E0000000000




Binary data:


In Words

0000: 006E0055 006E006B 0077006F 0000006E
0010: 0000


In Bytes

0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00 o.w.n...
0010: 00 00 ..
1 user thanked K8ZT for this useful post.
WN4AZY on 6/29/2022(UTC)
K8ZT
#15 Posted : Monday, February 6, 2023 8:53:19 PM(UTC)
aluscre

Rank: Advanced Member

Groups: Registered
Posts: 46
Location: Stow, OH

Thanks: 1 times
Was thanked: 8 time(s) in 8 post(s)
I installed newest version JTAlert and it is still crashing LOGic when it tries to send a new log record.

Windows error events

Application: LOGic.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
at System.IO.__Error.WinIOError(Int32, System.String)
at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean)
at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare)
at PDA.NewRecordWatcher.Watch.OnChanged(System.IO.FileSystemEventArgs)
at PDA.FileSystemWatcher.Watcher.OnChanged(System.Object, System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.OnChanged(System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.NotifyFileSystemEventArgs(Int32, System.String)
at System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)



Faulting application name: LOGic.exe, version: 10.0.12.0, time stamp: 0x6371b6ff
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2486, time stamp: 0xca518c9d
Exception code: 0xe0434352
Fault offset: 0x0012e292
Faulting process id: 0x4ba0
Faulting application start time: 0x01d93a954a0f2291
Faulting application path: C:\LOGic9\LOGic.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 820ccaac-f038-4c7e-a389-bfc2be21eb22
Faulting package full name:
Faulting package-relative application ID:
WN4AZY
#16 Posted : Wednesday, February 8, 2023 9:46:31 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Hi--

Thanks for the info.

I checked my code.


// Windows FileSystemWatcher watches C:\Users\Dennis\AppData\Local\WSJT-X\wsjtx_log.adi. When data is added
// this is called.
using (FileStream fs = new FileStream(_fileName, FileMode.Open, FileAccess.Read, FileShare.ReadWrite))
{
// read the new data out of the file
}



It is opening the ADIF file for read-only access, and sharing for write.

Here is the documentation on FileShare.ReadWrite:
https://learn.microsoft....e?view=netframework-4.8

It says "Additional parameters may be required" but doesn't go into detail.

I suspect this is something I can't fix in LOGic. LOGic works with WSJT-X and other similar programs. It used to work with JTAlert. Is there ANY support for JTAlert? Is it open-source per chance? If we could see their code or see what they changed to break it....

Tnx & 73,

Dennis WN4AZY
WN4AZY
#17 Posted : Wednesday, February 8, 2023 9:57:08 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Got signed up for their group. Will post something later.
WN4AZY
#18 Posted : Thursday, February 9, 2023 12:53:25 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Waiting to be approved by their moderators:

Quote:
Hi--I am Dennis WN4AZY, author of the LOGic logging program. https://www.hosenose.com/

LOGic monitors the WSJT-X ADIF file to update it's own log, much as I imagine that JTAlert does. Starting with JTAlert version 2.50.8, saving a QSO in WSJT-X while JTAlert is running causes LOGic to abort with an IO error:

Application: LOGic.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
at System.IO.__Error.WinIOError(Int32, System.String)
at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean)
at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare)
at PDA.NewRecordWatcher.Watch.OnChanged(System.IO.FileSystemEventArgs)
at PDA.FileSystemWatcher.Watcher.OnChanged(System.Object, System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.OnChanged(System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.NotifyFileSystemEventArgs(Int32, System.String)
at System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Here is my code:


// Windows FileSystemWatcher watches C:\Users\Dennis\AppData\Local\WSJT-X\wsjtx_log.adi. When data is added
// this is called.

using (FileStream fs = new FileStream(_fileName, FileMode.Open, FileAccess.Read, FileShare.ReadWrite))
{
// read the new data out of the file and process it
}


What could have happened between 2.50.7 & 2.50.8 to cause the problem with LOGic? Could you check that JTAlert opens the file for shared access? Any ideas for anything I could try?

Here is the discussion if the issue on our forum.

http://hosenose.com/Foru...to-crash.aspx#post11125

Thanks in advance for your assistance.

73,

Dennis Hevener, WN4AZY
WN4AZY
#19 Posted : Thursday, February 9, 2023 5:50:21 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Here is his reply:

https://hamapps.groups.i...tid=1675610906915182128

Note that he says that he DOES read the ADIF file during startup. If that is the case, then starting JTAlert before LOGic should fix the problem. Does anyone have any ideas?

Quote:
You're mistaken. JTAlert does not open the the WSJTX adif file. All JTAlert interaction is via the WSJTX UDP interface. The only time JTAlert opens a WSJTX file for reading is during startup for a one-time read of the WSJTX config file to determine UDP settings.
NA5Q
#20 Posted : Friday, February 10, 2023 10:41:17 AM(UTC)
Rank: Member

Groups: Registered
Posts: 13
Location: Louisiana

Was thanked: 3 time(s) in 3 post(s)
Been using JTAlert and WSJTX with Logic ever since Logic could read the WSJTX log without any problems.
I run two WSJTX and JTAlerts applications with my two panadapters.
In Log Form Setup, under Auto ADIF Logging I select C:\Users\username\Appdata\Local\WSJT-X-SDR-A\wsjtx_log.adi and C:\Users\username\Appdata\Local\WSJT-X-SDR-B\wsjtx_log.adi.

But before that setup I used C:\Users\username\Appdata\Local\WSJT-X\wsjtx_log.adi running only one WSJTX application and JTAlert stand alone.

Try it!
Roland NA5Q
1 user thanked NA5Q for this useful post.
WN4AZY on 2/10/2023(UTC)
WN4AZY
#21 Posted : Thursday, April 27, 2023 4:14:43 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Man
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
K8ZT found the problem (Thank you!)

LOGic was set to monitor the JTAlert log file. This causes the error. If LOGic is set to monitor the WSJT-X log file, everything works.

In other words, when installing JTAlert, don't change anything in LOGic.

Many thanks to K8ZT!

Tnx & 73,

Dennis WN4AZY

https://hamapps.groups.io/g/Support/message/43784
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.107 seconds.