Date   

Re: DXKeeper 16.1.0 is available

Jay KA9CFD
 

Dave I have several contacts logged as Q65 mode in DXkeeper prior to your update. eQSL still does not accept them as is. eQSL say they will accept the QSO's as MFSK with submode Q65. Do these prior contacts need to be modified so they can be uploaded to eQSL? Or should I just wait for eQSL to update their approved mode list?

On another note, I noticed overnight that TQSL has updated their configuration file and now accepts Q65 without having to map it to DATA prior to uploading to LOTW. I probably need to filter my log for Q65 contacts and upload them again with the Q65 mode rather than DATA.

Thanks and 73, 
Jay KA9CFD


Filtering SC for special callsigns by mode

Tim K9WX
 

I have been using the “Identifying Special Callsigns” feature (http://dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm) of SpotCollector with good success, but I wonder if there is some beneficial additional functionality available that I am missing.

 

I would like SC to display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode, in pursuit of CWops awards, along with any spots relevant to my DXCC or Challenge objectives without regard to band or mode.

 

Using the CWops roster as the Leaderboard special callsign list, I can display spots for all CWops members on unworked bands along with spots needed for DXCC or Challenge objectives, but the spot database display shows this for all modes and not just CW.  So, in the case of CWops members, I end up seeing many spots for modes that are not of interest.

 

If I invoke the Mode filter and set it for CW, then SC displays only the needed entries for CW, which works fine for the CWops awards, but I will miss other desirable entries such as an ATNO on FT8.

 

The ideal solution would be to allow me to further filter the Leaderboard spot displays by mode so that it contributes only the CWops counters that I need to the display, in conjunction with the display of other spots I need for DXCC and Challenge goals regardless of mode.

 

Is there a way to do this in the existing program?

 

Tim K9WX


Dxcluster ON0DXK-5 cprrect adress

Roland Huysentruyt
 

Hello

Please note correct adress for ON0DXK-5.

on0dxk.dyndns.org  ( port 8000 ) 

Do not use anymore  193.191.136.222 .

ipadress  soon  no more static.

73

Roland ON6HH ,sysop ON0DXK-5


Re: DXKeeper 16.1.0 is available

Dave AA6YQ
 

+ AA6YQ comments below

here is the tail of my DXKeeper ErrorLog.txt:

2021-04-06 19:26:42.417 > program error 3050 in module DXLogModule.OpenLog, state = 15, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not lock file.
2021-04-06 23:06:10.049 > Common.Terminate: DXKeeper shutdown

+ This occurred while you were running the previous version of DXKeeper, 16.0.7.


2021-04-21 10:22:35.877 > program error 3024 in module DXLogModule.OpenLog, state = 14, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not find file 'C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb'.

+ State 14 in the "OpenLog" procedure is only reached if after expanding the Mode item capacity DXKeeper's attempt to copy or compact the log file failed. I have added instrumentation to the next version of DXKeeper that will record the exact location of the failure.


2021-04-21 10:31:58.313 > program error 3050 in module DXLogModule.OpenLog, state = 1, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not lock file.

+ That's your "standard" sporadic " Could not lock file" DropBox failure.


Nothing unusual happened between the 6th April and Today other than I started Launcher Today, saw an application update, processed it, then tried to start the Suite as I usually do.

Note the "Could not lock file" messages which seem to correlate with the "whatever problem is causing DropBox to not reliably store your log file" issue you cite. It seems to me, that other than causing the MDB file to be locked periodically, DropBox is doing nothing wrong as files can become locked for a number of reasons unrelated to the application that owns and manages the file, and applications may be able to wait and retry to avoid that becoming a problem. For sure it is not a "chronic" problem with DropBox.

+ DXKeeper does not exclusively open the current log file, as both DXView and SpotCollector require continuous "read only" access. Thus DropBox should only be impeded if it's trying to exclusively open your log file - which it should never do.

I don't see any error messages related to scripts failing

+ There are no scripts involved in this process.


the log file clearly was not recreated during the compaction process. I note again that apart from an error that the log file could not be found, no other error messages were shown. As far as I was concerned the log file simply disappeared.

+ DXKeeper does the following:

1. makes a copy of G4WJS.mdb and name that copy Uncompacted_G4WJS.mdb

2. deletes G4WJS.mdb

3. directs the Jet database engine to compact Uncompacted_G4WJS.mdb and put the compacted result in G4WJS.mdb

+ Thus a failure of step 3 would produce the result you report:

A. Uncompacted_G4WJS.mdb is present

B. G4WJS.mdb is absent.

+ My Google search seeking problematic behavior when the Jet Engine's CompactDatabase function is invoked on files hosted by DropBox yielded no results. The transient "lock errors" you have been encountering could be responsible.

73,

Dave, AA6YQ


Re: LotW Sync not Responding - Solved (I think)

Dave AA6YQ
 

+ AA6YQ comments below

Well, you could knock me over with a feather. I was one of the first 50 customers to own the WN-2. I have a thread here asking about problems with LoTW sync operations in DXK. While it was clearly not a DXL caused issue, it was elusive and I couldn't isolate the behavior. You sir, just hit this nail square on the head.

I can report that over the last couple of days I have been able to independently reproduce this behavior. The WN-2 software is the culprit. Now I can update DXK from LoTW any time I like. This is fantastic.

Now, if it were a *nix system I would isolate the conflict, but being Windows not so much. I owe Alan (WN) a phone call over another question, so I'll update him on this discover.

+ It would be great if this could be tracked down to the root cause and corrected. When downloading information from LoTW, DXKeeper uses a function called

URLDownloadToFile

+ provided by Microsoft's URLMON.dll component. Evidently the WaveNode application is interfering with the operation of this function.

73,

Dave, AA6YQ


Re: LotW Sync not Responding - Solved (I think)

Jon Gefaell
 

Well, you could knock me over with a feather. I was one of the first 50 customers to own the WN-2. I have a thread here asking about problems with LoTW sync operations in DXK. While it was clearly not a DXL caused issue, it was elusive and I couldn't isolate the behavior. You sir, just hit this nail square on the head.

I can report that over the last couple of days I have been able to independently reproduce this behavior. The WN-2 software is the culprit. Now I can update DXK from LoTW any time I like. This is fantastic.

Now, if it were a *nix system I would isolate the conflict, but being Windows not so much. I owe Alan (WN)  a phone call over another question, so I'll update him on this discover.

Thank you Hank, and always Dave as well! 


On Tue, Apr 20, 2021 at 05:16 PM, Dave AA6YQ wrote:

After many process starts and stops, I finally determined that running the WN-2 Ver. 3.62 software for my WaveNode RF meter (USB
comms to computer) directly correlated to the DXKeeper - LotW misbehavior. Software running - errors. Not running no errors.
Doesn't appear to matter whether the WaveNode hardware is powered or not.

+ I'm glad that you found the culprit, Hank! I've added it to "Applications that can Interfere with DXLab Applications" in


Re: DX LAB 16.1.0 error

Dave AA6YQ
 

+ AA6YQ comments below
   Second attempt to upgrade to 16.1.0 also fails after reboot.
1) DXK 16.0.7 was running after I reverted from first attempt.
2) created backup data base
3) shut down DX Lab and rebooted the PC ( I did not start any of the non- DXL things that I normally run )
4) started launcher
5) up graded to 16.1.0
6) started DXK
7) first popup "Existing fields were not successfully updated due to an error noted in the errorlog.txt file; the specified log can not be opened."
8) The errorlog.txt for the contains the seem error message noted but for the present time
9) the database file is present where it has always been ../documents/ham data/DXLAB/DXKeeper/Databases/K0VM.mdb
10) after Ok on the first popup I get a second 'unable to open databse c:\users\al\documents\ham data\dxlab\dxkeeper\databases\k0vm.mdb'
11) after ok on the second popup dxkeeper opens but log  is empty.
12) attempting then to open the log in DXK gives a third popup.. 'the  specified log contains more fields than expected; this version of ...'

