Date   

Re: HRD Logbook Accepts But Fails To Log Contacts

Chris VK2BYI
 

Ian, MI1CCU/EI3HFB, tried the suggestion from Morris, WA4MIT, and created a blank Access database and listed it directly under the Maria DB Logbook in HRD Logbook Manager.  I guess something similar to this:



After rebooting his computer, Ian now reports that it is working 100% - including after many subsequent reboots.

Thanks Ian a
nd Morris.

73 Chris
VK2BYI


Re: QSORelay and AVAST

Bob Davet
 

Chris:

 

Thanks. That was one thing I did not think of.

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris VK2BYI
Sent: Sunday, May 28, 2017 7:58 PM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] QSORelay and AVAST

 

Or you could simply exclude 'C:\Program Files (x86)\VK2BYI\QSO Relay' and 'http://www.vk2byi.com.au/qsorelay/' as per these instructions from Avast: Excluding certain files or websites from scanning


Virus-free. www.avast.com


Re: QSORelay and AVAST

Chris VK2BYI
 
Edited

Or you could simply exclude 'C:\Program Files (x86)\VK2BYI\QSO Relay' and 'http://www.vk2byi.com.au/qsorelay/' as per these instructions from Avast: Excluding certain files or websites from scanning


QSORelay and AVAST

Bob Davet
 

Just going to mention this because it has happened to me twice now on updates. Most recently on the 1.4 upgrade this morning. Just got home from work. Was tired and forgot to stop AVAST.

I am using AVAST as my virus protection. Seems to work for me.
I know the work around for it but sometimes I forget like I did this AM when updating to 1.4

AVAST does not recognize the program so it scans it then quarantines it and you have to send it and a bunch of other information to AVAST so they can make sure it is OK. That can take from 2 days to 2 weeks.

I have a workaround for it. When you get ready to install any QSORelay program and/or update just turn off AVAST for 10 minutes till QSORelay is done installing.Then everything is good.

Chris, can you possibly look into getting QSORelay checked by AVAST and any other antivirus program so this does not happen when people upgrade or install?? Don't know what is involved or how that is done. It would just be nice to not have to deal with this issue when installing or upgrading.

Thanks

Bob
W8RID


locked QSO Relay version 1.4

Chris VK2BYI
 
Edited

Please be advised that a new release of QSO Relay (Version 1.4) is now available for download at http://www.vk2byi.com.au/qsorelay/, or by selecting the Check for Updates... item on the QSO Relay menu.

This version is a minor release only, that addresses a couple of issues that have affected a very small number of users.  Most users will notice no change in functionality.

  • Handles ‘empty’ values in the Latitude, Longitude, My Latitude and My Longitude columns during ADIF logging file extract;
  • Rounds non-integer values in RX Power and TX Power columns during ADIF logging file extract;
  • Added RX Power field to ADIF logging file extract.

Again we wish to thank all users for their positive feedback and patience in working with us to resolve some of the issues experienced.

 


Re: HRD Logbook Accepts But Fails To Log Contacts

Chris VK2BYI
 

Panos, SV8JNL, emailed me overnight and tells me he now has it working again without problem for 2 hours, and at the time of writing believes the problem is fixed.

He and a friend of his, were using the default 'mysql' database.  He created a new database without any tables in Maria DB, and then I presume he created a new ODBC Data Source Name for this database, and "opened" it with HRD Logbook so that it created the required 'table_hrd_contacts_v01' table.

Thanks Panos.

73 Chris VK2BYI


Re: HRD Logbook Accepts But Fails To Log Contacts

Chris VK2BYI
 

Ah yes, I remember that happening with me and SQL Server some time back.  I had to have an empty Access logbook open in HRD Logbook at the same time as the SQL Server logbook that I use for my contacts, otherwise an 'unspecified error' kept popping up.  But I haven't needed to do that for quite some time now, and assume it was fixed.  I went looking through the HRD release notes forum looking for a mention, but I couldn't find it.

Those affected can try Morris' suggestion, can't hurt.  Thanks Morris.

73 Chris VK2BYI


Re: HRD Logbook Accepts But Fails To Log Contacts

Morris WA4MIT
 

