Page 1 of 1

TX7T Marquesas now shows Clipperton Is.

Posted: 18 Nov 2019, 16:19
by K5CKS
This morning TX7T is now showing as "Clipperton Island" instead of Marquesas like it had been in the DX Cluster. What changed??
Thanks,
Rory, K5CKS

Re: TX7T Marquesas now shows Clipperton Is.

Posted: 18 Nov 2019, 16:25
by G4POP
Probably your country file automatically updated?

Re: TX7T Marquesas now shows Clipperton Is.

Posted: 18 Nov 2019, 20:00
by K5CKS
That is what I thought Terry. Unfortunately they are still in the Marquesas. Can that file be edited?

Rory

Re: TX7T Marquesas now shows Clipperton Is.

Posted: 19 Nov 2019, 13:55
by KD0ZV
Rory,

We are talking about the same thing at end of this thread.

https://forum.log4om.com/viewtopic.php? ... 4&start=10

It was working fine for me until a few days ago.

I have use ClubLog exception file checked and looking at my backups of the ClubLog.XML file it has not changed for that Island. So something else is driving it.

Not the first time it has shown up as Clipperton Island. TX0M was showing up as Clipperton as well.

I am not worrying about it. Just waiting for Log4OM V2 and hoping that will fix it :)

Log4om is 99% for me when it comes to lookups but when it messes up its always "Clipperton Island".

73
Rich
kd0zv

Re: TX7T Marquesas now shows Clipperton Is.

Posted: 19 Nov 2019, 16:36
by G4POP
I just checked this in Version 1 and you can see the results yourselves, all I did was make sure the files were up to date and of course I am using version 1.40, dont know what version you guys are using?


Capture.JPG
Capture.JPG (182.3 KiB) Viewed 4879 times

Re: TX7T Marquesas now shows Clipperton Is.

Posted: 02 Nov 2020, 19:13
by w9mdb
Piling on here....TX0T is coming up Clipperton Island in both V1 and V2 in the cluster spotting when it is French Polynesia in cty.dat
Doesn't V2 use cty.dat for cluster spot exceptions? In V2 I have "Use Clublog database" and "Use CTY database" enabled.
Also where does clublog.xml come from? Doesn't appear to get updated at all.

In V1 we see this error on a new installation of LogOM V1 -- could this error prevent the lookup of TX0T in the cty.dat file?

2020-11-02 16:27:58.9242 INFO: Log4OMMainWindow: *********************************************************
2020-11-02 16:27:58.9327 INFO: Log4OMMainWindow: *********** LOGGING LEVEL: TRACE MODE + SQL MODE ********
2020-11-02 16:27:58.9336 INFO: Log4OMMainWindow: *********************************************************
2020-11-02 16:28:13.3547 INFO: Log4OMMainWindow: *Open IMPORT CLUBLOG FROM WEB*
2020-11-02 16:28:13.4184 INFO: FileManagement: Clublog begin download
2020-11-02 16:28:13.4193 DEBUG: FileManagement: URL https://clublog.org/cty.php?api=6e41673 ... ce4c6bbe0e
2020-11-02 16:28:13.4368 INFO: Log4OMMainWindow: *Open IMPORT RANKING FROM WEB*
2020-11-02 16:28:13.8625 INFO: FileManagement: RANKING begin save
2020-11-02 16:28:13.8664 INFO: FileManagement: RANKING save completed
2020-11-02 16:28:13.8674 INFO: Log4OMMainWindow: *CLUBLOG Database updated*
2020-11-02 16:28:14.6826 ERROR: *** FileManagement: Error downloading ClubLog Database ******* [Function: #=qVfFY8UX3NIm9FZJNZkLa3CL8XpFKQYcgMs7U$XeUp5E=] System.NullReferenceException: Object reference not set to an instance of an object.
at LogOM.BL.FileManagement.#=qVfFY8UX3NIm9FZJNZkLa3CL8XpFKQYcgMs7U$XeUp5E=(Object #=qDs4haVqs9PbDqTR4OfKoPg==, AsyncCompletedEventArgs #=qegipl4uvOXoZkLMfRNCdmA==)