View Issue Details

IDProjectCategoryView StatusLast Update
00019815 - Closed w/o ActionBugpublic2019-09-14 01:50
ReporterKB3NPHAssigned ToK7ZCZ 
Status closedResolutionnot fixable 
Summary0001981: Google Earth will not open from Satellite Tracker
DescriptionThe Google Earth software will not start when the icon is clicked in the Satellite Tracker toolbar.
TagsNo tags attached.
ModuleSatellite Tracking
Testing Beta Failed


has duplicate 0001910 closedK7ZCZ 5 - Closed w/o Action Google Earth will not start from within Sat Tracker 
has duplicate 0002691 closedPD9FER Ham Radio Deluxe Satellite tracker, Clicking Google Earth button giver an error 
related to 0002132 closedK7ZCZ Ham Radio Deluxe Lookup Google Earth 



2017-06-23 10:04

developer   ~0003270

Looks like Google has withdrawn support for the Google Earth SDK:

Mike, should we remove Google Earth from the product? Is there a replacement, or is fancy mapping just gone?


2017-06-23 10:21

administrator   ~0003271

This is a 2014 story. Google eventually retracted that position and has continued Google Earth. In fact, they just released Google Earth v9 on 18 April 2017. I don't know if it's the same kind of app or not.

I haven't tried launching Google Earth from Sat Track lately. But I do recall that - after Google did some upgrade to it, you had to open Google Earth first... and then when you selected Google Earth within Sat Track, it tracked as normal.


2017-06-23 11:46

developer   ~0003272

On my development machine, I installed Google Earth manually. I had to, in order to build (compile) the code.
I've started Google Earth then stopped it. I still can't launch Google Earth from the Satellite Tracker.

On my VM, Google Earth doesn't appear to be installed -- I can't see a way to run it as an application from the Start menu. Is setup meant to install Google Earth as an app so that users are able to start it and shut it down? I dont think it is doing so. Or are customers meant to do that manually?

The only mention I see of "Google Earth" in the user's meanual is that it is supported from Satellite Tracker. But the only user's manual I can find is from version 6.2. Have things changed since then?

When I try to launch Google Earth, the error I see in the debugegr is "Class not registered". The code is trying to create a given class from the Google SDK with OLE. The message means that either the class isn't [correctly] installed, or the program is asking for the wrong class ID.

It's possible that Google has updated the ID of the class across versions, which is fixable by us getting a new SDK. But the only source I find for an SDK leads to that announcement that Google has dropped support for Google Earth:


2018-03-01 04:16

viewer   ~0004333

Google Earth not opening in .791 for me


2018-03-11 12:14

developer   ~0004471

I've got this shelved change list to remove the use of the unsupported COM interface to Google Earth Desktop from the Logbook. This doesn't fix this issue, but it's a step towards cleaning up the dependency.


2018-03-11 12:42

developer   ~0004472

It looks like the Satellite Tracker is meant to use the COM interface to Google Earth Desktop to draw the satellite. It will pass an azimuth and elevation, and let the user adjust the camera for viewing hte satellite against the earth in the background.

Because Google no longer supports the COM interface to Google Earth desktop, I don't believe there's a way to dynamically control the application. The symptom reported in this bug is that Google Earth doesn't open; that's because we CoCreate the COM object and it fails:

    HRESULT hr = CoCreateInstance(EARTHLib::CLSID_ApplicationGE,

with REGDB_E_CLASSNOTREG. That error message means either the class we're trying to create (a local server for the Google Earth application interface implementation) isn't available on the machine, or we're asking for the wrong interface.

The interface definition comes from an old version of the Google Earth type library rescued from an older installation of the Google Earth desktop product. That version of the product is no longer supported by Google and can't be downloaded or installed. No new programmatic interface information is available, as far as I can tell, because Google no longer supports the COM interface.

At this point, all we can do is:

1) try to find a different interface to Google Earth. For some parts of the HRD product, the static features that KML prodvides are quite adequate. I don't think KML supports what we were doing from the Sattellite Tracker application. Maybe hosting a web page inside the app, then usnig Google Earth on the web page, then animating Google Earth from the web page using JavaScript? Maybe something else?

2) try to find a product that replaces Google Earth. Get licensing together, sort out the installation issues, and add the supporting code to the product.

3) remove this feature from Satellite Tracker.

Meanwhile, the SatTracker code fails to create the Google Earth interface and doesn't say anything to the user. I've prepared this shelve set to add an error message:


2018-03-14 09:14

developer   ~0004488

I've made this checkin which removes some disconnected code related to this issue.


2018-03-14 09:15

developer   ~0004489

I've re-opened this issue. The issue is fixable; we just have to decide which approach we'd like to take. I'm assigning this issue to WA9PIE so he can drive that decision.


2018-06-01 03:18

updater   ~0005161

Getting the error: Cannot load google earth, Interface class is not registered
I downloaded and reinstalled Google Earth again and it opens on itself just fine.
But this error is popping up on executing HRD Sattrack.exe

See screenshot

2018-06-01_10-15-48.jpg (21,540 bytes)
2018-06-01_10-15-48.jpg (21,540 bytes)


2018-06-03 17:07

developer   ~0005186

This issue is assigned to WA9PIE for input about the proposed fixes. Notihng heard, so far.


2018-06-28 12:10

administrator   ~0005522

