Log4OM

Hello,

I have a problem.
I checked my QSL manager for waiting uploads and clicked on the filter on the bottom of the QSL manager window.
after that I observed that all my QSOs (over 9000) gets duplicated bit by bit (the number of the QSOs count up).
The duplicated contacts have about 15 Seconds time offset and for example the original DXCC is Russia and the copy is European Russia.

Anybody has an idea where this comes from and how I can stop that?
After that I have to delete all the duplicates, is it possible to delete them all at once or only seperately?

many thanky for your help.

Yes your getting the dupes because you set up a wsjt integration incorrectly

Export an adif then I port that adif into a clean database using a 60 second data logging interval in import routine

Hello Terry,

many thanks for the fast reply.
I already did that in the past by integrating the adif logfile from QRZ.com in a new database, because it contains all QSOs.
Is there anything I can do to use my existing logfile without getting the duplicates anymore.
Because I can remember that I had to edit the adif log from QRZ.com after importing it to Log4OM
Until today evening everything worked like a charm, so I do not know why this behaviour occours just now

I have attached you some screenshots for the WSJT-X integration.
I removed the setting for WSJT-X - Import QSO from JT Message #12 because I use UDP Listener for the loggings that come directly from WSJT-X and the ADIF monitor for the integration of missing QSOs from the WSJT-X adif if I forget to open Log4OM (which worked without any problems in the past.)

When I delete the double QSOs that were added in Log4OM, they just were re-added after a short time and I don't get why, there must be a wrong setting somewhere...
The only thing I did was clicking on the filters tab in the QSL Manager but I did not make any settings and after quitting it I got the duplicates

What I found is that the whole log was parsed by the awardparser:
2023-02-24 21:06:07.6965 INFO: * [dje_zM7ZNC2ZHXFWG32J8G3SWW_ejd] [AWARDPARSER] : Award Management - Parse log started on 9276 items
2023-02-24 21:06:07.6995 INFO: [AwardsDatabase] : Loading Awards list from database
2023-02-24 21:06:11.0850 INFO: [dje_z25PYL9QJCNWX6MKBBV845_ejd] : Found references on FT8 -14 dB 2011 Hz FT8 +11 dB 1071 Hz
2023-02-24 21:06:14.6232 INFO: * [AwardsDatabase][6922 ms] : Awards list retrieved from database
2023-02-24 21:06:14.6302 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER] : Award Management - Parse qso started on IU1LDW|13.05.2021 18:22:00|10m|FT8
2023-02-24 21:06:15.0929 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER - 462 ms] : Award Management - Parse qso terminated on IU1LDW|13.05.2021 18:22:00|10m|FT8
2023-02-24 21:06:15.0959 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER] : Award Management - Parse qso started on IZ5OVP|13.05.2021 18:30:00|10m|FT8
2023-02-24 21:06:15.5681 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER - 472 ms] : Award Management - Parse qso terminated on IZ5OVP|13.05.2021 18:30:00|10m|FT8
2023-02-24 21:06:15.5721 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER] : Award Management - Parse qso started on HA7TM|13.05.2021 18:41:00|10m|FT8
2023-02-24 21:06:15.6673 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER - 95 ms] : Award Management - Parse qso terminated on HA7TM|13.05.2021 18:41:00|10m|FT8
2023-02-24 21:06:15.6713 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER] : Award Management - Parse qso started on 9A2GB|13.05.2021 18:43:45|10m|FT8
2023-02-24 21:06:15.7735 INFO: * [dje_zBZYBZ82EUVHCMUDKZ9GUWB7PW7WA_ejd] [AWARDPARSER - 101 ms] : Award Management - Parse qso terminated on 9A2GB|13.05.2021 18:43:45|10m|FT8

