Basecamp Error When Viewing File in Google Earth

 

This has been an ongoing problem for some time now but something happened recently to make it worse.

For over a year, an error message would appear in Basecamp when trying to view a file in Google Earth. The work around was to open Google Earth manually first. Now, with Basecamp V4.6.2 and Google Earth Pro V7.1.8.3036, that no longer works. The Basecamp error message appears whether or not Google Earth is already open.

Now to view a Basecamp .gpx or .gdb file in Google Earth, you first have to save the file and import it into Google Earth manually. Although I haven't tried it, EPE may be affected as well. I know it doesn't sound like a big problem but for those of us who maintain files, it is a major inconvenience.

I'm curious if anyone has found a fix for this.

Yes ...

Try this:

From the Command Prompt type the following as applicable and press ENTER:
(Make sure you are in the C: root directory)

"C:Program Files (x86)GoogleGoogle Earth Proclientgoogleearth.exe" /RegServer (works with Google Earth Pro in Win 7...10)

"C:Program FilesGoogleGoogle Earth Proclientgoogleearth.exe" /RegServer (Google Earth Pro in XP)

"C:Program FilesGoogleGoogle Earthclientgoogleearth.exe" /RegServer (Google Earth in XP)

"C:Program Files (x86)GoogleGoogle Earthclientgoogleearth.exe" /RegServer (Google Earth non-Pro on Win 7, 8.x and 10)

Note for those not used to using the command line in Windows, the double quotes in all of the examples are critical.
They MUST be there and in the indicated places or you'll get an error that the directory name is invalid. It won't harm anything; it simply won't work.

--
Where there's a will ... there's a way ... DriveSmart51LMT-S, DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20

The death of DOS has been greatly exaggerated!

Not Sure....

sussamb wrote:

Try this:

From the Command Prompt type the following as applicable and press ENTER:
(Make sure you are in the C: root directory)

"C:Program Files (x86)GoogleGoogle Earth Proclientgoogleearth.exe" /RegServer (works with Google Earth Pro in Win 7...10)

"C:Program FilesGoogleGoogle Earth Proclientgoogleearth.exe" /RegServer (Google Earth Pro in XP)

"C:Program FilesGoogleGoogle Earthclientgoogleearth.exe" /RegServer (Google Earth in XP)

"C:Program Files (x86)GoogleGoogle Earthclientgoogleearth.exe" /RegServer (Google Earth non-Pro on Win 7, 8.x and 10)

Note for those not used to using the command line in Windows, the double quotes in all of the examples are critical.
They MUST be there and in the indicated places or you'll get an error that the directory name is invalid. It won't harm anything; it simply won't work.

Thanks for the advice but I'm not sure how booting Google Earth from the C prompt solves the problem. Google Earth boots just fine from the desktop icon. Basecamp just doesn't detect that it is running.

Hmmm. ..

You're not booting it, you're correcting a setting to enable BaseCamp to boot it. See here for more info

https://forums.garmin.com/showthread.php?369770-BaseCamp-and...

--
Where there's a will ... there's a way ... DriveSmart51LMT-S, DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20

command line switch

You mean the command line switch /RegServer ?

dobs108 smile

Thank you!

sussamb wrote:

Try this:

From the Command Prompt type the following as applicable and press ENTER:
(Make sure you are in the C: root directory)

"C:Program Files (x86)GoogleGoogle Earthclientgoogleearth.exe" /RegServer (Google Earth non-Pro on Win 7, 8.x and 10)

Genius! Thanks so much. Now after doing the above (for my free Google Earth in a Win 10 PC) in BaseCamp with or without Google Earth already running, I can tell BaseCamp to View in Google Earth and it works.

This should be a FAQ since I've run into this several times after updating either BaseCamp or Google Earth (I can't remember which).

However, and this is a biggie, sussamb (and JM), at least on my PC, the POI Factory has problems with backslashes. In the above bolded command line entry of yours in this reply and your orginal reply, there are four missing backslashes that were removed by the POI Factory software.

Maybe JM can share a way to display backslashes in messages here assuming it's possible. If not, be aware that a backslash is needed in each of the following places in the command:

  • after the (x86) between the ) and G of Google
  • between the e and G of the two Googles
  • between the h and c of earthclient
  • between the t and g of clientgoogleearth

And if the rest of you are seeing backslashes and can offer advice on why I can't, I'd appreciate it.

For folks not wanting to add the backslashes manually, sussamb's link:

https://forums.garmin.com/showthread.php?369770-BaseCamp-and...

correctly shows the command line entry with backslashes.

cannot see them

I cannot see the backslashes but I know where they go.

dobs108 smile

Thanks

dobs108 wrote:

I cannot see the backslashes but I know where they go.

dobs108 smile

Thanks, I don't feel as alone or as paranoid now. cool

Aha, already solved:

http://www.poi-factory.com/node/46831

Lookie here. I can post a backslash: \

or two: \\

or between words: words\words

Here's the sussamb command that worked for me:

"C:Program Files (x86)\Google\Google Earth\client\googleearth.exe" /RegServer

Just to be clear. It's all on a single command line; i.e., the ...exe" /RegServer is all on a single line with a single space before the slash.

JM has a great FAQ on Composing Tips:

http://www.poi-factory.com/filter/tips

but the tip for how to create a backslash is not in the FAQ.

intentional

I am sure JM wants to prevent a hacker from running code on the server.

dobs108 smile

Ooops

CraigW wrote:

However, and this is a biggie, sussamb (and JM), at least on my PC, the POI Factory has problems with backslashes. In the above bolded command line entry of yours in this reply and your orginal reply, there are four missing backslashes that were removed by the POI Factory software.

Sorry missed that as I posted just before running out to drop daughter off sad

Glad you resolved it though!

--
Where there's a will ... there's a way ... DriveSmart51LMT-S, DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20

Thanks sussamb!

It took a bit of time but I finally got your command line trick to work.

A tip some others may need to know is you must be logged in as administrator, NOT just a user with administrator privileges. I got command line failure messages in Win 7 Pro until I discovered this.

Thanks again!

I tried, was in the root

I tried, was in the root directory, and get a 'COM registration failed. I check and I am logged as administrator.
Beats me. Don't know what to do

Help...

--
Have a safe trip

Solved, I was log as

Solved, I was log as administrator on the computer, but not on the command line.

--
Have a safe trip

Great

smile

--
Where there's a will ... there's a way ... DriveSmart51LMT-S, DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20