+ OK. Please place your K0VM.mdb log file in a zip archive, attache the archive to an email message, and send the message to me via

aa6yq (at) ambersoft.com

        73,

              Dave, AA6YQ


Re: DX LAB 16.1.0 error

Al Groff
 

P.S. I can open a different smaller old log with DXK 16.1.0 without error so suspec that it is something unique to my logfile.

AL, K0VM

On 4/21/2021 1:59 PM, Al Groff wrote:
Dave ,
   Second attempt to upgrade to 16.1.0 also fails after reboot.
1) DXK 16.0.7 was running after I reverted from first attempt.
2) created backup data base
3) shut down DX Lab and rebooted the PC ( I did not start any of the non- DXL things that I normally run )
4) started launcher
5) up graded to 16.1.0
6) started DXK
7) first popup "Existing fields were not successfully updated due to an error noted in the errorlog.txt file; the specified log can not be opened."
8) The errorlog.txt for the contains the seem error message noted but for the present time
9) the database file is present where it has always been ../documents/ham data/DXLAB/DXKeeper/Databases/K0VM.mdb
10) after Ok on the first popup I get a second 'unable to open databse c:\users\al\documents\ham data\dxlab\dxkeeper\databases\k0vm.mdb'
11) after ok on the second popup dxkeeper opens but log  is empty.
12) attempting then to open the log in DXK gives a third popup.. 'the  specified log contains more fields than expected; this version of ...'

AL, K0VM


On 4/21/2021 12:02 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

DXK failed after  upgrading to 16.1.0.