Of my choices, here are my thoughts:

1. If it's possible, I'd like to fix our software so it works with the latest version of Google Earth Pro.
2. If #1 isn't possible, we could consider using NASA World Wind ( or Marble (
3. If #1 and #2 aren't possible, then let's do this.

These are my preferences in that order.


2018-07-01 16:31

developer   ~0005586

I don't understand what choice #3 is.

The other two choices need significant specification work, and their viability really rides on the details of what's desired in that specification. We should work together on figuring out what features are available, what solution is desired, and which geo package is the best match.


2018-07-09 21:46

administrator   ~0005648

These choices refer back to the 3 choices you describe in your comment from 2018-03-11 12:42.

Specifically, you said #3 is "3) remove this feature from Satellite Tracker."


2018-07-10 07:41

developer   ~0005651

Thanks for the clarification. The other two choices still need specification before we can take action.


2018-12-06 15:38

administrator   ~0006536

Remove the Google Earth button and feature from Satellite tracker.


2018-12-27 15:46

administrator   ~0006813

removing item


2019-06-27 12:09

updater   ~0008184

Still not removed and getting new tickets on it.


2019-07-01 17:37

developer   ~0008188

The Google Earth UI is disabled in the 6.7 branch with this checkin:

Note that the code is *not* removed, just disabled. Maybe Google changes their mind some day, or maybe we find an alternative.

Issue History

Date Modified Username Field Change
2017-02-17 12:54 KB3NPH New Issue
2017-03-08 00:06 WA9PIE Project 3 - Current Dev List => 2 - Next Dev List (Holding Area)
2017-06-23 10:04 K7ZCZ Note Added: 0003270
2017-06-23 10:04 K7ZCZ Assigned To => WA9PIE
2017-06-23 10:04 K7ZCZ Status new => assigned
2017-06-23 10:21 WA9PIE Note Added: 0003271
2017-06-23 11:46 K7ZCZ Note Added: 0003272
2017-07-23 01:20 K7ZCZ Relationship added has duplicate 0001910
2018-02-26 11:00 WA9PIE Project 2 - Next Dev List (Holding Area) => 3 - Current Dev List
2018-02-26 11:09 WA9PIE Status assigned => resolved
2018-02-26 11:09 WA9PIE Resolution open => fixed
2018-02-26 11:09 WA9PIE Fixed in Version =>
2018-02-26 11:09 WA9PIE Testing => Not Started
2018-02-27 09:56 WA9PIE Assigned To WA9PIE => K7ZCZ
2018-03-01 04:16 g3ypp Note Added: 0004333
2018-03-01 23:27 WA9PIE Status resolved => assigned
2018-03-01 23:27 WA9PIE Resolution fixed => reopened
2018-03-01 23:27 WA9PIE Fixed in Version =>
2018-03-01 23:27 WA9PIE Testing Not Started => Beta Failed
2018-03-11 12:05 K7ZCZ Relationship added related to 0002132
2018-03-11 12:14 K7ZCZ Note Added: 0004471
2018-03-11 12:34 WA9PIE Status assigned => resolved
2018-03-11 12:42 K7ZCZ Note Added: 0004472
2018-03-13 14:20 WA9PIE Resolution reopened => not fixable
2018-03-14 09:14 K7ZCZ Note Added: 0004488
2018-03-14 09:15 K7ZCZ Assigned To K7ZCZ => WA9PIE
2018-03-14 09:15 K7ZCZ Status resolved => assigned
2018-03-14 09:15 K7ZCZ Note Added: 0004489
2018-04-22 02:42 K7ZCZ Relationship added has duplicate 0002691
2018-06-01 03:18 PD9FER File Added: 2018-06-01_10-15-48.jpg
2018-06-01 03:18 PD9FER Note Added: 0005161
2018-06-03 17:07 K7ZCZ Note Added: 0005186
2018-06-28 12:10 WA9PIE Note Added: 0005522
2018-06-28 12:10 WA9PIE Assigned To WA9PIE => K7ZCZ
2018-06-28 12:10 WA9PIE Status assigned => feedback
2018-07-01 16:31 K7ZCZ Assigned To K7ZCZ => WA9PIE
2018-07-01 16:31 K7ZCZ Note Added: 0005586
2018-07-09 21:46 WA9PIE Note Added: 0005648
2018-07-09 21:47 WA9PIE Assigned To WA9PIE => K7ZCZ
2018-07-10 07:40 K7ZCZ Assigned To K7ZCZ => WA9PIE
2018-07-10 07:41 K7ZCZ Note Added: 0005651
2018-12-06 15:38 WA9PIE Note Added: 0006536
2018-12-06 15:38 WA9PIE Assigned To WA9PIE => K7ZCZ
2018-12-27 15:46 WA9PIE Status feedback => assigned
2018-12-27 15:46 WA9PIE Note Added: 0006813
2019-06-27 12:09 PD9FER Note Added: 0008184
2019-07-01 17:37 K7ZCZ Status assigned => resolved
2019-07-01 17:37 K7ZCZ Note Added: 0008188
2019-08-30 16:13 K7ZCZ Fixed in Version =>
2019-09-14 01:50 WA9PIE Status resolved => closed
2019-09-14 01:50 WA9PIE Fixed in Version =>
2019-09-14 01:50 WA9PIE Project 3 - Current Dev List => 5 - Closed w/o Action