I am using Maria DB with HRD.647 with no issues I have logged many contacts now with QSOrelay without any difficulties. I have been setup on Maria DB for a good while now without any issues with it either. Get them to setup a dummy blank my access DB along with their in use Marie DB. JTAlert had a similar issue with Maria DB users and the blank dummy access DB was the fix. 73 wa4mit Morris



On Saturday, May 27, 2017 12:03 AM, Chris VK2BYI <chris@...> wrote:


I have been made aware of two QSO Relay users (Ian, MI1CCU/EI3HFB and Panos, SV8JNL) who are experiencing a problem with HRD Logbook not logging contacts.  They are both using Maria DB as the back-end database server.

Here is a snippet from a session tracing log captured by Ian, that shows the problem that both Ian and Panos are experiencing.  Some the detail has been removed for clarity and replaced with 4-dot ellipses (....)

A contact from JTAlert is received:
2017-05-24 10:45:18.1993 Processing received data
<CALL:5>DF8JK .... <EOR>

The contact is written to QSO Relay SQLite database file:
2017-05-24 10:45:18.1998 Logging contact in SQLite
Insert Into [Log] ( QsoId, .... , '' );
2017-05-24 10:45:18.5675 Contact successfully logged in SQLite

The contact is relayed from QSO Relay to HRD Logbook.  Here is the conversation between QSO Relay and the HRD Logbook command line interface:
2017-05-24 10:45:18.5675 Relaying contact to HRD
[c] ver
Ham Radio Deluxe Version Release 6.4.0.647
[c] 
db add "MI1CCU" { CALL="DF8JK" .... }
Found 31 Valid Fields...
Added 31 Fields to MI1CCU...           <--- NOTE HRD Logbook indicates that 31 fields will be added to the 'MI1CCU' database
[c] 
quit
[c] 
2017-05-24 10:45:21.9301 Contact successfully relayed to HRD

QSO Relay then tries to verify that the contact has in fact been written to the database:
2017-05-24 10:45:21.9301 Verifying contact was logged by HRD
2017-05-24 10:45:21.9306 Checking HRD Logbook for DF8JK, 20170524, 094000, 20m, JT65
2017-05-24 10:45:26.1767 Retrying...
2017-05-24 10:45:27.1825 Retrying...
2017-05-24 10:45:28.1870 Retrying...
2017-05-24 10:45:29.1885 Retrying...
2017-05-24 10:45:30.1918 Retrying...
2017-05-24 10:45:31.1941 Retrying...
2017-05-24 10:45:32.1955 Retrying...
2017-05-24 10:45:33.1969 Retrying...
2017-05-24 10:45:34.1982 Retrying...
2017-05-24 10:45:35.2000 Retrying...
2017-05-24 10:45:37.9388 WARNING: Contact was not verified as logged in HRD

However, after 10 attempts at 1 second intervals, the contact cannot be found in the database.  A direct query of the database confirms the record has not been written.

I have never experienced this issue myself, but a close friend recently has, and he fixed it by completely uninstalling Ham Radio Deluxe using the freeware version of Revo Uninstaller, before re-installing it.  Although, he uses Microsoft SQL Server and not Maria DB.

Ian is going to attempt the reinstall as well.  Panos tried that, and that worked fine for him initially, but he now reports the same problem has returned.
Maria DB server is made by the original developers of MySQL, and is reportedly a binary compatible replacement for MySQL.  I have tested Maria DB on my development system with QSO Relay and HRD Logbook, and it works without any problems at all using MySQL Connection String properties.

I am aware of a long-standing issue in HRD Logbook, where a contact is only partially logged if an ADDRESS field contains carriage returns and/or line feeds characters.  However, in this case there is no ADDRESS field supplied in the data being sent to HRD Logbook, and it fails to log anything at all.

I am confident the issue lies within HRD Logbook and I have searched the HRDLLC Support Forum for an answer, but to no avail.  I would raise a ticket with HRD if I could reproduce the problem, but I can’t.

If any members reading this post can share their experiences and advice re Maria DB and HRD Logbook, I am sure they would be grateful.

73 Chris
VK2BYI



HRD Logbook Accepts But Fails To Log Contacts