Found this in the error log
2021-04-21 13:59:43     > DXKeeper version 16.1.0
2021-04-21 13:59:43     > App.Path          : C:\ham programs\DXLab\DXKeeper
2021-04-21 13:59:43     > App.exe           : DXKeeper
2021-04-21 13:59:43     > Module            : C:\ham programs\DXLab\DXKeeper\DXKeeper.exe
2021-04-21 13:59:43     > Operating System  : Windows 10 Home (64-bit) build 19042
2021-04-21 13:59:43     > Locale ID         : 1033 (0x409)
2021-04-21 13:59:43     > ANSI CodePage     : 1252
2021-04-21 13:59:43     > OEM CodePage      : 437
2021-04-21 13:59:43     > Country           : United States
2021-04-21 13:59:43     > Language          : English
2021-04-21 13:59:43     > DecimalSeparator  : .
2021-04-21 13:59:43     > ThousandSeparator : ,
2021-04-21 13:59:43     > DXLab Apps        : [CC,SC]
2021-04-21 14:09:18     > Monitors          : 2
2021-04-21 14:09:18     > Monitor 1
2021-04-21 14:09:18     >    width          : 1080
2021-04-21 14:09:18     >    height         : 1920
2021-04-21 14:09:18     >    dimensions     : (-1080, 0)-(0, 1920)
2021-04-21 14:09:18     > Monitor 2
2021-04-21 14:09:18     >    width          : 2560
2021-04-21 14:09:18     >    height         : 1440
2021-04-21 14:09:18     >    dimensions     : (0, 0)-(2560, 1440)
2021-04-21 14:09:18.015 > program error 3035 in module DXLogModule.UpdateFields: System resource exceeded.

Had to revert to 16.0.7 and recover log from last nights backup..

+ Did rebooting Windows as Joe W4TV suggested enable you to upgrade DXKeeper to 16.1.0?

         73,

                 Dave, AA6YQ





Re: DX LAB 16.1.0 error

Al Groff
 

Dave ,
   Second attempt to upgrade to 16.1.0 also fails after reboot.
1) DXK 16.0.7 was running after I reverted from first attempt.
2) created backup data base
3) shut down DX Lab and rebooted the PC ( I did not start any of the non- DXL things that I normally run )
4) started launcher
5) up graded to 16.1.0
6) started DXK
7) first popup "Existing fields were not successfully updated due to an error noted in the errorlog.txt file; the specified log can not be opened."
8) The errorlog.txt for the contains the seem error message noted but for the present time
9) the database file is present where it has always been ../documents/ham data/DXLAB/DXKeeper/Databases/K0VM.mdb
10) after Ok on the first popup I get a second 'unable to open databse c:\users\al\documents\ham data\dxlab\dxkeeper\databases\k0vm.mdb'
11) after ok on the second popup dxkeeper opens but log  is empty.
12) attempting then to open the log in DXK gives a third popup.. 'the  specified log contains more fields than expected; this version of ...'

AL, K0VM

On 4/21/2021 12:02 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

DXK failed after upgrading to 16.1.0.

Found this in the error log
2021-04-21 13:59:43 > DXKeeper version 16.1.0
2021-04-21 13:59:43 > App.Path : C:\ham programs\DXLab\DXKeeper
2021-04-21 13:59:43 > App.exe : DXKeeper
2021-04-21 13:59:43 > Module : C:\ham programs\DXLab\DXKeeper\DXKeeper.exe
2021-04-21 13:59:43 > Operating System : Windows 10 Home (64-bit) build 19042
2021-04-21 13:59:43 > Locale ID : 1033 (0x409)
2021-04-21 13:59:43 > ANSI CodePage : 1252
2021-04-21 13:59:43 > OEM CodePage : 437
2021-04-21 13:59:43 > Country : United States
2021-04-21 13:59:43 > Language : English
2021-04-21 13:59:43 > DecimalSeparator : .
2021-04-21 13:59:43 > ThousandSeparator : ,
2021-04-21 13:59:43 > DXLab Apps : [CC,SC]
2021-04-21 14:09:18 > Monitors : 2
2021-04-21 14:09:18 > Monitor 1
2021-04-21 14:09:18 > width : 1080
2021-04-21 14:09:18 > height : 1920
2021-04-21 14:09:18 > dimensions : (-1080, 0)-(0, 1920)
2021-04-21 14:09:18 > Monitor 2
2021-04-21 14:09:18 > width : 2560
2021-04-21 14:09:18 > height : 1440
2021-04-21 14:09:18 > dimensions : (0, 0)-(2560, 1440)
2021-04-21 14:09:18.015 > program error 3035 in module DXLogModule.UpdateFields: System resource exceeded.

Had to revert to 16.0.7 and recover log from last nights backup..

+ Did rebooting Windows as Joe W4TV suggested enable you to upgrade DXKeeper to 16.1.0?

73,

Dave, AA6YQ





Re: DXKeeper 16.1.0 is available

g4wjs
 

On 21/04/2021 18:00, Dave AA6YQ wrote:
+ AA6YQ comments below