2023-02-24 21:59:45.0788 INFO: * [dje_zM7ZNC2ZHXFWG32J8G3SWW_ejd] [AWARDPARSER - 1405406 ms] : Award Management - Parse log terminated
2023-02-24 21:59:45.0888 INFO: * [dje_zQ65UA4DUHLTQPUHRF2PGXD8E2ZDQ_ejd][1633963 ms] : End of ADIF import
2023-02-24 21:59:45.0918 INFO: [dje_zVRT48CL8A2U23D37GUSF2_ejd] : ############### ADD QSO Callsign: IU1LDW Date: 13.05.2021 18:22:00 Band: 10m Mode: FT8
2023-02-24 21:59:45.1118 INFO: [dje_z96VMACW2GZT6GB6EYAGTX_ejd] : [QRZCOM] Search start on IU1LDW (originally IU1LDW)
2023-02-24 21:59:45.7126 INFO: * [dje_z96VMACW2GZT6GB6EYAGTX_ejd][600 ms] : [QRZCOM] Search finished on IU1LDW (originally IU1LDW)
2023-02-24 21:59:45.7206 ERROR: [DbSqlite][dje_zKP3JADXNTL7BDSZ_ejd] : [SQLITE] InsertUpdateDatabase Command error
[EXCEPTION] constraint failed
UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode code = Constraint (19), message = System.Data.SQLite.SQLiteException (0x800027AF): constraint failed
UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode
bei System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
bei System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
bei System.Data.SQLite.SQLiteDataReader.NextResult()
bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery(CommandBehavior behavior)
bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
bei L4ONG.DAL.SQLITE.DbSqlite.dje_zKP3JADXNTL7BDSZ_ejd(QSO dje_z8WAFCDJK_ejd, String dje_zUE8S94RQ_ejd, QsoActionEnum dje_z8X25DSNZ_ejd, Boolean dje_zJAFWQ4YV_ejd)
2023-02-24 21:59:45.7271 ERROR: [DbSqlite][SaveQso] : SQLITE SaveQSO exception while saving QSO with QsoId 20230224213231171
[EXCEPTION] constraint failed
UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode code = Constraint (19), message = System.Data.SQLite.SQLiteException (0x800027AF): constraint failed
UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode
bei System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
bei System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
bei System.Data.SQLite.SQLiteDataReader.NextResult()
bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery(CommandBehavior behavior)
bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
bei L4ONG.DAL.SQLITE.DbSqlite.dje_zKP3JADXNTL7BDSZ_ejd(QSO dje_z8WAFCDJK_ejd, String dje_zUE8S94RQ_ejd, QsoActionEnum dje_z8X25DSNZ_ejd, Boolean dje_zJAFWQ4YV_ejd)
bei L4ONG.DAL.SQLITE.DbSqlite.SaveQso(QSO dje_z8WAFCDJK_ejd, Int32 duplicateThreshold, Boolean silent)


So that award parsing nearly took an hour, after that the doublets were added (not all contacts as you can see on the errors).

