Date   

Re: New version and DB

Bob Davet
 

Anthony:

 

I have the same problem with AVAST.

There is a function in AVAST where you can turn it off for 10min.

I usually do that when I install programs from places that I have confidence in and I have no problems.

I then go back in and turn it back on or it will turn itself back on after the time limit expires.

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Antony
Sent: Sunday, May 21, 2017 9:26 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] New version and DB

 

Hi Chris,

just downloaded the latest versions of JTAlert and Relay. The only problem I had was with Mcafee which kept putting a JTAlert file in the quarantine folder. After a lot of reading I managed to get the file into Mcafee's 'trusted list'. Reading your very precise instructions I was successful with logging contacts into HRD without problem, including syncing the logs. 

Many thanks for a great program and all the work put into the precise instructions. Regards, Antony G4CUS

ps. I love the chart you sent out earlier giving the data flow


Virus-free. www.avast.com


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

Chris VK2BYI
 

Great news Bob!

73 Chris
VK2BYI


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

Bob Davet
 

Morris:

 

That was it!! Everything looks right and seems to be transferring back and forth between the data bases now.

That was the only thing that I did not do. Usually that is one of the first things I do.

Just missed it.

 

Thanks

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Morris Wideman via Groups.Io
Sent: Friday, May 19, 2017 6:36 PM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Finally, I think it is set up right accept for one thing

 

Hi Bob I had similar with my setup and shutting down HRD, Relay, JTalert and JT software then restarting everything and run scan again and see if this works hope that helps 73 wa4mit Morris


Virus-free. www.avast.com


Re: New version and DB

Chris VK2BYI
 

Thank you very much for your kind words.

I am glad QSO Relay is working well for you.

Enjoy!

Chris

VK2BYI


Re: sync fail

Chris VK2BYI
 

Well, then it must be a configuration issue.

Refer to the QSO Relay Settings and Data Flow diagram and double check all of your QSO Relay settings.

Don't worry about the IP Address of the PC itself, you must use an IP Address value 127.0.0.1, and TCP Port of 7826 to access HRD Logbook from QSO Relay as the following image shows..


Make sure that the Logbook Database: you have selected to upload contacts to QSO Relay, is the same database file you have selected in the Connection String: setting in QSO Relay.  For a detailed explanation on how you check that Logbook Database: and Connection String: are both referencing the same Access (.mdb), read this document: Configuring QSO Relay for Microsoft Access Databases

You can also follow the instructions in the Reporting an Issue, and send me that information if all else fails.

73 Chris


Re: sync fail

Chris VK2BYI
 

Correct, but I thought SV8JNL SV8JNL was trying to run the logbook on a different PC, but the post makes it clear that is not the case.


Re: sync fail

Jerry
 

127.0.0.1 is a reserved IP address which systems interpret as meaning "this device".

73,
Jerry KB2GCG


- "Defeat lasts one day, giving up lasts a lifetime."

On May 21, 2017, at 10:28 PM, SV8JNL SV8JNL <sv8jnl@...> wrote:

Thank you for your answer but all programs are in the same pc i dont know why thr hrd uses the ip of the pc and not the 127.0.0.1. All the apps are in the same pc. I use microsoft access mdb.

With the previus version of qso relay  everything was workig fine.




Sent with SolMail App

--------- Original Message ---------
From: Chris VK2BYI
To: vk2byi-qsorelay@groups.io
Date: Mon May 22 05:11:51 EEST 2017
Subject: Re: [vk2byi-qsorelay] sync fail

Yes, it is critical.  QSO Relay uses the Logbook API command line interface (CLI) to log contacts in HRD Logbook via 127.0.0.1 port 7826.

It should be no problem as far as the download from HRD Logbook to QSO Relay is concerned, especially if you are using Microsoft SQL Server or Oracle MySQL for the database server, as you can specify the server name in the Connection String (OLEDB) settings.  If you are using a Microsoft Access (.mdb) file for the database in HRD Logbook, you will have to share that file on your local area network so it can be accessed from the PC running QSO Relay. That should work, but I haven't personally tried that.