I have just done this upgrade and had a problem when I started DXKeeper afterwards. I received a message saying the log database could not be opened, I do get this occasionally due to some background locking from Dropbox where I keep my log database. This is not normally an issue as I simply open the Config window and click the Open button to open the log. This has always worked up until now. This time there is no Open button because the log database has gone! In its place is Uncompacted_G4WJS.mdb. I assume  I can copy that back to G4WJS.mdb and proceed as normal, but how DXKeeper got to this point without any warning seems to be an issue. 

Hi again Dave,

as a follow up, since I have backups of everything, I went ahead and renamed the Uncompacted_G4WJS.mdb back to G4WJS.mdb, restarted DXKeeper, and SpotCollector; all seems OK now.

+ When altering the characteristics of an existing QSO item -- like increasing its maximum capacity from 8 characters to 12 characters - DXKeeper

1. creates a new QSO item with the desired characteristics and gives it a temporary name

2. in every copy the contents of the existing QSO item to the new QSO item in every logged QSO

3. deletes the existing QSO item from every logged QSO

4. changes the name of the new QSO item to that of the just-deleted QSO item

5. makes a copy of the log file; if the log file is named X.mdb, the copy is named uncompacted_X.mdb

6. compacts the log file to reclaim the space consumed by the deleted QSO item

Steps 1, 2, 3, 4, and 6 are accomplished by sending directives to the database engine (Microsoft Jet). Step 5 is accomplished with the Windows Scripting Host, a capability included in every version of Windows.

Any unrecoverable error that occurs during the above steps is reported to the user in an on-screen window, or in an errorlog.txt file whose presence is indicated in the title bar of DXKeeper's Main window. Is there an errorlog.txt file in your DXKeeper folder? If so, please attach it to an email message, and send it to me via aa6yq (at) ambersoft.com

Since DXKeeper was first made publicly available 20 years ago, the above procedure has been invoked in more than 25 different DXKeeper releases to expand the capacity of existing QSO items or alter their "data type" (e.g. from character string to date). 

In your case, Bill, the existence of a recently-created Uncompacted_G4WJS.mdb means that steps 1-5 above were completed successfully, but step 6 evidently failed. Given that you've had chronic problems with DropBox as the host of your log file, that's disappointing, but not surprising. My advice is to

A. backup your log file 

B. compact your log file (Configuration window, Log tab, "Log file" panel, Compact button)

C. correct whatever problem is causing DropBox to not reliably store your log file, or abandon it in favor of a mechanism that works reliably

       73,

                 Dave, AA6YQ

Hi Dave,

here is the tail of my DXKeeper ErrorLog.txt:

2021-04-06 19:26:38     > DXKeeper version 16.0.7
2021-04-06 19:26:38     > App.Path          : C:\DXLab\DXKeeper
2021-04-06 19:26:38     > App.exe           : DXKeeper
2021-04-06 19:26:38     > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
2021-04-06 19:26:38     > Operating System  : Windows 8.1 (64-bit) build 9600
2021-04-06 19:26:38     > Locale ID         : 2057 (0x809)
2021-04-06 19:26:38     > ANSI CodePage     : 1252
2021-04-06 19:26:38     > OEM CodePage      : 850
2021-04-06 19:26:38     > Country           : United Kingdom
2021-04-06 19:26:38     > Language          : English
2021-04-06 19:26:38     > DecimalSeparator  : .
2021-04-06 19:26:38     > ThousandSeparator : ,
2021-04-06 19:26:38     > DXLab Apps        : 
2021-04-06 19:26:42     > Monitors          : 2
2021-04-06 19:26:42     > Monitor 1
2021-04-06 19:26:42     >    width          : 1920
2021-04-06 19:26:42     >    height         : 1080
2021-04-06 19:26:42     >    dimensions     : (0, 0)-(1920, 1080)
2021-04-06 19:26:42     > Monitor 2
2021-04-06 19:26:42     >    width          : 1920
2021-04-06 19:26:42     >    height         : 1080
2021-04-06 19:26:42     >    dimensions     : (-1920, 0)-(0, 1080)
2021-04-06 19:26:42.417 > program error 3050 in module DXLogModule.OpenLog, state =  15, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not lock file.
2021-04-06 23:06:10.049 > Common.Terminate: DXKeeper shutdown

