Swisslog updated 01/13/25 now I get 10022 invalid argument

[W1SPS]

My database updated around 01/13/25 now I get 10022: [10022] invalid argument. And now that I get that error it no longer talks to gridtracker. Prior to this update my SunSDR2DX running WSJT-X, JtAlert, Gridtracker, ans Swisslog were running perfectly. But without Swisslog working properly gridtracker in particular doesn't work and neither does the logging on Swisslog.

Hope there's a solution.

73
Rich W1SPS

[EA3GCV]

Hi Rich,

Are you using latest Swislsog version? What do you mean when you explain that you database was updated around 01/13/25? Do you mean that you updated the statistic database or the country table? When do you get exactly this error meesage? I need to know more details to try to know the source of this issue.

Could you log any QSO manually into Swisslog? If QSOs from WSJT-X are not being logged in Swisslog seems a communication issue. I would need to see the UDP configuration you use in all these programs to see the data flow and UDP port chain you use. Please send me screenshots to support@swisslogforwindows.com. But if the UDP port configuration is properly done it should work well. It's very importat you add exceptions to all these programs in your firewall to avoid blockings.

73

[W1SPS]

Hi Rich,

Are you using latest Swislsog version? What do you mean when you explain that you database was updated around 01/13/25? Do you mean that you updated the statistic database or the country table? When do you get exactly this error meesage? I need to know more details to try to know the source of this issue.

Could you log any QSO manually into Swisslog? If QSOs from WSJT-X are not being logged in Swisslog seems a communication issue. I would need to see the UDP configuration you use in all these programs to see the data flow and UDP port chain you use. Please send me screenshots to support@swisslogforwindows.com. But if the UDP port configuration is properly done it should work well. It's very importat you add exceptions to all these programs in your firewall to avoid blockings.

73

Hey there,
Yes newest version. In fact I downloaded the newest install and ran it hoping it would maybe fix something that may have gotten corrupted. It didn't work. The error comes up just as the program is finishing starting up, like just at the moment the program is ready to wait for info. I don't remember the exact message. It said swisslog had to update something and would re-start. After that I got the 10022 message and gridtracker no longer worked right and no one I contacted would log.
I changed several UDP settings between the programs like a dope and now I have no Idea where I am. But I fear if I cant fix the 10022 error on swiss log (which happened before I changed anything) it won't matter what I do.

[EA3GCV]

Hi,

This error seems to come from a communication error due to a wrong UDP port assignment. If you send me screenshots of the udp configuration of Swisslog and other programs I will be able to see what may happen. You are linking many programs and UDP settings must be done well. Remember you can't share an UDP port so you need to broadcast info into another port. Here an example:

WSJT-X sending at port 2237
Gridtracker receiving at port 2237 then broadcast into 2332
Swisslog receiving at port 2332 (enable broadcast into another different port if needed)

Otherwise contact me via whatsapp to arrange a remote session through Teamviewer or Anydesk to see online what may happen. You can see my number in the Contact section of the website.