Chris VK2BYI
 
Edited

I have been made aware of two QSO Relay users (Ian, MI1CCU/EI3HFB and Panos, SV8JNL) who are experiencing a problem with HRD Logbook not logging contacts.  They are both using Maria DB as the back-end database server.

Here is a snippet from a session tracing log captured by Ian, that shows the problem that both Ian and Panos are experiencing.  Some of the detail has been removed for clarity and replaced with 4-dot ellipses (....)

A contact from JTAlert is received:

2017-05-24 10:45:18.1993 Processing received data
<CALL:5>DF8JK .... <EOR>

The contact is written to QSO Relay SQLite database file:

2017-05-24 10:45:18.1998 Logging contact in SQLite

Insert Into [Log] ( QsoId, .... , '' );

2017-05-24 10:45:18.5675 Contact successfully logged in SQLite


The contact is relayed from QSO Relay to HRD Logbook.  Here is the conversation between QSO Relay and the HRD Logbook command line interface:

2017-05-24 10:45:18.5675 Relaying contact to HRD

[c] ver

Ham Radio Deluxe Version Release 6.4.0.647

[c] 

db add "MI1CCU" { CALL="DF8JK" .... }

Found 31 Valid Fields...

Added 31 Fields to MI1CCU...           <--- NOTE HRD Logbook indicates that 31 fields will be added to the 'MI1CCU' database

[c] 

quit

[c] 

2017-05-24 10:45:21.9301 Contact successfully relayed to HRD

QSO Relay then tries to verify that the contact has in fact been written to the database:
2017-05-24 10:45:21.9301 Verifying contact was logged by HRD

2017-05-24 10:45:21.9306 Checking HRD Logbook for DF8JK, 20170524, 094000, 20m, JT65

2017-05-24 10:45:26.1767 Retrying...

2017-05-24 10:45:27.1825 Retrying...

2017-05-24 10:45:28.1870 Retrying...

2017-05-24 10:45:29.1885 Retrying...

2017-05-24 10:45:30.1918 Retrying...

2017-05-24 10:45:31.1941 Retrying...

2017-05-24 10:45:32.1955 Retrying...

2017-05-24 10:45:33.1969 Retrying...

2017-05-24 10:45:34.1982 Retrying...

2017-05-24 10:45:35.2000 Retrying...

2017-05-24 10:45:37.9388 WARNING: Contact was not verified as logged in HRD

However, after 10 attempts at 1 second intervals, the contact cannot be found in the database.  A direct query of the database confirms the record has not been written.

I have never experienced this issue myself, but a close friend recently has, and he fixed it by completely uninstalling Ham Radio Deluxe using the freeware version of Revo Uninstaller, before re-installing it.  Although, he uses Microsoft SQL Server and not Maria DB.

Ian is going to attempt the reinstall as well.  Panos tried that, and that worked fine for him initially, but he now reports the same problem has returned.

Maria DB server is made by the original developers of MySQL, and is reportedly a binary compatible replacement for MySQL.  I have tested Maria DB on my development system with QSO Relay and HRD Logbook, and it works without any problems at all using MySQL Connection String properties.

I am aware of a long-standing issue in HRD Logbook, where a contact is only partially logged if an ADDRESS field contains carriage return and/or line feed characters.  However, in this case there is no ADDRESS field supplied in the data being sent to HRD Logbook, and it fails to log anything at all.

I am confident the issue lies within HRD Logbook and I have searched the HRDLLC Support Forum for an answer, but to no avail.  I would raise a ticket with HRD if I could reproduce the problem, but I can’t.

If any members reading this post can share their experiences and advice re Maria DB and HRD Logbook, I am sure Ian and Panos would be grateful.

73 Chris
VK2BYI


Re: QSORelay and HRD will not log

Chris VK2BYI
 

Hi Ian,
That really is strange.
I will contact you direct.
73 Chris
VK2BYI


Re: QSORelay and HRD will not log

Ian Morrow
 

Hi Chris

Further to your email

Thank you so much for getting back to me.

 

(Can I assume that you see the contact eventually appear in MI1CCU HRD Logbook?)

As to your Question, NO it does not appear in MI1CCU HRD Logbook at any time at all. 

