locked Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"


 

Hi John, 

Everytime wsjtx creates a new file it erroneously creates the bad header record. You are deliberately forcing it to create a new log file by renaming the old one.
Most loggers I think can cope with importing a log file and ignore those records it imported before.

73 Phil GM3ZZA

On 7 Sep 2020 18:00, "John L. Broughton" <2silverhondas@...> wrote:
That file contained all the contacts I made in the prior session. When I opened the next session, the eoh had been changed to eh.

My habit is that most every day, I save the wsjx_log.adi to another name and a new file is created the next time I open WSJT-X. I upload the daily files to LoTW and eQSL, import the file to my HRD log (I like it as it is handy for displaying all the essential elements of a QSO when I have to check a QSO for confirmation purposes on QRZ or eQSL), and then import my LoTW log into QRZ. I like to do all that manually rather than logging each contact directly into some other log.

I rely on the running log in JTAlert to flag worked before stations, wanted calls/DX/states, etc.

73,

John, WB9VGJ
On 9/4/2020 1:23 PM, Jim Preston N6VH wrote:

On 9/3/2020 6:29 PM, John L. Broughton wrote:
Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ
--
John L. Broughton
wb9vgj@...
2silverhondas@...
www.wb9vgj.us

John,

Since that is your entire file, and you have been using WSJT-X for several years, then that indicates that something is either re-naming or deleting your previous file. Other wise, that file would have many more entries in it. The only way I know that that could happen, would be if you click on File/Erase wsjtx_log.adi. Since I don't think that is happening, I have no idea what is causing the problem, but I am reasonably certain it is not WSJT-X. I don't think an AV program would pick on that particular file. There must be something on your computer that is causing this.

73,

Jim N6VH





    

Y

--
73 Phil GM3ZZA

Join main@WSJTX.groups.io to automatically receive all group messages.