2021-04-21 10:22:29     > DXKeeper version 16.1.0
2021-04-21 10:22:29     > App.Path          : C:\DXLab\DXKeeper
2021-04-21 10:22:29     > App.exe           : DXKeeper
2021-04-21 10:22:29     > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
2021-04-21 10:22:29     > Operating System  : Windows 8.1 (64-bit) build 9600
2021-04-21 10:22:29     > Locale ID         : 2057 (0x809)
2021-04-21 10:22:29     > ANSI CodePage     : 1252
2021-04-21 10:22:29     > OEM CodePage      : 850
2021-04-21 10:22:29     > Country           : United Kingdom
2021-04-21 10:22:29     > Language          : English
2021-04-21 10:22:29     > DecimalSeparator  : .
2021-04-21 10:22:29     > ThousandSeparator : ,
2021-04-21 10:22:29     > DXLab Apps        : 
2021-04-21 10:22:35     > Monitors          : 2
2021-04-21 10:22:35     > Monitor 1
2021-04-21 10:22:35     >    width          : 1920
2021-04-21 10:22:35     >    height         : 1080
2021-04-21 10:22:35     >    dimensions     : (0, 0)-(1920, 1080)
2021-04-21 10:22:35     > Monitor 2
2021-04-21 10:22:35     >    width          : 1920
2021-04-21 10:22:35     >    height         : 1080
2021-04-21 10:22:35     >    dimensions     : (-1920, 0)-(0, 1080)
2021-04-21 10:22:35.877 > program error 3024 in module DXLogModule.OpenLog, state =  14, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not find file 'C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb'.
2021-04-21 10:23:51.336 > Common.Terminate: DXKeeper shutdown

2021-04-21 10:31:54     > DXKeeper version 16.1.0
2021-04-21 10:31:54     > App.Path          : C:\DXLab\DXKeeper
2021-04-21 10:31:54     > App.exe           : DXKeeper
2021-04-21 10:31:54     > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
2021-04-21 10:31:54     > Operating System  : Windows 8.1 (64-bit) build 9600
2021-04-21 10:31:54     > Locale ID         : 2057 (0x809)
2021-04-21 10:31:54     > ANSI CodePage     : 1252
2021-04-21 10:31:54     > OEM CodePage      : 850
2021-04-21 10:31:54     > Country           : United Kingdom
2021-04-21 10:31:54     > Language          : English
2021-04-21 10:31:54     > DecimalSeparator  : .
2021-04-21 10:31:54     > ThousandSeparator : ,
2021-04-21 10:31:54     > DXLab Apps        : 
2021-04-21 10:31:58     > Monitors          : 2
2021-04-21 10:31:58     > Monitor 1
2021-04-21 10:31:58     >    width          : 1920
2021-04-21 10:31:58     >    height         : 1080
2021-04-21 10:31:58     >    dimensions     : (0, 0)-(1920, 1080)
2021-04-21 10:31:58     > Monitor 2
2021-04-21 10:31:58     >    width          : 1920
2021-04-21 10:31:58     >    height         : 1080
2021-04-21 10:31:58     >    dimensions     : (-1920, 0)-(0, 1080)
2021-04-21 10:31:58.313 > program error 3050 in module DXLogModule.OpenLog, state =  1, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not lock file.

Nothing unusual happened between the 6th April and Today other than I started Launcher Today, saw an application update, processed it, then tried to start the Suite as I usually do.

Note the "Could not lock file" messages which seem to correlate with the "whatever problem is causing DropBox to not reliably store your log file" issue you cite. It seems to me, that other than causing the MDB file to be locked periodically, DropBox is doing nothing wrong as files can become locked for a number of reasons unrelated to the application that owns and manages the file, and applications may be able to wait and retry to avoid that becoming a problem. For sure it is not a "chronic" problem with DropBox.

I don't see any error messages related to scripts failing, the log file clearly was not recreated during the compaction process. I note again that apart from an error that the log file could not be found, no other error messages were shown. As far as I was concerned the log file simply disappeared.

73
Bill
G4WJS.


--
73

Bill

G4WJS.


Re: DXKeeper 16.1.0 is available

Peter Laws / N5UWY
 

On Tue, Apr 20, 2021 at 9:03 PM Dave AA6YQ <aa6yq@ambersoft.com> wrote:


before installing or upgrading to DXKeeper 16.1.0

I saw the ITU Zone fix script (those unnecessary leading 0s have
bugged me for a while!) and thought - cool! Let me do that! I saw
that DXKeeper would be messing with the DB itself so only clicked the
DXKeeper button in Launcher rather that starting everything. Updated
DXK, all was well. Ran DXK and it offered to make a backup since it
was planning to muck with the DB and I said "good idea". Let that
run, no issues. Went to the ADV screen, found the "run script"
button, found the ITU fix script, ran that, and all was well ... with
proper ITUZ numbers in the log. :-)

No problems. Lest you think something along the lines of "he must
have a small DB" ... I have over 18k QSOs in it.

Killed DXK, went to launcher, loaded my "SWL" workspace and have been
trying to copy NDBs all morning while I do other things.


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: DX LAB 16.1.0 error

Dave AA6YQ
 

+ AA6YQ comments below

DXK failed after upgrading to 16.1.0.