It just says  WARNING  “Contact was not logged in Ham Radio Deluxe Logbook”

 

As I said before (I have to delete the QSO RELAY SQLITE DATABASE, create a new database, and then synchronise the database and then it works 100% again until I shut all down again.)

 

That is the only way I can get it to work.

If it would help you to have access to my Computer that is ok as I have Skype and Teamviewer on it , just let me know and we can arrange a time for you .

 

73’s

Ian MI1CCU/EI3HFB


Re: QSORelay and HRD will not log

Chris VK2BYI
 
Edited

Here is your Session 20170524102621.log with explanations and a lot of detail removed:

2017-05-24 10:26:21.7147 Trace listener started
 
1. Contact sent by JTAlert received:
2017-05-24 10:45:18.1993 Processing received data
<CALL:5>DF8JK<QSO_DATE:8> .... <EOR>
 
2. Contact stored in the QSO Relay SQLite database file OK:
2017-05-24 10:45:18.1998 Logging contact in SQLite
Native library pre-loader is trying to load native SQLite library "C:\Program Files (x86)\VK2BYI\QSO Relay\x86\SQLite.Interop.dll"...
Insert Into [Log] ( QsoId, .... '', '', '' );
2017-05-24 10:45:18.5675 Contact successfully logged in SQLite
 
3. The conversation with HRD Logbook where the contact is accepted:
2017-05-24 10:45:18.5675 Relaying contact to HRD
[c] ver
Ham Radio Deluxe Version Release 6.4.0.647
[c] 
db add "MI1CCU" { CALL="DF8JK" QSO_DATE="20170524" .... QSO_COMPLETE="Y" }
Found 31 Valid Fields...
Added 31 Fields to MI1CCU...
[c] 
quit
[c] 
2017-05-24 10:45:21.9301 Contact successfully relayed to HRD
 
4. However, here is the problem.  QSO Relay is trying to verify if the contact has been added to the HRD Logbook database:
2017-05-24 10:45:21.9301 Verifying contact was logged by HRD
2017-05-24 10:45:21.9306 Checking HRD Logbook for DF8JK, 20170524, 094000, 20m, JT65
2017-05-24 10:45:26.1767 Retrying...
2017-05-24 10:45:27.1825 Retrying...
2017-05-24 10:45:28.1870 Retrying...
2017-05-24 10:45:29.1885 Retrying...
2017-05-24 10:45:30.1918 Retrying...
2017-05-24 10:45:31.1941 Retrying...
2017-05-24 10:45:32.1955 Retrying...
2017-05-24 10:45:33.1969 Retrying...
2017-05-24 10:45:34.1982 Retrying...
2017-05-24 10:45:35.2000 Retrying...
2017-05-24 10:45:37.9388 WARNING: Contact was not verified as logged in HRD
 
After 10 attempts at 1 second intervals, it still can't see the contact in the HRD Logbook and warns that it is not verified.  And a similar thing is happening with other contacts in this session log, and contacts in the other session log files you provided.
 
Can I assume that you see the contact eventually appear in MI1CCU HRD Logbook?
 
Whenever you see these repeated Retrying... statements as above, what is happening is that although the contact has made it as far as being accepted by HRD Logbook (step 3), HRD Logbook itself for some reason or other has taken more than 10 seconds to actually store the contact in your MySQL database.  In the meantime, QSO Relay has given up trying to verify it as being there.
 
I am a little astonished I must say, that HRD Logbook is taking that long to write the contact.  My testing reveals that it can take up to 5 seconds when a Microsoft Access database is being used, but with SQL Server and MySQL the contact is always verified on the first attempt, or second attempt at worst - never 10 attempts without success.
 
This is a nuisance but bearable, if the contact does eventually end up in the backend database.  In the next release, I will make the number of verification attempts a user-configurable setting.  In the meantime, I suggest you restart HRD Logbook when this occurs.

73 Chris
VK2BYI
 


Re: HRD logging?

Chris VK2BYI
 
Edited

Hi Arnie,
The way contacts are logged is as follows:
  • JTAlert sends the contact to QSO Relay;
  • QSO Relay stores it in its database;
  • QSO Relay then relays it to HRD Logbook via a command line interface.
