DX Keeper - LOTW QSL sync problem


tomcromack@btinternet.com
 

Hi,
I am a long time very satisfied user of DX Lab Suite but have recently changed QTH which has resulted in change callsign. Have updated LOTW, and new certificated loaded.
Have updated DX Keeper with new info.
Uploaded trial number of QSOs. Reached LOTW and processed as checked by loging in to LOTW.
DX Keeper has sync LOTW QSO,s but every time I try to sync LOTW QSLs DXKeeper  says DX Keeper checking LOTW QSL data then after a few seconds (not responding)
programme freezes and I have to close to get control back.
Have QSL config set to LOTW

Have looked at the error log which says.
Programme error 482 in module DXQSLModule
Update EnvelopePrinter Qualitystate=0 Printer error
Printer= Kodak ESP1.2+2420
I=0
Programme error 9 in module QSLSetup. Initialize Envelope Paper Size Array, State=7
I=1024 Ing Paper Count=-1, Ing Counter=0
Paper Code=0 Subscript out of range

The printer noted above was disposed of during house move and so I have tried to remove to see if this is the problem.
I selected nil (blank line) in select printer config but no change in situation and everytime I reloaded DXK it still shows the Kodak printer.

I have tried to use help files but cannot find any guidance on how to remove printer.

I would be very grateful for any guidance you can give me to get this part of DX Keeper working

Many thanks
Tom Cromack G0FGI


Dave AA6YQ
 

+ AA6QY comment sbelow

I am a long time very satisfied user of DX Lab Suite but have recently changed QTH which has resulted in change callsign. Have updated LOTW, and new certificated loaded.
Have updated DX Keeper with new info.
Uploaded trial number of QSOs. Reached LOTW and processed as checked by loging in to LOTW.
DX Keeper has sync LOTW QSO,s but every time I try to sync LOTW QSLs DXKeeper says DX Keeper checking LOTW QSL data then after a few seconds (not responding) programme freezes and I have to close to get control back.
Have QSL config set to LOTW

Have looked at the error log which says.
Programme error 482 in module DXQSLModule Update EnvelopePrinter Qualitystate=0 Printer error Printer= Kodak ESP1.2+2420
I=0
Programme error 9 in module QSLSetup. Initialize Envelope Paper Size Array, State=7
I=1024 Ing Paper Count=-1, Ing Counter=0 Paper Code=0 Subscript out of range

The printer noted above was disposed of during house move and so I have tried to remove to see if this is the problem.
I selected nil (blank line) in select printer config but no change in situation and everytime I reloaded DXK it still shows the Kodak printer.

I have tried to use help files but cannot find any guidance on how to remove printer.

I would be very grateful for any guidance you can give me to get this part of DX Keeper working


+ Let's focus first on the "sync LOTW QSLs" problem. Please do the following:

1. terminate all applications

2. reboot Windows into "Safe mode with networking"

3. start DXKeeper

4. invoke "Sync LoTW QSLs"

+ What happens?

73,

Dave, AA6YQ


tomcromack@btinternet.com
 