Here a short excerpt from the log file of the adding of the doublets:
2023-02-24 21:59:46.7048 INFO: [dje_zVRT48CL8A2U23D37GUSF2_ejd] : ############### ADD QSO Callsign: 9A2GB Date: 13.05.2021 18:43:45 Band: 10m Mode: FT8
2023-02-24 21:59:46.7284 INFO: [dje_z96VMACW2GZT6GB6EYAGTX_ejd] : [QRZCOM] Search start on 9A2GB (originally 9A2GB)
2023-02-24 21:59:47.4419 INFO: * [dje_z96VMACW2GZT6GB6EYAGTX_ejd][713 ms] : [QRZCOM] Search finished on 9A2GB (originally 9A2GB)
2023-02-24 21:59:47.4629 INFO: [dje_zVRT48CL8A2U23D37GUSF2_ejd] : QSO Callsign: 9A2GB Date: 13.05.2021 18:43:45 Band: 10m Mode: FT8 Saved
2023-02-24 21:59:47.4659 INFO: [AdifManagement] : Begin export single QSO to ADIF string
2023-02-24 21:59:47.4689 INFO: [AdifManagement] : Export QSO to ADIF file completed
2023-02-24 21:59:47.4869 INFO: [dje_zWS97VJLWM96ZR2ATK3WG29Q9PVUZSLLK7X_ejd] : [ADIF MONITOR] C:\Users\Admin\AppData\Local\WSJT-X\wsjtx_log.adi NEW QSO LOADED: 9A2GB|13.05.2021 18:43:45|10m|FT8
2023-02-24 21:59:47.4909 INFO: [dje_zVRT48CL8A2U23D37GUSF2_ejd] : ############### ADD QSO Callsign: MI0NWA Date: 13.05.2021 18:46:45 Band: 10m Mode: FT8
2023-02-24 21:59:47.5179 INFO: [dje_z96VMACW2GZT6GB6EYAGTX_ejd] : [QRZCOM] Search start on MI0NWA (originally MI0NWA)
2023-02-24 21:59:47.9465 INFO: * [dje_z96VMACW2GZT6GB6EYAGTX_ejd][428 ms] : [QRZCOM] Search finished on MI0NWA (originally MI0NWA)
2023-02-24 21:59:49.5591 INFO: [dje_zVRT48CL8A2U23D37GUSF2_ejd] : QSO Callsign: MI0NWA Date: 13.05.2021 18:46:45 Band: 10m Mode: FT8 Saved
2023-02-24 21:59:49.5621 INFO: [AdifManagement] : Begin export single QSO to ADIF string
2023-02-24 21:59:49.5661 INFO: [AdifManagement] : Export QSO to ADIF file completed

If there is no other way in opening a new database I will do so but I still think there is only a wrong setting...

73s and thank you for your help

Stefan

3 more screenshots.

73s

Why did you decide to deviate from the method described in our user guide?

Hi Terry,

I was watching some YouTube videos and it worked without any issues as already said.. but I will refer to the method in the user guide for sure to have everything correct. Could you give me a hint where to check the manual for my problem to fix it on my own?

73s
Stefan

Hi Stefan,

think your problem is the enabled ADIF monitor. In my case it´s off and all is working fine with UDP only. If you have run
ADIF monitor and UDP it could be possible that each contact is stored twice ..... Check out without ADIF monitor enabled
in the configuration settings.

Hi Jürgen,

Many thanks for your reply.
I will definitely test that.
The curious fact is that I did not have any double contacts before and did not change any settings.. the ADIF monitor was also enabled before the problems occured.
I used the monitor to fetch missing QSOs from the Wsjt-x log if I forgot to open Log4OM.
I use UDP for logging from wsjt-x to Log4OM only, so I think missing QSOs will not be added this way..
Somehow the duplicates have a few seconds time difference and I don't know why they are added to Log4OM again.
Is there no setting to prevent duplicates when the time difference is only about a few seconds?
I think I uploaded my log from QRZ.com to Log4OM and the entries from the Wsjt-x log have some seconds time difference, maybe this is the reason.

73s
Stefan

Ok, after reading the User Guide I understand some settings better.
I deactivated the ADIF monitor and deleted the double entries, it took a while but now everything seems to be allright again

BUT:
When I forget to start Log4OM and log a few contacts to my WSJT-X adif file will they be added to Log4OM after opening it?
If not how can I manage this without getting double entries? What would be the best way?
I always thought the ADIF monitor is the right tool for this scenario.

regards

DO9KW wrote: 25 Feb 2023, 22:34 Ok, after reading the User Guide I understand some settings better.
I deactivated the ADIF monitor and deleted the double entries, it took a while but now everything seems to be allright again

BUT:
When I forget to start Log4OM and log a few contacts to my WSJT-X adif file will they be added to Log4OM after opening it?
If not how can I manage this without getting double entries? What would be the best way?
I always thought the ADIF monitor is the right tool for this scenario.

regards

Auto start Log4OM and WSJT then you cant forget

ADI monitor should only be used on software that has no other form of integration with software like Log4OM