¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Pathfinder callbook error


 

¿ªÔÆÌåÓý

When I use Pathfinder to lookup a callsign I get the Pathfinder not logged into QRZ.? But I have verified that I am logged in.? I can click on the Pathfinder icon in the Tray and it opens and when I click on QRZ it looks up the callsign.? My password and Automatic look up filled in and checked.? Any recommendations?



73, George
W2GS


 

+ AA6YQ comments below
When I use Pathfinder to lookup a callsign I get the Pathfinder not logged into QRZ.? But I have verified that I am logged in.? I can click on the Pathfinder icon in the Tray and it opens and when I click on QRZ it looks up the callsign.? My password and Automatic look up filled in and checked.? Any recommendations?
+ When did this misbehavior first begin? What changes did you make to your hardware or software around that time?

? ? ?73,

? ? ? ? ? ?Dave, AA6YQ


 

¿ªÔÆÌåÓý

Dave,
This on a new Win11 PC with a new installation of DXLabs software.? I followed the wiki to move my setup to the new computer and everything is working except for callsign lookup.? I checked the Pathfinder settings on my old computer and they are the same as on the new computer.
George, W2GS

On 5/16/2025 10:23 AM, Dave AA6YQ wrote:

+ AA6YQ comments below
When I use Pathfinder to lookup a callsign I get the Pathfinder not logged into QRZ.? But I have verified that I am logged in.? I can click on the Pathfinder icon in the Tray and it opens and when I click on QRZ it looks up the callsign.? My password and Automatic look up filled in and checked.? Any recommendations?
+ When did this misbehavior first begin? What changes did you make to your hardware or software around that time?

? ? ?73,

? ? ? ? ? ?Dave, AA6YQ


 

George,
I noticed exactly the same thing on May 15th as you described above.
Nothing was changed in the DXL settings.
Even more, PV was difficult because??was not reachable (now, that happens more often).?
This morning (May 16th) still the same problems. Tonight 17:00 UTC) everything seems to be normal. Hopefully for you too.
On May 14th I did see a cumulative update for my W10 22H2 x64 (KB5058379) but that will not be the cause I think.
Sometimes the problems are solved by themselves: we have to be patient...
73 de ON6TM,
Tony


 

+ AA6YQ comments below

This on a new Win11 PC with a new installation of DXLabs software.

+ So both your hardware and you software changed.

+ To enable me to see what's going on, please do the following:

1. on Pathfinder's Configuration window, check the "Log debugging info" box

2. terminate Pathfinder

3. start Pathfinder, and wait for it to initiate

4. direct Pathfinder to lookup my callsign in QRZ

5. on Pathfinder's Configuration window, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your Pathfinder folder to an email message, and send that message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


 

+ AA6YQ comments below

I noticed exactly the same thing on May 15th as you described above.
Nothing was changed in the DXL settings.
Even more, PV was difficult because <> was not reachable (now, that happens more often).

+ Make sure that your anti-malware is configured to enable PropView to access the internet.

This morning (May 16th) still the same problems. Tonight 17:00 UTC) everything seems to be normal. Hopefully for you too.
On May 14th I did see a cumulative update for my W10 22H2 x64 (KB5058379) but that will not be the cause I think.

Sometimes the problems are solved by themselves: we have to be patient...

+ I strongly prefer that users immediately report problematic behavior, rather than wait on the infinitesimally small chance that the problem will solve itself. Waiting to report a problem can deprive us of critical evidence needed to identify the root cause of the misbehavior.

73,

Dave, AA6YQ