Hi Dave,
Many thanks for your rapid response.
I have done as you suggested.
Result :-
When I invoke 'Sync LoTW QSLs'
DX Keeper says ....Checking LoTW QSL Data
then after 2 or 3 seconds
Checking LoTW QSL Data (Not responding)
Then as before have to close DX keeper to get back control.
The error message generated is similar to before....
28-Oct-2018 11:15:13 > DXKeeper version 14.6.2
28-Oct-2018 11:15:13 > App.Path          : C:\DXLab\DXKeeper
28-Oct-2018 11:15:13 > App.exe           : DXKeeper
28-Oct-2018 11:15:13 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
28-Oct-2018 11:15:13 > Operating System  : Windows 10 Home (64-bit) build 17134
28-Oct-2018 11:15:13 > Locale ID         : 2057 (0x809)
28-Oct-2018 11:15:13 > ANSI CodePage     : 1252
28-Oct-2018 11:15:13 > OEM CodePage      : 850
28-Oct-2018 11:15:13 > Country           : United Kingdom
28-Oct-2018 11:15:13 > Language          : English
28-Oct-2018 11:15:13 > DecimalSeparator  : .
28-Oct-2018 11:15:13 > ThousandSeparator : ,
28-Oct-2018 11:15:13 > DXLab Apps        : 
28-Oct-2018 11:15:17 > Monitors          : 1
28-Oct-2018 11:15:17 > Monitor 1
28-Oct-2018 11:15:17 >    width          : 1024
28-Oct-2018 11:15:17 >    height         : 768
28-Oct-2018 11:15:17 >    dimensions     : (0, 0)-(1024, 768)
28-Oct-2018 11:15:17 > program error 482 in module DXQSLModule.UpdatePrinterQuality, State = 0: Printer error
28-Oct-2018 11:15:17 >    Printer = KodakESP1.2+2420
28-Oct-2018 11:15:17 >    I = 0
28-Oct-2018 11:15:17 >    Actual Quality = 0
28-Oct-2018 11:15:17 > program error 482 in module DXQSLModule.UpdateLabelPrinterQuality, State = 0: Printer error
28-Oct-2018 11:15:17 >    Printer = KodakESP1.2+2420
28-Oct-2018 11:15:17 >    I = 0
28-Oct-2018 11:15:17 >    Actual Quality = 0
28-Oct-2018 11:15:17 > program error 9 in module QSLSetup.InitializeLabelPaperSizeArray, State = 7, I = 1024, lngPaperCount = -1, lngCounter = 0, PaperCode = 0: Subscript out of range
28-Oct-2018 11:15:17 > program error 482 in module DXQSLModule.UpdateEnvelopePrinterQuality, State = 0: Printer error
28-Oct-2018 11:15:17 >    Printer = KodakESP1.2+2420
28-Oct-2018 11:15:17 >    I = 0
28-Oct-2018 11:15:17 >    Actual Quality = 0
28-Oct-2018 11:15:17 > program error 9 in module QSLSetup.InitializeEnvelopePaperSizeArray, State = 7, I = 1024, lngPaperCount = -1, lngCounter = 0, PaperCode = 0: Subscript out of range
 
28-Oct-2018 11:17:35 > DXKeeper version 14.6.2
28-Oct-2018 11:17:35 > App.Path          : C:\DXLab\DXKeeper
28-Oct-2018 11:17:35 > App.exe           : DXKeeper
73, Tom G0FGI


Dave AA6YQ
 

OK. Please do the following:

1. if you haven't rebooted Windows normally, do so

2. start DXKeeper

3. on the Configuration window's General tab, check the "Log debugging info" box

4. terminate DXKeeper

5. start DXKeeper

6. after DXKeeper initializes, select the Main window's QSL tab, and click the "Sync LoTW QSLs" button

7. wait 1 hour

8. if the operation has not completed, terminate DXKeeper

9. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ



Hi Dave,
Many thanks for your rapid response
I have done as you suggested.
Result :-
When I invoke 'Sync LoTW QSLs'
DX Keeper says ....Checking LoTW QSL Data then after 2 or 3 seconds Checking LoTW QSL Data (Not responding) Then as before have to close DX keeper to get back control.
The error message generated is similar to before....