However, I do not know how you can access the CLI from a different PC. There does not appear to be an option in HRD Logbook settings anywhere, where you change the values of 127.0.0.1 and port 7826 used by the CLI.  This means that QSO Relay and HRD Logbook need to be on the same PC.

You might want to post a question on the Ham Radio Deluxe Support Forum and ask if anyone knows if the Logbook API CLI interface can be accessed from another PC.

If anyone reading this knows, please let us know, as I am only too willing to support it if it can be done.

73 Chris
VK2BYI


Re: sync fail

SV8JNL SV8JNL
 

Thank you for your answer but all programs are in the same pc i dont know why thr hrd uses the ip of the pc and not the 127.0.0.1. All the apps are in the same pc. I use microsoft access mdb.

With the previus version of qso relay  everything was workig fine.




Sent with SolMail App

--------- Original Message ---------
From: Chris VK2BYI
To: vk2byi-qsorelay@groups.io
Date: Mon May 22 05:11:51 EEST 2017
Subject: Re: [vk2byi-qsorelay] sync fail

Yes, it is critical.  QSO Relay uses the Logbook API command line interface (CLI) to log contacts in HRD Logbook via 127.0.0.1 port 7826.

It should be no problem as far as the download from HRD Logbook to QSO Relay is concerned, especially if you are using Microsoft SQL Server or Oracle MySQL for the database server, as you can specify the server name in the Connection String (OLEDB) settings.  If you are using a Microsoft Access (.mdb) file for the database in HRD Logbook, you will have to share that file on your local area network so it can be accessed from the PC running QSO Relay. That should work, but I haven't personally tried that.

However, I do not know how you can access the CLI from a different PC. There does not appear to be an option in HRD Logbook settings anywhere, where you change the values of 127.0.0.1 and port 7826 used by the CLI.  This means that QSO Relay and HRD Logbook need to be on the same PC.

You might want to post a question on the Ham Radio Deluxe Support Forum and ask if anyone knows if the Logbook API CLI interface can be accessed from another PC.

If anyone reading this knows, please let us know, as I am only too willing to support it if it can be done.

73 Chris
VK2BYI


Re: sync fail

Chris VK2BYI
 

Yes, it is critical.  QSO Relay uses the Logbook API command line interface (CLI) to log contacts in HRD Logbook via 127.0.0.1 port 7826.

It should be no problem as far as the download from HRD Logbook to QSO Relay is concerned, especially if you are using Microsoft SQL Server or Oracle MySQL for the database server, as you can specify the server name in the Connection String (OLEDB) settings.  If you are using a Microsoft Access (.mdb) file for the database in HRD Logbook, you will have to share that file on your local area network so it can be accessed from the PC running QSO Relay. That should work, but I haven't personally tried that.

However, I do not know how you can access the CLI from a different PC. There does not appear to be an option in HRD Logbook settings anywhere, where you change the values of 127.0.0.1 and port 7826 used by the CLI.  This means that QSO Relay and HRD Logbook need to be on the same PC.

You might want to post a question on the Ham Radio Deluxe Support Forum and ask if anyone knows if the Logbook API CLI interface can be accessed from another PC.

If anyone reading this knows, please let us know, as I am only too willing to support it if it can be done.

73 Chris
VK2BYI


Re: New version and DB

Antony
 

Hi Chris,

just downloaded the latest versions of JTAlert and Relay. The only problem I had was with Mcafee which kept putting a JTAlert file in the quarantine folder. After a lot of reading I managed to get the file into Mcafee's 'trusted list'. Reading your very precise instructions I was successful with logging contacts into HRD without problem, including syncing the logs. 

Many thanks for a great program and all the work put into the precise instructions. Regards, Antony G4CUS

