Version 2.2.26.0.0 KML Exports Not Working version

[k0did]

Greetings,

Been a while since I tried KML export, it seems that it is not working at least on my system.

1. Select QSOs from recent QSL list
2. Right Click Save Selected as KML
3. Expect it to be exported
The file is simply not created, I tried all of my drives, in folders on not in folders and the file is simply not created.

LOG4OM2 Log just says;
"23:12:00.089 Warn: [KMLManagement][GenerateQsoLocatorMap] : Executing D:\Log4OM_KML_20230307231153.kml FAILED! File not found"

[G4POP]

Try 2.26.0.7 Beta please

[k0did]

Install the Beta and it has the same result. Adi exports are OK with either the beta or the previous version.
00:03:31.269 Warn: [KMLManagement][GenerateQsoLocatorMap] : Executing D:\Log4OM_KML_20230308000323.kml FAILED! File not found.

[KI5IO]

Jerry,

Is Google Earth Pro working and updated?

Can you open that APP OK?

I just did a select, export and it saved the file and did an automatic open of Google Earth Pro with a mapping of the Q's I had selected.

I'm using V 2.26.0.7 (beta)

[k0did]

Great...... something local to my system. Yes Google Earth Pro is installed and working. For good measure I removed it and reinstalled.

Same Result.
Debug Log from live log only indicates the same File Not Found error.

08:29:44.579 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Performing QSO search on callsign MM7OSL
08:29:44.579 Debug: * [Countries][SearchCallsign][9403 ms] : Performing Search Callsign on call MM7OSL on date 3/8/2023 8:29:44 AM
08:29:44.591 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : No Clublog CQ ZONE found for MM7OSL
08:29:44.592 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Searching clublog exceptions
08:29:44.593 Debug: * [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext][13 ms] : QSO search on callsign MM7OSL completed
08:29:44.593 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call MM7OSL on date 3/8/2023 8:29:44 AM
08:29:44.603 Debug: * [Countries][SearchCallsign][8 ms] : Performing Search Callsign on call LX1MAX on date 3/8/2023 8:29:44 AM
08:29:44.612 Debug: [dje_z586HLBU4VEFHPX3BBTP7U5Z2M3DQ_ejd][MoveNext] : SPOT mode overriden to FT8
DX de LX1MAX: 14074.0 MM7OSL ft8 faker ? 0829Z JN29
08:29:44.612 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Performing QSO search on callsign MM7OSL
08:29:44.613 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call MM7OSL on date 3/8/2023 8:29:44 AM
08:29:44.623 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : No Clublog CQ ZONE found for MM7OSL
08:29:44.624 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Searching clublog exceptions
08:29:44.625 Debug: * [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext][12 ms] : QSO search on callsign MM7OSL completed
08:29:44.625 Debug: * [Countries][SearchCallsign][11 ms] : Performing Search Callsign on call MM7OSL on date 3/8/2023 8:29:44 AM
08:29:44.636 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call LX1MAX on date 3/8/2023 8:29:44 AM
08:29:44.645 Debug: [dje_z586HLBU4VEFHPX3BBTP7U5Z2M3DQ_ejd][MoveNext] : SPOT mode overriden to FT8
DX de LX1MAX: 14074.0 MM7OSL ft8 faker ? 0829Z
08:29:49.406 Warn: [KMLManagement][GenerateQsoLocatorMap] : Executing D:\Log4OM_KML_20230308082942.kml FAILED! File not found
08:30:30.711 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Performing QSO search on callsign MM7OSL
08:30:30.713 Debug: * [Countries][SearchCallsign][46077 ms] : Performing Search Callsign on call MM7OSL on date 3/8/2023 8:30:30 AM
08:30:30.727 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : No Clublog CQ ZONE found for MM7OSL
08:30:30.729 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Searching clublog exceptions
08:30:30.731 Debug: * [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext][19 ms] : QSO search on callsign MM7OSL completed
08:30:30.732 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call MM7OSL on date 3/8/2023 8:30:30 AM
08:30:30.742 Debug: * [Countries][SearchCallsign][9 ms] : Performing Search Callsign on call LX1MAX on date 3/8/2023 8:30:30 AM
08:30:30.752 Debug: [dje_z586HLBU4VEFHPX3BBTP7U5Z2M3DQ_ejd][MoveNext] : SPOT mode overriden to FT8
DX de LX1MAX: 14074.0 MM7OSL ft8 faker ? 0829Z JN29
08:30:31.164 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Performing QSO search on callsign R7BR
08:30:31.165 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call R7BR on date 3/8/2023 8:30:31 AM
08:30:31.178 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : No Clublog CQ ZONE found for R7BR
08:30:31.183 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Searching clublog exceptions
08:30:31.185 Debug: * [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext][20 ms] : QSO search on callsign R7BR completed
08:30:31.186 Debug: * [Countries][SearchCallsign][20 ms] : Performing Search Callsign on call R7BR on date 3/8/2023 8:30:31 AM
08:30:31.197 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call R3CL on date 3/8/2023 8:30:31 AM
08:30:36.093 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Performing QSO search on callsign R3CL
08:30:36.094 Debug: * [Countries][SearchCallsign][4897 ms] : Performing Search Callsign on call R3CL on date 3/8/2023 8:30:36 AM
08:30:36.108 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : No Clublog CQ ZONE found for R3CL
08:30:36.113 Debug: [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext] : Searching clublog exceptions
08:30:36.116 Debug: * [dje_zZ56SS7DZQU45YZ9E27D8X45JBLSFRY8LCZ_ejd][MoveNext][22 ms] : QSO search on callsign R3CL completed
08:30:36.117 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call R3CL on date 3/8/2023 8:30:36 AM
08:30:36.148 Debug: * [Countries][SearchCallsign][29 ms] : Performing Search Callsign on call OH5ZZ on date 3/8/2023 8:30:36 AM