28-Oct-2018 11:15:13 > DXKeeper version 14.6.2
28-Oct-2018 11:15:13 > App.Path : C:\DXLab\DXKeeper
28-Oct-2018 11:15:13 > App.exe : DXKeeper
28-Oct-2018 11:15:13 > Module : C:\DXLab\DXKeeper\DXKeeper.exe
28-Oct-2018 11:15:13 > Operating System : Windows 10 Home (64-bit) build 17134
28-Oct-2018 11:15:13 > Locale ID : 2057 (0x809)
28-Oct-2018 11:15:13 > ANSI CodePage : 1252
28-Oct-2018 11:15:13 > OEM CodePage : 850
28-Oct-2018 11:15:13 > Country : United Kingdom
28-Oct-2018 11:15:13 > Language : English
28-Oct-2018 11:15:13 > DecimalSeparator : .
28-Oct-2018 11:15:13 > ThousandSeparator : ,
28-Oct-2018 11:15:13 > DXLab Apps :
28-Oct-2018 11:15:17 > Monitors : 1
28-Oct-2018 11:15:17 > Monitor 1
28-Oct-2018 11:15:17 > width : 1024
28-Oct-2018 11:15:17 > height : 768
28-Oct-2018 11:15:17 > dimensions : (0, 0)-(1024, 768)
28-Oct-2018 11:15:17 > program error 482 in module DXQSLModule.UpdatePrinterQuality, State = 0: Printer error
28-Oct-2018 11:15:17 > Printer = KodakESP1.2+2420
28-Oct-2018 11:15:17 > I = 0
28-Oct-2018 11:15:17 > Actual Quality = 0
28-Oct-2018 11:15:17 > program error 482 in module DXQSLModule.UpdateLabelPrinterQuality, State = 0: Printer error
28-Oct-2018 11:15:17 > Printer = KodakESP1.2+2420
28-Oct-2018 11:15:17 > I = 0
28-Oct-2018 11:15:17 > Actual Quality = 0
28-Oct-2018 11:15:17 > program error 9 in module QSLSetup.InitializeLabelPaperSizeArray, State = 7, I = 1024, lngPaperCount = -1, lngCounter = 0, PaperCode = 0: Subscript out of range
28-Oct-2018 11:15:17 > program error 482 in module DXQSLModule.UpdateEnvelopePrinterQuality, State = 0: Printer error
28-Oct-2018 11:15:17 > Printer = KodakESP1.2+2420
28-Oct-2018 11:15:17 > I = 0
28-Oct-2018 11:15:17 > Actual Quality = 0
28-Oct-2018 11:15:17 > program error 9 in module QSLSetup.InitializeEnvelopePaperSizeArray, State = 7, I = 1024, lngPaperCount = -1, lngCounter = 0, PaperCode = 0: Subscript out of range

28-Oct-2018 11:17:35 > DXKeeper version 14.6.2
28-Oct-2018 11:17:35 > App.Path : C:\DXLab\DXKeeper
28-Oct-2018 11:17:35 > App.exe : DXKeeper
73, Tom G0FGI


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Fred Roberts
 

Dave,
       I am very new to the DX labs suite of programs....actually still setting it up with the help of a long time user of the programs, and one of my Elmers. Unfortunately, he didn't convince me to start using DXkeeper until I had 10,000+ QSOs in the log. I imported my log in ADIF format with no problems, and then I tried the Sync LoTW QSLs button; the program waited 2 or 3 seconds and then I received the Program not responding error  message, as the previous poster did. The Sync LoTW QSOs button works, as does the Update from LoTW button - (which by the way for 10,000+ records took about 8 hours). Can you help a newbie to the group with an idea as to what I've done wrong in setting things up?
Thanks,
Fred
WB4QOC


Fred Roberts
 

Addendum.....the only other clue that i have is that on the Log QSOs page, in the QSL section, I have a flashing blue "my QTH" message in front if the drop down box. If I press the down arrow, I can choose my call sign, but the drop down box reverts to a nil entry....it will not permit me to populate that field....sorry for not including that in the first post.
73,
Fred
WB4QOC


Dave AA6YQ
 

+ AA6YQ comments below

I am very new to the DX labs suite of programs....actually still setting it up with the help of a long time user of the programs, and one of my Elmers. Unfortunately, he didn't convince me to start using DXkeeper until I had 10,000+ QSOs in the log. I imported my log in ADIF format with no problems, and then I tried the Sync LoTW QSLs button; the program waited 2 or 3 seconds and then I received the Program not responding error message, as the previous poster did.

The Sync LoTW QSOs button works, as does the Update from LoTW button - (which by the way for 10,000+ records took about 8 hours). Can you help a newbie to the group with an idea as to what I've done wrong in setting things up?

+ First, the appearance of "Not responding" in DXKeeper's Title bar means "waiting for input or output" - in this case, waiting for LoTW to supply an ADIF file specifying all of your QSLs. When this "Micosoft-speak message" appears, ignore it and let the operation run to completion.