ps. I love the chart you sent out earlier giving the data flow


Re: sync fail

SV8JNL SV8JNL
 

PLease could you tell me if its critical that the ham radio deluxe ip server rus not in 127.0.0.1 but in 192.168.10.10?


locked Re: QSO Relay Settings and Data Flow

Chris VK2BYI
 
Edited

PS:  The group email that was sent for the first post in this topic, contains the full resolution image of 1608 x 1250 pixels.  At this resolution it prints clearly enough on A4 size paper, and I hope US-Letter, so that it can be read.

For those who do not subscribe to forum emails, you can download the full resolution image from here: QSO Relay Settings and Data Flow

73 Chris
VK2BYI


locked QSO Relay Settings and Data Flow

Chris VK2BYI
 

Here is graphical checklist that will help you to correctly configure JTAlert and QSO Relay:

The arrows point the in direction of the two data flows (top-left):

  1. Log QSO to HRD Logbook;
  2. Synchronise Databases in QSO Relay, followed by Scan Log and Update In JTAlert.

The data flow steps labelled A, B, C and D (top-left), depend upon the correct settings in QSO Relay, also labelled A, B, C and D (top-right).

Also, note the settings labelled A and D (top-right), need to match the corresponding settings in JTAlert, also labelled A (bottom-left), and D (bottom-right).

73 Chris
VK2BYI


Re: sync fail

Chris VK2BYI
 

Please read the post on Reporting an issue.  We need to see the files written by QSO Relay to see what might be wrong.

73 Chris
VK2BYI


Re: sync fail

SV8JNL SV8JNL
 

Hello i found the dublicate this is ok now .

I have anothor problem now i do everything you say in manual for 1.3 and jtalert 2.9.7 when i press sync a message sais its synced but nothing synced. when i press to delete a contoct nothing come up and when i fill a callsing all tis error came up


Ανατρέξτε στο τέλος αυτού του μηνύματος για περισσότερες πληροφορίες σχετικά με την κλήση του 

εντοπισμού σφαλμάτων just-in-time (JIT) αντί για αυτό το παράθυρο διαλόγου.


************** Κείμενο εξαίρεσης **************

System.NullReferenceException: Δεν έχει οριστεί αναφορά αντικειμένου σε μια παρουσία αντικειμένου.

   σε QSORelay.DeleteContact.SearchTextChanged(Object sender, EventArgs e)

   σε System.Windows.Forms.Control.OnTextChanged(EventArgs e)

   σε System.Windows.Forms.TextBoxBase.OnTextChanged(EventArgs e)

   σε System.Windows.Forms.TextBoxBase.WmReflectCommand(Message& m)

   σε System.Windows.Forms.TextBoxBase.WndProc(Message& m)

   σε System.Windows.Forms.TextBox.WndProc(Message& m)

   σε System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   σε System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   σε System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)



************** Συγκροτήσεις που έχουν φορτωθεί **************

mscorlib

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

----------------------------------------

QSORelay

    Έκδοση συγκρότησης: 1.3.6343.31566

    Έκδοση Win32: 1.3

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/QSORelay.exe

----------------------------------------

MutexManager

    Έκδοση συγκρότησης: 1.0.0.0

    Έκδοση Win32: 1.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/MutexManager.DLL

----------------------------------------

System.Windows.Forms

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2094.0 built by: NET47REL1LAST

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2093.0 built by: NET47REL1LAST

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

NLog

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.4.5069

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/NLog.DLL

----------------------------------------

System.Configuration

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Core

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2093.0 built by: NET47REL1LAST

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

System.Xml

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.ServiceModel

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll

----------------------------------------

System.Data

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

System.Runtime.Serialization

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll

----------------------------------------

NLog.Windows.Forms

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.2.3.167

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/NLog.Windows.Forms.DLL

----------------------------------------