HRD Logbook has to be running in order for QSO Relay to be able to add a QSO.  The only method supported for writing QSOs into HRD Logbook is via a command line interface (CLI) that requires that HRD Logbook to be running.

If QSO Relay can't get a response from the HRD Logbook CLI, it caches the contact, and the next time you Synchronise Databases in QSO Relay, it will try multiple times to log the contact.  So, if you experience a temporary outage of HRD Logbook, your QSOs will not be lost.  Simply restart HRD Logbook, perform a Synchronise Database operation, and QSO Relay will try again to add any cached contacts into HRD Logbook.  However, this is a costly exercise - it can take many seconds to process each cached contact.  So in the normal course of events, you should always have HRD Logbook running.

The ADIF file is only used by QSO Relay to provide a complete extract from HRD Logbook for JTAlert to read duing its Scan Log and Update process to update your wanted alerts requirements.

73 Chris
VK2BYI
 

 


HRD logging?

AMP
 

Chris:

I want to make sure I understand the operation of QSO-RELAY correctly:
Does HRD logging have to be open for QSO-RELAY to be able to add a qso to it? Or does QSO-RELAY interact directly with the HRD logbook ADIF file without needing the logging program to be running?

Tnx de Arnie W8DU


Re: QSORelay and HRD will not log

Ian Morrow
 

Hi chris
I have uploaded the files to the Reported issue Uploads folder as you asked.
Hope this helps solve the problem for me.

73's Ian
MI1CCU/EI3HFB


Re: QSORelay and HRD will not log

Chris VK2BYI
 
Edited

Hi Ian,
I am not sure what might be happening, but you shouldn't have to recreate the SQLite file to get logging to work again.
So, reproduce the situation where the HRD logging is not working. Then:
  1. Tick the Enable Tracing checkbox in the QSO Relay options dialog to start a new session trace;
  2. Try to log a test contact or two;
  3. Un-tick the Enable Tracing checkbox to flush the session data and close the file;
  4. Zip up all the files from the QSO Relay AppData folder and upload the results to the Reported Issue Uploads folder, or email the zip file to me direct if you prefer.  You can get my email address from QRZ.com.

The session trace file will show me in detail what is happening from the contact being received from JTAlert through to it trying to be logged in HRD Logbook.

73 Chris

VK2BYI


QSORelay and HRD will not log

Ian Morrow
 

Hi Chris

 

Sorry to bother you but I am having bother with logging in HRD. Here is my setup software

Ham Radio Deluxe 6.4.0.647

JTAlertX 2.9.7

WSJT-X 1.7.0

QSORelay 1.3.6343.31566

Windows 10 64Bit PRO

 

I setup all the programmes as you said in you manual and everything works 100% (FANTASTIC SOFTWARE), but the problem is when I shut all the software down and the computer and comeback after a while.

When I start all up again HRD will not log at all.  I have changed nothing only switched everything off. I have tried to synchronise database again but it does not fix it!  I have been able to fix it but it is only temporary.  I have to delete the QSO RELAY SQLITE DATABASE, create a new database, and then synchronise the database and then it works 100% again until I shut all down again.

 

I will send you whatever Exception logs there are in the folder and also a Session Tracing Log that I created to your email if needed.

 

Best Regards

 

Ian MI1CCU/EI3HFB

 


Re: Finally, I think it is set up right accept for one thing

Chris VK2BYI
 

You're welcome.

73 Chris VK2BYI


Re: New version and DB

Antony
 

Hi Bob,

yes, that's what I did with mcafee. One can choose the time in multiples of 15 minutes chunks. During the 'off' time I added the file to the 'trusted list'. My first attempts without doing the above were unsuccessful as mcafee kept putting the file in quarantine!

This is  the first time I've had to do this. One keeps learning!

Regards, Antony G4CUS


Re: Finally, I think it is set up right accept for one thing

Bob Davet
 

Chris:

 

Thanks for being patient with me through this.

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris VK2BYI
Sent: Monday, May 22, 2017 8:14 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Finally, I think it is set up right accept for one thing

 

Great news Bob!

73 Chris
VK2BYI


Virus-free. www.avast.com