+ The "Update from LoTW" function directs LoTW to report the status of each QSO in the Log Page Display - one at a time (and is thus much slower). If you've already done this for all 10,000 of your logged QSOs, there is no need to invoked "Sync LoTW QSLs" with the date beneath it set to the beginning of time. On the Main window's QSL tab,

1. set the "QSO Via" panel to LoTW

2. double-click the date under the "Sync LotW QSLs" button

3. In the small "LoTW QSL Synchronization" window that appears, change the date to

2021-01-01

and click the OK button

4. click the "Sync LotW QSLs" button

+ This will direct LotW to report any QSLs that have arrived since the beginning of the year, providing some overlap in case new QSLs have arrived since you completed the "Update from LoTW" operation above.

+ From now on, just click "Sync LoTW QSLs", and your Log will be updated to reflect new LoTW confirmatins.

73,

Dave, AA6YQ


Dave AA6YQ
 

+ AA6YQ comments below

Addendum.....the only other clue that i have is that on the Log QSOs page, in the QSL section, I have a flashing blue "my QTH" message in front if the drop down box. If I press the down arrow, I can choose my call sign, but the drop down box reverts to a nil entry....it will not permit me to populate that field....sorry for not including that in the first post.

+ On the Main window's "my QTHs" tab, how many QTHs have you defined?

73,

Dave, AA6YQ


Fred Roberts
 

Dave,
     I only have 1 MyQTHID set. It is set to my call, WB4QOC.
Fred
PS....thank you for your very quick response!





Sent from my phone.....Fred


On Sat, Mar 13, 2021, 6:26 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Addendum.....the only other clue that i have is that on the Log QSOs page, in the QSL section, I have a flashing blue "my QTH" message in front if the drop down box. If I press the down arrow, I can choose my call sign, but the drop down box reverts to a nil entry....it will not permit me to populate that field....sorry for not including that in the first post.

+ On the Main window's "my QTHs" tab, how many QTHs have you defined?

       73,

              Dave, AA6YQ









Dave AA6YQ
 

+ AA6YQ comments below
I only have 1 MyQTHID set. It is set to my call, WB4QOC

+ Were all 10,000 of your logged QSOs made from that myQTH ?

      Dave


Fred Roberts
 

Dave....
       Yes. All of them made from the same call, but some of them were made from a different grid square. Is that where the problem lies?
Fred
WB4QOC



Sent from my phone.....Fred


On Sat, Mar 13, 2021, 7:02 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I only have 1 MyQTHID set. It is set to my call, WB4QOC

+ Were all 10,000 of your logged QSOs made from that myQTH ?

      Dave


Dave AA6YQ
 

+ AA6YQ comments below
Yes. All of them made from the same call, but some of them were made from a different grid square.
+  You should define a myQTH for each physical location from which you made QSOs -- independent of the callsign you employed over the air. I suggest using a town name or county name as the myQTH ID. Let me know when you have your two myQTHs defined, and we'll proceed to the next step, which is updating your logged QSOs to reflect the correct myQTH ID
Is that where the problem lies?
+ The flashing myQTH ID label is DXKeeper pointing out that you had not specified a myQTH ID in that QSO. We'll be taking care of that.

        73,

              Dave, AA6YQ


Fred Roberts
 

Dave....
      Thank you for your quick reply....again....I apologize for not getting back to you sooner.....sometimes my 10 year old grandson can get a bit demanding. He is going back to 'Real School' starting tomorrow.
      Thank you for the my QTH fix. No problems now.
Fred
WB4QOC



Sent from my phone.....Fred


On Sat, Mar 13, 2021, 7:41 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
Yes. All of them made from the same call, but some of them were made from a different grid square.
+  You should define a myQTH for each physical location from which you made QSOs -- independent of the callsign you employed over the air. I suggest using a town name or county name as the myQTH ID. Let me know when you have your two myQTHs defined, and we'll proceed to the next step, which is updating your logged QSOs to reflect the correct myQTH ID
Is that where the problem lies?
+ The flashing myQTH ID label is DXKeeper pointing out that you had not specified a myQTH ID in that QSO. We'll be taking care of that.

        73,

              Dave, AA6YQ