Devart.Data.Universal

    Έκδοση συγκρότησης: 3.70.1359.0

    Έκδοση Win32: 3.70.1359.0

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/Devart.Data.Universal.DLL

----------------------------------------

Microsoft.GeneratedCode

    Έκδοση συγκρότησης: 1.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

Devart.Data

    Έκδοση συγκρότησης: 5.0.1654.0

    Έκδοση Win32: 5.0.1654.0

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/Devart.Data.DLL

----------------------------------------

Syncfusion.Shared.Base

    Έκδοση συγκρότησης: 14.4460.0.15

    Έκδοση Win32: 14.4460.0.15

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/Syncfusion.Shared.Base.DLL

----------------------------------------

System.Transactions

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll

----------------------------------------

System.Data.resources

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.resources/v4.0_4.0.0.0_el_b77a5c561934e089/System.Data.resources.dll

----------------------------------------

System.Numerics

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll

----------------------------------------

System.EnterpriseServices

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll

----------------------------------------

Accessibility

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

----------------------------------------

mscorlib.resources

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_el_b77a5c561934e089/mscorlib.resources.dll

----------------------------------------

System.resources

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.resources/v4.0_4.0.0.0_el_b77a5c561934e089/System.resources.dll

----------------------------------------

System.Data.SQLite

    Έκδοση συγκρότησης: 1.0.105.0

    Έκδοση Win32: 1.0.105.0

    CodeBase: file:///C:/Program%20Files%20(x86)/VK2BYI/QSO%20Relay/System.Data.SQLite.DLL

----------------------------------------

System.Windows.Forms.resources

    Έκδοση συγκρότησης: 4.0.0.0

    Έκδοση Win32: 4.7.2046.0 built by: NET47REL1

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_el_b77a5c561934e089/System.Windows.Forms.resources.dll

----------------------------------------


************** Εντοπισμός σφαλμάτων JIT **************

Για να ενεργοποιήσετε τον εντοπισμό σφαλμάτων just-in-time (JIT), το αρχείο .config

για αυτή την εφαρμογή ή για τον υπολογιστή (machine.config)

πρέπει να έχει για το jitDebugging την τιμή που έχει οριστεί στην ενότητα system.windows.forms.

Η εφαρμογή πρέπει επίσης να μεταγλωττιστεί

με ενεργοποιημένο τον εντοπισμό σφαλμάτων.


Για παράδειγμα:


<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>


Όταν είναι ενεργοποιημένος ο εντοπισμός σφαλμάτων JIT, οποιαδήποτε εξαίρεση

που δεν είναι δυνατό να αντιμετωπιστεί θα στέλνεται στο πρόγραμμα εντοπισμού σφαλμάτων JIT που είναι καταχωρημένο στον υπολογιστή

αντί να αντιμετωπίζεται μέσω αυτού του παραθύρου διαλόγου.




Re: sync fail

Chris VK2BYI
 

Look in the Documents/QSORelay folder and you see a file call Sync Report yyMMddHHmmss.txt.  Can you share that with us?

I also encourage everyone when reporting an issue, to first of all read the post on Reporting an issue.  Following the advice in that post will make it significantly easier for us to diagnose the root cause of a problem.

73 Chris
VK2BYI


sync fail

SV8JNL SV8JNL
 

I yry to setup the qsorelay following the manual.When i try for the first time to sync a message sais that i have dublicates. I dont have. Any idea to find which qso have the problem?


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

Chris VK2BYI
 

Hi Bob,

Please read the sticky post on Reporting an Issue and send me the files I need to properly diagnose your problem.

No need to send the Access database this time, just the contents of the QSO Relay AppData folder as documented in the Reporting an Issue post.

Chris VK2BYI


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

Chris VK2BYI
 

Good advice Morris, thanks.


Re: JT Alert Scan Log & Update

Chris VK2BYI
 

Hi Karel,

Thanks for the feedback and you are most welcome.

73 Chris
VK2BYI