[KI5IO]

Jerry,

I noted in the error log it indicates a "D" drive location. Is your Log4OM V2 installed on your "C" drive? Are you using or started to use a OneDrive.

I'm just thinking of some 'one-offs' that could be causing this.

[k0did]

LOG4OM is installed on drive C: (C:\Program Files (x86)\IW3HMH\Log4OM NextGen). I have tried KML exporting to drive C: and to drive D: as well as a local network drive the same issue of no file created happens on all drives in any folder I have tried.
In comparison, LOTW ADIF upload auto exports go to D:\LOTWup and have never failed and I can manual export ADIF to any drive/location I choose.

** This is wierd? The file is not created however, the export file name does show in the file explorer Recent File List (20) but the file does not exist in the location indicated, opening the file from this list launches Goggle Earth and then Google Earth errors saying the file could not be opened.

Other things I have tried that have not cured the problem, running as administrator, clean reboot, disable all Windows Security options, added an exception to not scan *.kml files. I have not uninstalled LOG4OM totally yet, not real excited about a complete reconfig or taking the chance of losing 6000 QSOs......

[KI5IO]

Jerry,

A puzzler for sure and the resolution might be staring us in the face, but we will continue to try and debug.

I just did a couple more tests. Selected a number of Q's from my Recent QSO (F7) tab and did an export and chose the "KML Connection Map" option.

Then a screen popped up asking me to verify which folder I wanted to save the file in. (I have a whole list of Log4OM V2 folders under "Documents / Ham Radio / Log4OM2". That is the default "Documents" folder located on my C drive where both Google Earth Pro and Log4OM V2 are installed.

Once I choose the folder to save the file in ... it is saved (for these tests I just left the suggested filename to be used). Once saved Google Earth Pro starts up, but actually is "behind" my Log4OM V2 Main UI. So I have to tap on the GEPro icon in the taskbar to bring it to the front/top for viewing.

FWIW I've attached a screen clip of my log file where the KML files have been created.

.

[k0did]

I will download a fresh copy on my laptop and go through the setup/configure and import a full ADIF export, maybe just a full reinstall will fix this.

What is the best way to approach a full removal and then a reinstall to not lose anything?

Jerry

[G4POP]

I doubt that will help better to reinstall Google earth and check file and folder permissions