Found this in the error log
2021-04-21 13:59:43 > DXKeeper version 16.1.0
2021-04-21 13:59:43 > App.Path : C:\ham programs\DXLab\DXKeeper
2021-04-21 13:59:43 > App.exe : DXKeeper
2021-04-21 13:59:43 > Module : C:\ham programs\DXLab\DXKeeper\DXKeeper.exe
2021-04-21 13:59:43 > Operating System : Windows 10 Home (64-bit) build 19042
2021-04-21 13:59:43 > Locale ID : 1033 (0x409)
2021-04-21 13:59:43 > ANSI CodePage : 1252
2021-04-21 13:59:43 > OEM CodePage : 437
2021-04-21 13:59:43 > Country : United States
2021-04-21 13:59:43 > Language : English
2021-04-21 13:59:43 > DecimalSeparator : .
2021-04-21 13:59:43 > ThousandSeparator : ,
2021-04-21 13:59:43 > DXLab Apps : [CC,SC]
2021-04-21 14:09:18 > Monitors : 2
2021-04-21 14:09:18 > Monitor 1
2021-04-21 14:09:18 > width : 1080
2021-04-21 14:09:18 > height : 1920
2021-04-21 14:09:18 > dimensions : (-1080, 0)-(0, 1920)
2021-04-21 14:09:18 > Monitor 2
2021-04-21 14:09:18 > width : 2560
2021-04-21 14:09:18 > height : 1440
2021-04-21 14:09:18 > dimensions : (0, 0)-(2560, 1440)
2021-04-21 14:09:18.015 > program error 3035 in module DXLogModule.UpdateFields: System resource exceeded.

Had to revert to 16.0.7 and recover log from last nights backup..

+ Did rebooting Windows as Joe W4TV suggested enable you to upgrade DXKeeper to 16.1.0?

73,

Dave, AA6YQ


Re: DXKeeper 16.1.0 Issue

Dave AA6YQ
 

+ AA6YQ comments below

I updated DXKeeper to 16.1.0 this morning, but it refuses to open my log. I get the following error message:

The specified log contains more fields than expected; this version - 16.1.0 - is incapable of opening it. This problem can likely be overcome by running the current version of DXKeeper.

What needs to be done to overcome this issue? I want to be able to use the latest version of DXKeeper.

+ Please place your log file in a zip archive, and attach the zip archive to an email message. If there's an errorlog.txt file in your DXKeeper folder, please attach that to the email message as well. Then send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: DXKeeper 16.1.0 is available

Dave AA6YQ
 

+ AA6YQ comments below

I have just done this upgrade and had a problem when I started DXKeeper afterwards. I received a message saying the log database could not be opened, I do get this occasionally due to some background locking from Dropbox where I keep my log database. This is not normally an issue as I simply open the Config window and click the Open button to open the log. This has always worked up until now. This time there is no Open button because the log database has gone! In its place is Uncompacted_G4WJS.mdb. I assume I can copy that back to G4WJS.mdb and proceed as normal, but how DXKeeper got to this point without any warning seems to be an issue.

Hi again Dave,

as a follow up, since I have backups of everything, I went ahead and renamed the Uncompacted_G4WJS.mdb back to G4WJS.mdb, restarted DXKeeper, and SpotCollector; all seems OK now.

+ When altering the characteristics of an existing QSO item -- like increasing its maximum capacity from 8 characters to 12 characters - DXKeeper

1. creates a new QSO item with the desired characteristics and gives it a temporary name

2. in every copy the contents of the existing QSO item to the new QSO item in every logged QSO

3. deletes the existing QSO item from every logged QSO

4. changes the name of the new QSO item to that of the just-deleted QSO item

5. makes a copy of the log file; if the log file is named X.mdb, the copy is named uncompacted_X.mdb

6. compacts the log file to reclaim the space consumed by the deleted QSO item

Steps 1, 2, 3, 4, and 6 are accomplished by sending directives to the database engine (Microsoft Jet). Step 5 is accomplished with the Windows Scripting Host, a capability included in every version of Windows.

Any unrecoverable error that occurs during the above steps is reported to the user in an on-screen window, or in an errorlog.txt file whose presence is indicated in the title bar of DXKeeper's Main window. Is there an errorlog.txt file in your DXKeeper folder? If so, please attach it to an email message, and send it to me via aa6yq (at) ambersoft.com

Since DXKeeper was first made publicly available 20 years ago, the above procedure has been invoked in more than 25 different DXKeeper releases to expand the capacity of existing QSO items or alter their "data type" (e.g. from character string to date).

In your case, Bill, the existence of a recently-created Uncompacted_G4WJS.mdb means that steps 1-5 above were completed successfully, but step 6 evidently failed. Given that you've had chronic problems with DropBox as the host of your log file, that's disappointing, but not surprising. My advice is to

A. backup your log file

B. compact your log file (Configuration window, Log tab, "Log file" panel, Compact button)

C. correct whatever problem is causing DropBox to not reliably store your log file, or abandon it in favor of a mechanism that works reliably

73,

Dave, AA6YQ


DXK update - no issues here

Phil Cooper
 

Hi all,

 

I have just updated DXKeeper to 16.1.0 and had no issues at all.

 

For those that did, did you close any/all of the items in Note 1 of the release notes?

It specifically says that DXView, JT-Alert, Spotcollector or SpotSpy need to be closed first.

 

