Date
1 - 17 of 17
Locked Issues with LOTW and Worked Station after upgrading to 2.5.2 #stopped_working
|
Hello, I see that I may be probably the only one with these issues of color indications after scanning through the various groups. It is a total pain to have to jump out to the web browser to check if the station uses LOTW and also to my ADIF to see if the station was worked. |
|
|
|
Dave Garber <ve3wej@...>
thats is why I prefer to keep jtalert to tell me all the info. if you installed wsjt in a different folder, or with a -rig it may have opened a new appdata folder under that name. jtalert checks my full logging program, and then colours as per what my log says, not what wsjt says, and it marks eqsl users, lotw users, and a few more items as needed maybe you were using jtalert previously, and forgot to reinstall it? Dave Garber VE3WEJ / VE3IE On Sun, Dec 12, 2021 at 2:45 AM N2BRG <n2brg@...> wrote:
|
|
|
|
Hello Dave,
Thanks for the reply. This has been a fresh install, well at least twice now, I backed up my ADIF and placed it in the proper folder along with placing the LOTW file (manually downloaded) in the Logs folder as suggested by many. I rather not have to run other software to do what I thought the latest WSJT-x would do. A couple of versions ago I was able to get it all working along with a Black BG with White FG for worked stations. I do not remember how I did that. Usually, I make notes on some setups. After the latest install, again after purging existing installs, I can not get LOTW to show or Worked stations as stated in my earlier posts. I'll take another shot with a fresh install after another purge. Gary Euler N2BRG |
|
|
|
Reino Talarmo
A couple of versions ago I was able to get it all working along with a Black BG with White FG for worked stations. I do not remember how I did that. Usually, I make notes on some setups. After the latest install, again after purging existing installs, I can not get LOTW to show or Worked stations as stated in my earlier posts. I'll take another shot with a fresh install after another purge.Hi Gary, It seems to be at least partially a colors setting issue. Go to File | Settings | Colors and right click on the CQ in message line. That bring a menu and click on the Foreground color... line and select while color and hit OK. Do the same for Background color and select black for it. You may need to do the same for the LoTW User color settings. That should help, if wsjt_log.adi file is there. You may try to press Rescan ADIF log to see whether on the bottom line of the main window you will see for a short time how many worked before station are in the ADIF file. 73, Reino OH3mA |
|
|
|
Another fresh Install and still no go. Guess I will do without. I am not about to install other programs to do what is set to do in the program.
|
|
|
|
Jay Lijoi
I have the same issue with new install.
Something is not right. |
|
|
|
Jay Lijoi
Ok, operator error on my part. Didn't see the check box in General settings for "...worked before status."
Again all I ... well, most is right in the world. 🙂 |
|
|
|
Hello Reino,
I tried that and the issue is still there with the latest version. I think the main issues are that the LoTW CSV and or ADIF files are not being read for the Worked and LoTW. I think I may have just run out of options here. It is not an option here to be running other programs to fix an issue that may be in the latest versions of WSJT-x. Microsoft Windows 10 is probably contributing to the issue too when it just does not allow SSL/TSL, but again, I have downloaded that manually and placed it in the proper folders. Thank you for your suggestions, Gary, N2BRG P.S. Jay, been there and done that some time ago. That is the first thing I check during a fresh setup. |
|
|
|
Joe Subich, W4TV
Microsoft Windows 10 is probably contributing to the issue too when it just does not allow SSL/TSL,Nonsense. Follow the instructions in the WSJTX on-line help files to download/install the necessary Open SSL libraries and make sure your Windows firewall allows access for WSJT-X. 73, ... Joe, W4TV On 2021-12-20 11:09 AM, N2BRG wrote: Hello Reino, |
|
|
|
Ken
Joe et al,
toggle quoted message
Show quoted text
I have the same problem. I am running WSJT-X V2.5.2 on Windows 10. I just installed Win64 Open SSL and Microsoft VC++ on my Windows 10 PC. The installation said it was successful, but I still get the Network error - SSL/TLS support not installed error when I try to Fetch the Users CSV file. On my main PC in the shack, I am running WSJT-X V2.5.3 on Windows 7 Pro and it seems to work fine with no network error messages, Do I need to upgrade to WSJT-X v2.5.3 on the Windows 10 system ? Why does Microsoft keep F____ up things that work when they upgrade to a new version of Windows ? Ken - W8KEN On 12/20/2021 11:22 AM, Joe Subich, W4TV wrote:
Microsoft Windows 10 is probably contributing to the issue too when it just does not allow SSL/TSL,Nonsense. Follow the instructions in the WSJTX on-line help files to |
|
|
|
Mike Black
There's a 32-bit and 64-bit version of SSL.Did you load the correct one?
toggle quoted message
Show quoted text
Mike W9MDB On Monday, December 20, 2021, 11:30:19 AM CST, Ken via groups.io <w8ken@...> wrote:
Joe et al, I have the same problem. I am running WSJT-X V2.5.2 on Windows 10. I just installed Win64 Open SSL and Microsoft VC++ on my Windows 10 PC. The installation said it was successful, but I still get the Network error - SSL/TLS support not installed error when I try to Fetch the Users CSV file. On my main PC in the shack, I am running WSJT-X V2.5.3 on Windows 7 Pro and it seems to work fine with no network error messages, Do I need to upgrade to WSJT-X v2.5.3 on the Windows 10 system ? Why does Microsoft keep F____ up things that work when they upgrade to a new version of Windows ? Ken - W8KEN On 12/20/2021 11:22 AM, Joe Subich, W4TV wrote: Microsoft Windows 10 is probably contributing to the issue too whenNonsense. Follow the instructions in the WSJTX on-line help files to |
|
|
|
Ken
Don’t know. I have a 64 bit operating system so I loaded the 64 bit version.
toggle quoted message
Show quoted text
Does WSJT-X require the 32 bit version ? W8KEN - Ken On Dec 20, 2021, at 12:34, Michael Black via groups.io <mdblack98@...> wrote: |
|
|
|
Joe Subich, W4TV
Mike,
toggle quoted message
Show quoted text
Interesting ... I have had no issues on my Windows 10 Pro system but tried Windows 10 Home (on my laptop) and the LotW user list update failed there. Both are 64 bit systems ... Both are 21H1, build 19043.1415 Both have Windows Feature Experience Pack 120-2212.3920.0 Both have the current Open SSL 64 bit libraries installed. Both are running WSJTX 2.5.3 (64 bit) Now, where to look for differences (a cursory scan of the Windows Firewall rules does not highlight anything). 73, ... Joe, W4TV On 2021-12-20 12:34 PM, Michael Black via groups.io wrote:
There's a 32-bit and 64-bit version of SSL.Did you load the correct one? |
|
|
|
Mike Black
From the help...
toggle quoted message
Show quoted text
If you still get the same network error after installing the OpenSSL libraries then you also need to install the Microsoft VC++ 2013 Redistributable component. From the download page select vcredist_x86.exe for use with the 32-bit WSJT-X build or vcredist_x64.exe with the 64-bit build, then run it to install. Mike W9MDB On Monday, December 20, 2021, 03:02:27 PM CST, Joe Subich, W4TV <lists@...> wrote:
Mike, Interesting ... I have had no issues on my Windows 10 Pro system but tried Windows 10 Home (on my laptop) and the LotW user list update failed there. Both are 64 bit systems ... Both are 21H1, build 19043.1415 Both have Windows Feature Experience Pack 120-2212.3920.0 Both have the current Open SSL 64 bit libraries installed. Both are running WSJTX 2.5.3 (64 bit) Now, where to look for differences (a cursory scan of the Windows Firewall rules does not highlight anything). 73, ... Joe, W4TV On 2021-12-20 12:34 PM, Michael Black via groups.io wrote: There's a 32-bit and 64-bit version of SSL.Did you load the correct one? |
|
|
|
Joe Subich, W4TV
That's not it. The microsoft VC++ 2013 Redistributable component is
toggle quoted message
Show quoted text
already installed. However, I downloaded the vcredist_x64.exe and ran it again. It performed a "repair" and restarted my system ... The error persists following the vcredist_x64 "repair". Again, my systems are identical with the exceptions of Win 10 Home vs. Win 10 Pro ... both are running identical installations of 2.5.3 64 bit. The Pro system works, the Home system fails with the network error. 73, ... Joe, W4TV On 2021-12-20 4:07 PM, Michael Black via groups.io wrote:
From the help...If you still get the same network error after installing the OpenSSL libraries then you also need to install the Microsoft VC++ 2013 Redistributable component. From the download page select vcredist_x86.exe for use with the 32-bit WSJT-X build or vcredist_x64.exe with the 64-bit build, then run it to install. |
|
|
|
Mike Black
Try this utility
toggle quoted message
Show quoted text
https://docs.microsoft.com/en-us/sysinternals/downloads/listdlls And look the DLLs for WSJT-X and see if there's an openssl reference. Interestingly enough on Windows 11 I just installed here I didn't have to download the SSL library. Here's my depending list for WSJT-XYou should be able to compare your two systems to see if there's a difference. Mike W9MDB wsjtx.exe pid: 86952Command line: wsjtx -r test2 Base Size Path0x0000000000400000 0x199f4000 C:\WSJT\wsjtx253\bin\wsjtx.exe0x000000006f5e0000 0x207000 C:\Windows\SYSTEM32\ntdll.dll0x000000006e120000 0xbd000 C:\Windows\System32\KERNEL32.DLL0x000000006cbe0000 0x374000 C:\Windows\System32\KERNELBASE.dll0x000000006e400000 0xa3000 C:\Windows\System32\msvcrt.dll0x000000006d4f0000 0x29000 C:\Windows\System32\GDI32.dll0x000000006d210000 0x26000 C:\Windows\System32\win32u.dll0x0000000067500000 0x9a5000 C:\WSJT\wsjtx253\bin\libhamlib-4.dll0x0000000063740000 0x24f000 C:\WSJT\wsjtx253\bin\libfftw3f-3.dll0x0000000068880000 0x639000 C:\WSJT\wsjtx253\bin\Qt5Core.dll0x000000006cac0000 0x112000 C:\Windows\System32\gdi32full.dll0x000000006f070000 0x1ac000 C:\Windows\System32\USER32.dll0x000000006f310000 0xac000 C:\Windows\System32\ADVAPI32.dll0x0000000061940000 0x6d2000 C:\WSJT\wsjtx253\bin\Qt5Gui.dll0x000000006d3d0000 0x9d000 C:\Windows\System32\msvcp_win.dll0x000000006e240000 0x6f000 C:\Windows\System32\WS2_32.dll0x000000006e360000 0x9d000 C:\Windows\System32\sechost.dll0x000000006d240000 0x111000 C:\Windows\System32\ucrtbase.dll0x000000006e4b0000 0x19a000 C:\Windows\System32\ole32.dll0x000000006e690000 0x121000 C:\Windows\System32\RPCRT4.dll0x000000006e8c0000 0x7ae000 C:\Windows\System32\SHELL32.dll0x000000006d640000 0x378000 C:\Windows\System32\combase.dll0x000000006e7e0000 0xd6000 C:\Windows\System32\OLEAUT32.dll0x000000006b480000 0xf1000 C:\WSJT\wsjtx253\bin\Qt5Multimedia.dll0x0000000069700000 0x1b2000 C:\WSJT\wsjtx253\bin\Qt5Network.dll0x000000006d0a0000 0x162000 C:\Windows\System32\CRYPT32.dll0x000000006df40000 0x5c000 C:\WSJT\wsjtx253\bin\Qt5PrintSupport.dll0x0000000065880000 0x1c000 C:\WSJT\wsjtx253\bin\Qt5SerialPort.dll0x000000006d7c0000 0x4a000 C:\WSJT\wsjtx253\bin\Qt5Sql.dll0x000000006dc60000 0x46b000 C:\Windows\System32\SETUPAPI.dll0x000000006f420000 0xec000 C:\Windows\System32\comdlg32.dll0x0000000061440000 0x1a000 C:\WSJT\wsjtx253\bin\libgcc_s_seh-1.dll0x000000006f220000 0xea000 C:\Windows\System32\shcore.dll0x0000000064940000 0x15000 C:\WSJT\wsjtx253\bin\libwinpthread-1.dll0x0000000063600000 0x2e000 C:\WSJT\wsjtx253\bin\libgomp-1.dll0x000000006cf00000 0x59000 C:\WSJT\wsjtx253\bin\libquadmath-0.dll0x000000006f3c0000 0x5d000 C:\Windows\System32\SHLWAPI.dll0x000000006fc40000 0x163000 C:\WSJT\wsjtx253\bin\libstdc++-6.dll0x00000000667a0000 0x280000 C:\Windows\SYSTEM32\d3d11.dll0x000000006a2f0000 0xf3000 C:\Windows\SYSTEM32\dxgi.dll0x000000005b500000 0x18000 C:\Windows\SYSTEM32\NETAPI32.dll0x0000000057870000 0x1d000 C:\Windows\SYSTEM32\MPR.dll0x000000006b600000 0x43000 C:\WSJT\wsjtx253\bin\libusb-1.0.dll0x0000000068700000 0x36000 C:\WSJT\wsjtx253\bin\libboost_filesystem-mgw8-mt-x64-1_77.dll0x000000006a480000 0xcd000 C:\WSJT\wsjtx253\bin\libboost_log_setup-mgw8-mt-x64-1_77.dll0x00000000655c0000 0x24000 C:\WSJT\wsjtx253\bin\libboost_thread-mgw8-mt-x64-1_77.dll0x000000006c1d0000 0x29000 C:\Windows\SYSTEM32\USERENV.dll0x0000000066a60000 0xa000 C:\Windows\SYSTEM32\VERSION.dll0x0000000065710000 0x33000 C:\Windows\SYSTEM32\WINMM.dll0x000000006b7c0000 0xe7000 C:\Windows\SYSTEM32\DNSAPI.dll0x000000006b790000 0x2d000 C:\Windows\SYSTEM32\IPHLPAPI.DLL0x000000005c5d0000 0xb2000 C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.22000.1_none_271a8fad6a2d1b1e\COMCTL32.dll0x0000000062e90000 0x9b000 C:\Windows\SYSTEM32\WINSPOOL.DRV0x000000006c340000 0xc000 C:\Windows\SYSTEM32\CRYPTBASE.DLL0x000000006c7c0000 0x4c000 C:\Windows\SYSTEM32\cfgmgr32.DLL0x000000006b920000 0xc000 C:\Windows\SYSTEM32\NETUTILS.DLL0x0000000066d30000 0x28000 C:\Windows\SYSTEM32\SRVCLI.DLL0x000000003df50000 0x585000 C:\WSJT\wsjtx253\bin\Qt5Widgets.dll0x000000003e4e0000 0xbb000 C:\WSJT\wsjtx253\bin\libboost_log-mgw8-mt-x64-1_77.dll0x0000000059970000 0xc000 C:\Windows\SYSTEM32\Secur32.dll0x000000006bef0000 0x40000 C:\Windows\SYSTEM32\SSPICLI.DLL0x000000006a5f0000 0x2f000 C:\Windows\SYSTEM32\dwmapi.dll0x000000006a180000 0xac000 C:\Windows\SYSTEM32\UxTheme.dll0x000000006e0d0000 0x31000 C:\Windows\System32\IMM32.DLL0x000000006e680000 0x9000 C:\Windows\System32\NSI.dll0x000000006a880000 0x1c5000 C:\WSJT\wsjtx253\plugins\platforms\qwindows.dll0x0000000068ec0000 0x14000 C:\Windows\SYSTEM32\WTSAPI32.dll0x000000006bcd0000 0x18000 C:\Windows\SYSTEM32\kernel.appcore.dll0x000000006d020000 0x80000 C:\Windows\System32\bcryptPrimitives.dll0x000000006ac70000 0x867000 C:\Windows\SYSTEM32\windows.storage.dll0x000000006ab00000 0x166000 C:\Windows\SYSTEM32\wintypes.dll0x000000006c9f0000 0x21000 C:\Windows\SYSTEM32\profapi.dll0x000000006b4f0000 0x4d000 C:\Windows\SYSTEM32\powrprof.dll0x000000006b6d0000 0x13000 C:\Windows\SYSTEM32\UMPDC.dll0x000000006cc40000 0x35000 C:\WSJT\wsjtx253\plugins\styles\qwindowsvistastyle.dll0x000000001ae50000 0x14000 C:\WSJT\wsjtx253\plugins\imageformats\qgif.dll0x000000006c600000 0x16000 C:\WSJT\wsjtx253\plugins\imageformats\qicns.dll0x000000006e840000 0x14000 C:\WSJT\wsjtx253\plugins\imageformats\qico.dll0x00000000626c0000 0x6a000 C:\WSJT\wsjtx253\plugins\imageformats\qjpeg.dll0x00000000400e0000 0x12000 C:\WSJT\wsjtx253\plugins\imageformats\qsvg.dll0x00000000436e0000 0x55000 C:\WSJT\wsjtx253\bin\Qt5Svg.dll0x0000000040100000 0x12000 C:\WSJT\wsjtx253\plugins\imageformats\qtga.dll0x0000000043740000 0x73000 C:\WSJT\wsjtx253\plugins\imageformats\qtiff.dll0x0000000066ac0000 0x12000 C:\WSJT\wsjtx253\plugins\imageformats\qwbmp.dll0x00000000437c0000 0x91000 C:\WSJT\wsjtx253\plugins\imageformats\qwebp.dll0x00000000629c0000 0x113000 C:\WSJT\wsjtx253\plugins\sqldrivers\qsqlite.dll0x000000004d750000 0x25f000 C:\Windows\system32\dwrite.dll0x000000006c790000 0x2c000 C:\Windows\SYSTEM32\DEVOBJ.dll0x000000006d360000 0x66000 C:\Windows\System32\WINTRUST.dll0x000000006c380000 0x12000 C:\Windows\SYSTEM32\MSASN1.dll0x000000006c980000 0x1e000 C:\WSJT\wsjtx253\plugins\audio\qtaudio_windows.dll0x000000006e2b0000 0xaf000 C:\Windows\System32\clbcatq.dll0x000000005a4a0000 0x1f000 C:\Windows\System32\devenum.dll0x000000006a4b0000 0x34000 C:\Windows\SYSTEM32\ntmarta.dll0x000000005c0d0000 0x29000 C:\Windows\SYSTEM32\winmmbase.dll0x00000000651e0000 0x9c000 C:\Windows\SYSTEM32\MMDevAPI.DLL0x000000001e8c0000 0x46000 C:\Windows\SYSTEM32\wdmaud.drv0x0000000067d20000 0xb000 C:\Windows\SYSTEM32\AVRT.dll0x0000000045d50000 0x9000 C:\Windows\SYSTEM32\ksuser.dll0x000000005ba90000 0x1d5000 C:\Windows\SYSTEM32\AUDIOSES.DLL0x000000003e7d0000 0xd000 C:\Windows\SYSTEM32\msacm32.drv0x000000002f370000 0x1e000 C:\Windows\SYSTEM32\MSACM32.dll0x000000003e7c0000 0xb000 C:\Windows\SYSTEM32\midimap.dll0x00000000586b0000 0xb000 C:\Windows\SYSTEM32\msdmo.dll0x0000000061fe0000 0xa2000 C:\Windows\SYSTEM32\dsound.dll0x0000000060f90000 0xb1000 C:\Windows\SYSTEM32\ResampleDmo.DLL0x000000006a4f0000 0x15000 C:\Windows\SYSTEM32\resourcepolicyclient.dll0x0000000068250000 0x19000 C:\Windows\SYSTEM32\dhcpcsvc6.DLL0x0000000068d10000 0x1e000 C:\Windows\SYSTEM32\dhcpcsvc.DLL0x000000005ca00000 0x2a5000 C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22000.120_none_9d947278b86cc467\comctl32.dll0x0000000065a20000 0x1ae000 C:\Windows\SYSTEM32\WindowsCodecs.dll0x0000000048d60000 0x66000 C:\Windows\System32\thumbcache.dll0x00000000688c0000 0x10c000 C:\Windows\system32\winhttp.dll0x000000003e840000 0x17000 C:\Windows\system32\napinsp.dll0x000000003e820000 0x1b000 C:\Windows\system32\pnrpnsp.dll0x000000006c0e0000 0x67000 C:\Windows\System32\mswsock.dll0x000000003e800000 0x12000 C:\Windows\System32\winrnr.dll0x000000004cd40000 0x15000 C:\Windows\system32\wshbth.dll0x000000003e7e0000 0x1f000 C:\Windows\system32\nlansp_c.dll0x0000000062620000 0x1a6000 C:\Windows\system32\d3d9.dll0x000000006a430000 0x38000 C:\Windows\SYSTEM32\dxcore.dll0x0000000066a20000 0x31000 C:\Windows\SYSTEM32\cryptnet.dll0x000000006e660000 0x1f000 C:\Windows\System32\imagehlp.dll0x000000006c320000 0x18000 C:\Windows\SYSTEM32\CRYPTSP.dll0x000000006bc30000 0x35000 C:\Windows\system32\rsaenh.dll0x000000006c4a0000 0x27000 C:\Windows\SYSTEM32\bcrypt.dll0x0000000067de0000 0x44000 C:\Windows\SYSTEM32\directxdatabasehelper.dll0x000000006d520000 0x11e000 C:\Windows\System32\MSCTF.dll0x000000004a3c0000 0x5d000 C:\Windows\system32\dataexchange.dll0x0000000064be0000 0x266000 C:\Windows\system32\twinapi.appcore.dll0x0000000050ee0000 0x12d000 C:\Windows\SYSTEM32\textinputframework.dll0x0000000069bc0000 0x132000 C:\Windows\SYSTEM32\CoreMessaging.dll0x0000000067310000 0x36d000 C:\Windows\SYSTEM32\CoreUIComponents.dll0x0000000050700000 0x188000 C:\Windows\System32\Windows.UI.dll0x0000000065840000 0xa000 C:\Windows\System32\rasadhlp.dll0x0000000067a20000 0x81000 C:\Windows\System32\fwpuclnt.dll On Monday, December 20, 2021, 03:32:23 PM CST, Joe Subich, W4TV <lists@...> wrote:
That's not it. The microsoft VC++ 2013 Redistributable component is already installed. However, I downloaded the vcredist_x64.exe and ran it again. It performed a "repair" and restarted my system ... The error persists following the vcredist_x64 "repair". Again, my systems are identical with the exceptions of Win 10 Home vs. Win 10 Pro ... both are running identical installations of 2.5.3 64 bit. The Pro system works, the Home system fails with the network error. 73, ... Joe, W4TV On 2021-12-20 4:07 PM, Michael Black via groups.io wrote: From the help...If you still get the same network error after installing the OpenSSL libraries then you also need to install the Microsoft VC++ 2013 Redistributable component. From the download page select vcredist_x86.exe for use with the 32-bit WSJT-X build or vcredist_x64.exe with the 64-bit build, then run it to install. |
|
|
|
I switched to the 32-bit version due to the call letters with ac / crashing the 64-bit. The LoTW is working for download now. Just waiting to see if Worked is functioning yet. Kind of killing two birds with one stone.
Thanks all for the suggestions de N2BRG, Gary |
|
|