Date   
locked Re: QSO Relay version 1.3

Morris WA4MIT
 
Edited

Chris I could not get the DB to work at all I have tried uninstalling and reinstall program everything seems to indicate it was working but when look at delete DB there is nothing there. I have now reverted back to 1.1 again and it has the data base and logs to HRD .647 this takes an hour to run the sync. The only thing I can pinpoint as different is I am using the Maria DB in HRD. See my earlier post with info.  OK I put this up before seeing your latest about my problem will look into what you say and let you know back but it is working OK with version 1.1 why is that?. Thanks wa4mit

ok the UT2IJ had some goofy number in that column so after correcting this I will try again and let you know what happens keep your fingers crossed hi hi 73 thanks wa4mit


locked Re: QSO Relay version 1.3

Chris VK2BYI
 

The synchronise database operation in version 1.1 downloaded all rows from HRD Logbook and then updated existing rows, and inserted new rows, in the SQLite database as individual transactions which made the performance terrible on larger datasets.  All of the rows but one or two may have been processed successfully, but a missing row or two probably went unnoticed.

But as I said, in order to improve the improve the performance in version 2, we switched to a truncate, then insert all rows in a single transaction model.  The performance improved dramatically, but if one bad row causes an error, then none get inserted.  A small price to pay for a dramatic improvement performance I think, but it also means I have to get the code to handle all types of error conditions, and obviously you have something in your database that my code can't handle - and it should.

I test with a row 100,000 test database that takes about 3 minutes to sync without any issues at all.  So I am keen to get to the bottom of this.

I forgot to ask if you could also zip up all of the '*.log' files, and the 'settings.config' file in your AppData folder and email them to me?

73 Chris
Vk2BYI


locked Re: QSO Relay version 1.3

Chris VK2BYI
 

Crossed they are!  Let me know the goofy value too please. :)

locked Re: QSO Relay version 1.3

Mike Davies <face@...>
 

Chris,

Thanks I've sent three files, session report, exception and zipped logbook .mdb to your email address as given in QRZ.com.  Looking forward to an answer.  Remember that this worked in v1.0.

Regards
--
Mike, G0KAD

locked Re: QSO Relay version 1.3

Morris WA4MIT
 

Partial success I was able to create a DB and it seems to have all my log in it this all went smooth, in JTAlert I setup for the ADI log it is pointed to the "log.adi" in the app data qso relay folder however a JTAlert scan says I have no states, countries etc confirmed so it is like day one on JT mode. I will send you the screen shots I made of my setup in Alert and Relay and my data base zipped if I can. The sync went without any errors in just a few seconds. In the UT7IJ log entry the number was like .9410000002300 something like that I used bulk edit to erase and I had this column showing and this was the only entry that had anything in this column now how did that get there?. Thanks Chris 73 wa4mit Morris

 

locked Re: QSO Relay version 1.3

Morris WA4MIT
 

Chris I shut everything down left home for about 3 hours and when returned restarted HRD/JTAlert did a alert scan and this time it worked. Did not change any settings. Have made a few contacts now and everything seems to function normally logging OK. I sent zipped files to your personal email. Appreciate your help and the QSO Relay software it does a great job.

73 Morris wa4mit 

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

That is great news Morris.  I am pleased you have it all working now.

I think it is a good idea anytime you change configuration settings, to restart all of the applications so that they all start afresh with the new configuration.  So when you returned and restarted HRD/JTAlert etc., it started working correctly.

I also checked the screen capture you sent of your JTAlert and QSO Relays settings, and they look correct to me.

Thanks for providing the other items I requested.  I will use it to make QSO Relay more resilient against 'goofy' data and make it more stable.

How that value got into RX Power, I have no idea either.  But regardless, it is a valid floating point number and the code should handle it.  It will in the next release.

Thanks for your patience and assistance.

73 Chris
VK2BYI

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

You're welcome Danny.  73 Chris

locked Reporting an Issue - MUST READ

Chris VK2BYI
 
Edited

If you encounter a problem, before reporting the issue via our support forum, please read the following information.  You will then be able to provide us with technical information that will help to diagnose and resolve any coding issues more quickly.

Firstly, read the documents available in the Files folder of the forum, as a solution to your problem may be found there.  Also, search the message topics posted by other forum members, as a solution to your problem may be found there as well.

If you still cannot find a resolution, then follow these steps:

        1.  If an application error occurs, an exception log file will be automatically created using the following name format:

       Exception yyyy-MM-dd.log

       where yyyy-MM-dd is the current local date

        2.  If you can repeat the process that causes an error, refer to the Session Tracing section in the QSO Relay document on how to create a session log file.

        3.  Then repeat the process with session tracing enabled.

        4.  Be sure to uncheck the Enable tracing checkbox and click the Close button in the QSO Relay Options dialog when done. This will ensure that the full session tracing information is written and the file closed.

        5.  The exception and session tracing log files are written to the following folder:

       C:\Users\<your username>\AppData\Roaming\VK2BYI\QSORelay\

        6.  Zip up all the files from this folder, and send an email to me (my email address is on my QRZ.com page) explaining the issue you are encountering, and be sure to attach the zipped files.

        7.  You may also want to include a zipped copy of your HRD Logbook as an Access database (*.mdb) file, if that is possible.  I will keep the content confidential, and I will destroy the file when the issue has been resolved.

        8.  If the attachment(s) are too big to be sent via email, you can post it to the files section in our support forum instead.

Thank you,
Chris VK2BYI

Re: JT Alert Scan Log & Update

zs6wn@...
 

Hi Chris, tnx a lot.

I followed the instruction before my post but just to be sure I double checked and all was exactly as per your instructions.

I sync the database once again and then all was fine as before.

What went wrong earlier this week seems a mystery (in IT terms "a hidden feature").

Thanks for your patience.

73 de ZS6WN

Karel


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

Bob Davet
 

Got all the files pointing to the right direction.

Running JT65-HF V4

JTAlert V2.9.7

QSORelay V1.3.6343.31566


Using HRD logging. When I make a contact and log it it goes into my HRD log very quickly.

What I am not seeing is my contacts, countries and other stuff like that, that I have already contacted show up right in JTAlert.

Seem to be showing in JT65-HF correctly, I see the ones I just contacted today there as qso b4.

But that same ontact in JTAlert shows like I never contacted them before.


It seems like there is something missing coming back from my HRD log.

Is there a setting that I have missed?? I followed the new setup PDF and don't think I missed anything.

I selected the Standard ADIF File in JTAlert for logging. Set up a file name for it.

Selected the same file in QSORelay for JTAlert ADIF file name.

I even tried San Log and Update in JTAlert thinking that might update things but it up dated but I'm still not getting the feed back from my HRD log.

I also tried synchronizing the database in QSORelay after making these contacts just to see if that made a difference but it didn't.

It seems like JTAlert is not getting log feedback from the HRD and QSORelay logs so it can update its log.


Bob

W8RID


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

Morris WA4MIT
 

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

Re: JT Alert Scan Log & Update

Chris VK2BYI
 

Hi Karel,

Thanks for the feedback and you are most welcome.

73 Chris
VK2BYI

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

Chris VK2BYI
 

Good advice Morris, thanks.

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

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: 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

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
 

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

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