73 de Phil GU0SUP


Re: DX LAB 16.1.0 error

Joe Subich, W4TV
 

2021-04-21 14:09:18.015 > program error 3035 in module
DXLogModule.UpdateFields: System resource exceeded.
RESTART (not reboot) Windows and try again. Looks like you ran out of
some Windows resource.

73,

... Joe, W4TV


On 2021-04-21 10:26 AM, Al Groff via groups.io wrote:
DXK failed after  upgrading to 16.1.0.
Found this in the error log
2021-04-21 13:59:43     > DXKeeper version 16.1.0
2021-04-21 13:59:43     > App.Path          : C:\ham programs\DXLab\DXKeeper
2021-04-21 13:59:43     > App.exe           : DXKeeper
2021-04-21 13:59:43     > Module            : C:\ham programs\DXLab\DXKeeper\DXKeeper.exe
2021-04-21 13:59:43     > Operating System  : Windows 10 Home (64-bit) build 19042
2021-04-21 13:59:43     > Locale ID         : 1033 (0x409)
2021-04-21 13:59:43     > ANSI CodePage     : 1252
2021-04-21 13:59:43     > OEM CodePage      : 437
2021-04-21 13:59:43     > Country           : United States
2021-04-21 13:59:43     > Language          : English
2021-04-21 13:59:43     > DecimalSeparator  : .
2021-04-21 13:59:43     > ThousandSeparator : ,
2021-04-21 13:59:43     > DXLab Apps        : [CC,SC]
2021-04-21 14:09:18     > Monitors          : 2
2021-04-21 14:09:18     > Monitor 1
2021-04-21 14:09:18     >    width          : 1080
2021-04-21 14:09:18     >    height         : 1920
2021-04-21 14:09:18     >    dimensions     : (-1080, 0)-(0, 1920)
2021-04-21 14:09:18     > Monitor 2
2021-04-21 14:09:18     >    width          : 2560
2021-04-21 14:09:18     >    height         : 1440
2021-04-21 14:09:18     >    dimensions     : (0, 0)-(2560, 1440)
2021-04-21 14:09:18.015 > program error 3035 in module DXLogModule.UpdateFields: System resource exceeded.
Had to revert to 16.0.7 and recover log from last nights backup..
AL, K0VM


Re: DXKeeper 16.1.0 Issue

Victor Culver
 

Did you read the release notes before updating?  Sometimes old Dave slips in an update that requires an extra step before executing the update. 

If the update is broken he will fix it quickly. 

Good morning. 



Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

73, Vic, W4VIC 





On Wednesday, April 21, 2021, 9:02 AM, Nathern Priddy <nbpriddy@...> wrote:

I updated DXKeeper to 16.1.0 this morning, but it refuses to open my log.  I get the following error message:

The specified log contains more fields than expected; this version - 16.1.0 - is incapable of opening it.  This problem can likely be overcome by running the current version of DXKeeper.

What needs to be done to overcome this issue?  I want to be able to use the latest version of DXKeeper.

Barry Priddy - K5VIP


DX LAB 16.1.0 error

Al Groff
 

DXK failed after  upgrading to 16.1.0.

Found this in the error log
2021-04-21 13:59:43     > DXKeeper version 16.1.0
2021-04-21 13:59:43     > App.Path          : C:\ham programs\DXLab\DXKeeper
2021-04-21 13:59:43     > App.exe           : DXKeeper
2021-04-21 13:59:43     > Module            : C:\ham programs\DXLab\DXKeeper\DXKeeper.exe
2021-04-21 13:59:43     > Operating System  : Windows 10 Home (64-bit) build 19042
2021-04-21 13:59:43     > Locale ID         : 1033 (0x409)
2021-04-21 13:59:43     > ANSI CodePage     : 1252
2021-04-21 13:59:43     > OEM CodePage      : 437
2021-04-21 13:59:43     > Country           : United States
2021-04-21 13:59:43     > Language          : English
2021-04-21 13:59:43     > DecimalSeparator  : .
2021-04-21 13:59:43     > ThousandSeparator : ,
2021-04-21 13:59:43     > DXLab Apps        : [CC,SC]
2021-04-21 14:09:18     > Monitors          : 2
2021-04-21 14:09:18     > Monitor 1
2021-04-21 14:09:18     >    width          : 1080
2021-04-21 14:09:18     >    height         : 1920
2021-04-21 14:09:18     >    dimensions     : (-1080, 0)-(0, 1920)
2021-04-21 14:09:18     > Monitor 2
2021-04-21 14:09:18     >    width          : 2560
2021-04-21 14:09:18     >    height         : 1440
2021-04-21 14:09:18     >    dimensions     : (0, 0)-(2560, 1440)
2021-04-21 14:09:18.015 > program error 3035 in module DXLogModule.UpdateFields: System resource exceeded.

Had to revert to 16.0.7 and recover log from last nights backup..

AL, K0VM


