What is this all about?  The operations center worked fine earlier this morning, then I updated it.

 

 

 

 

Running win 10, and I have all the admin rights, etc. 

 

Not running FSX anymore but I do own the FSX version as well as the Prepar3d version.  But very bizarre that this thing worked fine just a couple hours ago, before I updated things.

 

Name is Mark A Sewell, in case that is required here.

 

 

Not running FSX anymore but I do own the FSX version as well as the Prepar3d version.  But very bizarre that this thing worked fine just a couple hours ago, before I updated things.

 

Do you have the Estonia Migration Tool installed?

 

Indeed I do have it installed.

Indeed I do have it installed.

 

That's why. The EMT adds a bunch of different P3D registry values with the intent of confusing installers into installing various versions of P3D software (and FSX software in some cases) into another. The Ops Center is built to work with all versions of P3D (after 2.5), so it's seeing multiple values in the registry and, understandably, getting confused. Remove the EMT and remove the false registry values and it'll work again.

 

Thank you sir, I will do just that.

 

Cheers

 

 

Thank you sir, I will do just that.

 

Welcome!

 

 

Name is Mark A Sewell, in case that is required here.

It is required in PMDG Forums per this - http://forum.avsim.net/topic/245586-you-must-sign-your-full-real-name-to-posts-to-use-this-forum-posts-without-names-will-be-deleted/. Right where you have Drink Locally, Fly Globally. Sorry.

 

I have removed EMT and also the registry values. Still no change. I'll restart the computer and try again.

I have removed EMT and also the registry values. Still no change. I'll restart the computer and try again.

Yeah, not surprising. Removal of the "tool" does not necessarily undo the damage. It's basically a virus. I'm always surprised anyone uses it.

No worries, I'll just uninstall PMDG and try it again.

 

This is a little strange, though, as I was using the operations center just fine this morning. The migration tool was never an issue before. If I'd never updated the thing, I'd probably still be using it.

Reinstalling NGX didn't make any difference.

 

I am tempted to think that something is wrong here this version of Op Center as it worked fine today before I ran the update -- but if that were the case then I'd not be the only one howling right now.

 

I guess I am going to have to live without it for a while. Going to test the aircraft itself to see if it is jacked up as well.

 

 

I am tempted to think that something is wrong here this version of Op Center as it worked fine today before I ran the update

 

Have you looked at the operations center log file to see if there are clues?  This file is found in the AppData\Roaming\PMDG\PMDG Operations Center folder.

 

No but that is a damn good idea. I have just uploaded to those as attachments to my support tickets as well.

 

You don't suppose this here is part of the problem, do you?

 

Finding P3D

15:08:47.366 Prepar3D SetupPath registry key was located but could not be read.

 

hmmmm

 

I might be about overdue to just ditch version 2.5 and migrate on over to version 3.2 pretty soon anyway. I'd been waiting for V3 support from one last developer, VRS, and that just came out the other day.

 

We'll see what the support folks have to say first.

 

And thank you guys for the assistance.

 

 

15:08:47.366 Prepar3D SetupPath registry key was located but could not be read.

 

Exactly, PMDG Product Support can help you with this.

Hello I had the same problem with 777 base pack and expansion pack.The operations center seems to not be reading a valid register license after updating.I uninstalled and reinstalled both but the problem remained. I wrote a ticket on the 22nd but no answer yet maybe because of holidays.

I will appreciate any help on this matter

Best Regards and happy landings

 

Mauricio Villada