Many thanks for all your efforts in creating the greatest log book system for HAM radio! It actually works VERY well and with minimal fuss. This is a testament to you and all the contributions made to CQRLOG.
Having an issue with 2.3.0(001) in regards to QRZ lookups failing due to username/password being incorrect. Debug indicates only the following: (scrubbed "set name=" to ***)
GetIOTAFor<?xml version="1.0" encoding="utf-8" ?>
Username/password incorrect
Tue Jan 1 04:02:33 2019
cpu: 0.770s
As I understand it, this is an ongoing problem with QRZ. While I can use HamQTH for lookup. I prefer QRZ as the graphical dissemination of information is greater than any. And they also allow one to manage additional call signs. Have yet to find that functionality on HamQTH or others.
I can assist in troubleshooting as I am technically savvy.
Best regards,
Byron
KN4PHS
Hi Byron!
>"And they also allow one to manage additional call signs. Have yet to find that functionality on HamQTH or others."
You can manage additional calls in HamQth.com from settings (top right, the "cogwheel")
See image.
Is that what you are looking for?
File:
--
Saku
OH1KH
Hi Byron!
I hope I understood your problem right.
If you put this to your browser with change to your callsign and your password instead of mine:
https://xmldata.qrz.com/xml/current/?username=oh1kh;password=XXXXX;agent...
You will get answer like:
<QRZDatabase xmlns="http://xmldata.qrz.com" version="1.33">
<Session>
<Key>542cc63235c06bbc7c77eaad5f80b7db</Key>
<Count>15374</Count>
<SubExp>non-subscriber</SubExp>
<GMTime>Tue Jan 1 17:47:00 2019</GMTime>
<Remark>cpu: 0.128s</Remark>
</Session>
</QRZDatabase>
If it gives "non-subscriber" you fill not get all informations. You will know it at this phase already.
But you can continue trying by copying Key string from that reply and place it to below line after "s=" and before ";" that you will next feed to browser:
https://xmldata.qrz.com/xml/current/?s=542cc63235c06bbc7c77eaad5f80b7db;...
That should give something like:
<QRZDatabase xmlns="http://xmldata.qrz.com" version="1.33">
<Callsign>
<call>OH1KH</call>
<fname>Sakari (Saku)</fname>
<name>Nylund</name>
<addr2>28800 Pori</addr2>
<country>Finland</country>
</Callsign>
<Session>
<Key>542cc63235c06bbc7c77eaad5f80b7db</Key>
<Count>15374</Count>
<SubExp>non-subscriber</SubExp>
<Message>
A subscription is required to access the complete record.
</Message>
<GMTime>Tue Jan 1 17:48:24 2019</GMTime>
<Remark>cpu: 0.030s</Remark>
</Session>
</QRZDatabase>
Again it informs that "A subscription is required to access the complete record."
So If you get similar responses with your callsign and password there is no way cqrlog can fill all information of NewQso.
If you can get all informations with this browser test, but cqrlog does not record them then it is a programming question of cqrlog.
--
Saku
OH1KH
Many thanks for the feedback and assistance.
Upon using the URL in your example, https://xmldata.qrz.com/xml/current/?username=oh1kh;password=XXXXX;agent...
I found the user agent does not parse special characters properly. Specifically the # symbol
Upon changing my password to using 16 characters of alpha/numeric only characters, the user agent authenticates without issue
I have verified my log in and password are correct for QRZ.com, but continue to get the above error. Any ideas for fixing would be greatly appreciated!
73,
Jim
I have also verified that I am a subscriber to QRZ.com
Hi Jim!
This message chain is quite good example. If you can do it like I described then Cqlog can do it too.
Try to change you password to very simple just ordinary letters and numbers and test again.
The message chain is rather old, 2019, now question is what version of Cqrlog you are using and could it cause this problem.
--
Saku
OH1KH