DXKeeper 16.1.0 Issue

Barry Priddy
 

I updated DXKeeper to 16.1.0 this morning, but it refuses to open my log.  I get the following error message:

The specified log contains more fields than expected; this version - 16.1.0 - is incapable of opening it.  This problem can likely be overcome by running the current version of DXKeeper.

What needs to be done to overcome this issue?  I want to be able to use the latest version of DXKeeper.

Barry Priddy - K5VIP


Re: DXKeeper 16.1.0 is available

g4wjs
 

On 21/04/2021 11:30, g4wjs wrote:
On 21/04/2021 03:03, Dave AA6YQ wrote:
* If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions

before installing or upgrading to DXKeeper 16.1.0


* Terminate DXView, JT-Alert, SpotCollector, and SpotSpy before startingDXKeeper 16.1.0 so that it can update your log, as
described in

https://groups.io/g/DXLab/message/200923


This version

- when executing the "First QSOs" and "Uniques" functions, tolerates QSOs whose callsign items are not specified

- when downloading DXCC Credits, informs the user if the specified LoTW username/password combination has been rejected (tnx to Saad
N5FF)

- tolerates a QSO with an empty WPX prefix in WPXModule.UpdateWPXProgress

- when generating a user item progress report, replaces slash or backslash characters in the report filename with hyphens (tnx to
Paul W2EXK)

- when logging a QSO or processing an update from LoTW, removes any leading zeroes from ITU items (tnx to Norm KC1BMD and Joe W4TV)

- includes a Normalize_ITU.txt script in its Scripts folder that removesleading zeros from the ITU items of logged QSOs (tnx to
Norm KC1BMD and Joe W4TV)

- provides a "Create Mobile myQTHID" option on the Main window's "ImportQSOs" tab (tnx to Al AB2ZY, Dave W0ZF, Alan N5NA, Joe W4TV,
Rich VE3KI, and Scott N9LJX)

- when directed to log a QSO by another application but unable to add anentry to the log's QSO table, closes and re-opens the log
database table, and then retries the operation (tnx to Bernd KB7AK)

- responds to depressing the CTRL key while clicking the "Check LoTW Queue" button by directing your default web browser to display
the LoTW Server's processing queue history and current status

- on opening a log file, automatically increases the width of its Mode items from 8 characters to 12 characters

- supports 67 new submodes added to ADIF 3.1.2: DOM-M, DOM4, DOM5, DOM8,DOM11, DOM16, DOM22, DOM44, DOM88, HELLX5, HELLX9,
SLOWHELL, FST4W, JTMS, MFSK64L, MFSK128L, Q65, 8PSK125, 8PSK125F, 8PSK125FL, 8PSK250, 8PSK250F, 8PSK250FL, 8PSK500, 8PSK500F,
8PSK1000, 8PSK1000F, 8PSK1200F, PSK63RC20, PSK63RC32, PSK63RC4, PSK63RC5, PSK63RC10, PSK125RC10, PSK125RC12, PSK125RC16, PSK125RC4,
PSK125RC5, PSK250RC2, PSK250RC3, PSK250RC5, PSK250RC6, PSK250RC7, PSK500RC2, PSK500RC3, PSK500RC4, PSK800RC2, PSK1000RC2, THOR-M,
THOR4, THOR5, THOR8, THOR11, THOR16, THOR22, THOR25X4, THOR50X1, THOR50X2, THOR100, THRBX1, THRBX2, THRBX4, THROB1, THROB2, THROB4,
NAVTEX, SITORB

- updates the Configuration.htm, Import.htm, ModifyLog.htm, Progress.htm, and QSL.htm documentation files


Notes:

1. The automatic increase of the width of the current log file's Mode item from 8 characters to 12 characters will fail if DXView,
JT-Alert, SpotCollector, or SpotSpy are running, so these applications must be terminated before the automatic Mode item expansion
can be completed; DXKeeper will inform you if this is necessary.


2. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

    a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

    b. VirusTotal: 0 of 67 scanners detected malware in this version's executable

    c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


4. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


DXKeeper 16.1.0 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

       73,

             Dave, AA6YQ

Hi Dave,

I have just done this upgrade and had a problem when I started DXKeeper afterwards. I received a message saying the log database could not be opened, I do get this occasionally due to some background locking from Dropbox where I keep my log database. This is not normally an issue as I simply open the Config window and click the Open button to open the log. This has always worked up until now. This time there is no Open button because the log database has gone! In its place is Uncompacted_G4WJS.mdb. I assume  I can copy that back to G4WJS.mdb and proceed as normal, but how DXKeeper got to this point without any warning seems to be an issue.

73
Bill
G4WJS.

Hi again Dave,

as a follow up, since I have backups of everything, I went ahead and renamed the Uncompacted_G4WJS.mdb back to G4WJS.mdb, restarted DXKeeper, and SpotCollector; all seems OK now.


--
73

Bill

G4WJS.

2921 - 2940 of 203852