Hello all,
I have upgraded my Log4OM V2 to Rev. 2.21.1.0. After doing this I can no longer connect to the MySQL database which has worked without problems with earlier versions of Log4OM. Anyone here in this group that can help clarifying on this.
The application is run on a Windows 10 PC Pro fully updated with NET version 4.8.
I switched from SQLite to MySQL database after reaching 160.000 QSO's. This switch was uneventful and MySQL has been working until now.
When checking in Program Settings - Database - Check Connection the response is:
'Connection Test Failed, Database seems not valid' and questions marks next to Database Name, User Name, Password etc.
I use only the very basic functions of Log4oM V2. No radio control and other fancy functions are used. However, I use Log4OM V2 to upload QSOs to eQsl and LoTW.
I have experienced problems with importing ADIF files generated by WSJT-X and problems with uploading to LoTW (started after Log4OM V2 Ver. 2.18.0.0).
I believe that the WSJT-X generate ADIF Std. 3 files, see example ADIF header from WSJT-X generated ADIF below. So I don't understand why import to Log4OM V2 is rejected. When I upload the very same ADIF file to eQsl it is processed without problems. Please comment on this.
ADIF Export
<adif_ver:5>3.1.1
<created_timestamp:15>20220322 201200
<programid:6>WSJT-X
<programversion:5>2.5.4
<eoh>
These two additional problems are unsolved and I have been forced to upload manually ADIF files to LoTW. I now have several thousands QSO's that need to be imported to Log4OM V2.
Brgds
Peter
OX3XR
Updated Log4OM V2 to ver. 2.21.1.0, cannot connect to database
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Updated Log4OM V2 to ver. 2.21.1.0, cannot connect to database
Set Debug mode in help menu and then send a support request to Lele (AT) pisto.it
73 Terry G4POP
Re: Updated Log4OM V2 to ver. 2.21.1.0, cannot connect to database
Hello Terry,
Will send the requested data for investigation.
You did not comment on the ADIF file format generated by WSJT-X. Is it ADIF Std. 3 format?
Brgds
Peter
OX3XR
Will send the requested data for investigation.
You did not comment on the ADIF file format generated by WSJT-X. Is it ADIF Std. 3 format?
Brgds
Peter
OX3XR
Re: Updated Log4OM V2 to ver. 2.21.1.0, cannot connect to database
Terry, just for info. When starting Log4OM in Admin mode causes same behaviour.
Brgds
Peter
OX3XR
Brgds
Peter
OX3XR
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Updated Log4OM V2 to ver. 2.21.1.0, cannot connect to database
PeterOX3XR wrote: ↑15 Apr 2022, 13:15
You did not comment on the ADIF file format generated by WSJT-X. Is it ADIF Std. 3 format?
Version 3 but not the latest release definition
73 Terry G4POP
Re: Updated Log4OM V2 to ver. 2.21.1.0, cannot connect to database
Terry,
Thank you for the response, appreciated.
What exact ADIF revision No. 3 release No. (3.X.Y) is needed to have Log4OM V2
accepting an ADIF file e.g. generated by WSJT-X?
Do you have knowledge on resources persons who have experience in transforming
non-compatible Standard 3 ADIF files to the exact ADIF Standard/Version No. that
Log4OM V2 can import?
Brgds
Peter
OX3XR
Thank you for the response, appreciated.
What exact ADIF revision No. 3 release No. (3.X.Y) is needed to have Log4OM V2
accepting an ADIF file e.g. generated by WSJT-X?
Do you have knowledge on resources persons who have experience in transforming
non-compatible Standard 3 ADIF files to the exact ADIF Standard/Version No. that
Log4OM V2 can import?
Brgds
Peter
OX3XR
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Updated Log4OM V2 to ver. 2.21.1.0, cannot connect to database
Just because they use an old ADIF format it does not mean Log4OM can't import it it Will
73 Terry G4POP