Log4OM

I'm not sure what's causing this, but it seems I've seen Waco Tx a lot when looking up calls on this latest version 2.26.0.0

I'm using QRZ as the primary source, and no secondary.

I can reproduce it with call KD5TDK. In QRZ, he's in EM14am, but when I search for his call in this version, it says EM11.

ka5pmv wrote: 24 Jan 2023, 21:55 I'm not sure what's causing this, but it seems I've seen Waco Tx a lot when looking up calls on this latest version 2.26.0.0

I'm using QRZ as the primary source, and no secondary.

I can reproduce it with call KD5TDK. In QRZ, he's in EM14am, but when I search for his call in this version, it says EM11.

Paul,

Read through this thread: https://forum.log4om.com/viewtopic.php?t=8096

Look at the screen clips I attached in my reply. Try and set your Information Provider Configuration the same and try those calls again.

Make sure that your Country and Clublog files have also been updated. Settings / Update Resources / Clublog & Country File

I updated Country & Clublog, but same results.

I turned up the log level to debug, and get the information below.
If I take the search url, and put that into a new browser tab, the grid info coming back from QRZ is correct (EM14am), but the Grid in on screen is still EM11.

11:18:22.016 Debug: [dje_zJNHB8DUQDUUDKANLX47C9KPTAJT62JAHY2_ejd][MoveNext] : Performing QSO search on callsign KD5TDK
11:18:22.016 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call KD5TDK on date 1/25/2023 11:18:22 AM
11:18:22.026 Debug: [dje_zJNHB8DUQDUUDKANLX47C9KPTAJT62JAHY2_ejd][MoveNext] : No Clublog CQ ZONE found for KD5TDK
11:18:22.042 Debug: [dje_z2QAR75GGYL4J7YEFRZV3ZDL3G9VQ_ejd][MoveNext] : Searching primary engine QRZCOM
11:18:22.043 Info: [dje_z96VMACW2GZT6GB6EYAGTX_ejd] : [QRZCOM] Search start on KD5TDK (originally KD5TDK)
11:18:22.044 Debug: [dje_z96VMACW2GZT6GB6EYAGTX_ejd][MoveNext] : [QRZCOM] search url https://xmldata.qrz.com/xml/1.34/?s=9ad ... nt=LOG4OM2
11:18:22.045 Debug: [dje_zUQ74T8UPWW45ZQRJEWKEV7DBV6W65PUW72_ejd][MoveNext] : UpdateQSO on screen complete
11:18:22.272 Debug: [FwFile][WriteFile] : Begin writing text file C:\Users\paul_\AppData\Roaming\Log4OM2\temp\TEMP_KD5TDK_QRZCOM.XML
11:18:22.274 Debug: [FwFile][WriteFile] : Text file write completed C:\Users\paul_\AppData\Roaming\Log4OM2\temp\TEMP_KD5TDK_QRZCOM.XML
11:18:22.275 Info: * [dje_z96VMACW2GZT6GB6EYAGTX_ejd][232 ms] : [QRZCOM] Search finished on KD5TDK (originally KD5TDK)
11:18:22.276 Debug: [dje_zJNHB8DUQDUUDKANLX47C9KPTAJT62JAHY2_ejd][MoveNext] : Searching clublog exceptions
11:18:22.277 Debug: [dje_zJNHB8DUQDUUDKANLX47C9KPTAJT62JAHY2_ejd][MoveNext] : LOTW user identified
11:18:22.278 Debug: * [dje_zJNHB8DUQDUUDKANLX47C9KPTAJT62JAHY2_ejd][MoveNext][262 ms] : QSO search on callsign KD5TDK completed
11:18:22.279 Debug: * [dje_zT5YET9WUT4N2WEA94B6ULHK3GVAA_ejd][MoveNext][27004 ms] : DownloadImage: Downloading image from https://cdn-xml.qrz.com/k/kd5tdk/20170610_133448.jpg
11:18:22.28 Info: [dje_zT5YET9WUT4N2WEA94B6ULHK3GVAA_ejd] : DownloadImage: Found in cache: C:\Users\paul_\AppData\Roaming\Log4OM2\temp\TEMP_KD5TDK.png
11:18:22.297 Info: * [dje_z4NY9FKSKC7A93VENUCMKR5UKCG9D65JLXW_ejd] [AWARDCALLPARSER] : Award Management - Parse callsign started on KD5TDK
11:18:22.298 Debug: [dje_zXFX9AK8369JQV3LLW4M4Q_ejd][MoveNext] : Loading Awards items from database for multiple award codes
11:18:22.32 Debug: * [dje_zXFX9AK8369JQV3LLW4M4Q_ejd][MoveNext][20 ms] : Awards reference list retrieved from database
11:18:22.321 Info: * [dje_z4NY9FKSKC7A93VENUCMKR5UKCG9D65JLXW_ejd] [AWARDCALLPARSER - 23 ms] : Award Management - Parse callsign terminated on KD5TDK
11:18:22.6 Info: * [dje_z5SGQUYA7KTTZ2MW3WZB98QTGGZJ67KDWLX_ejd] [STATS] : ### STATS ###
11:18:22.668 Info: * [dje_z5SGQUYA7KTTZ2MW3WZB98QTGGZJ67KDWLX_ejd] [STATS - 67 ms] : ### END STATS ###

Well the lookup works fine for me, see below

Are you sure that you have the Program config/info providers - Configuration tab set correctly, again as below?

-

Ok, I have my realtime logging now in the order listed above, and is now picking the correct location.

Although, now i'm trying to edit and refresh records from yesterday that pulled in the incorrect Grid, and they're not updating when I click Edit, and Refresh. Am I going to have to enter them manually?

They wont by using edit!

You need to use QSO manager, bulk delete the incorrect grids, then bulk update the data using Update info in the QSO manager

All in our user guide

Got them updated, Thanks!

Just to mention, I've only been using Log4OM for a little over a month or so now, so please have patience with me as I get familiar with the program. As someone that's been in software development for many years, I can see there's been a LOT of time creating this, therefore, it'll take a while for me to learn how to use it. When things like this happens, you have to stop and figure out what caused this to suddenly change it's behavior that I've experienced over 3 versions. I finally got it working nicely with WSJT-X, and I even have my pota laptop sending log entries over to my desktop, or online depending on what environment I'm at.

Cheers!