I have an odd one-   after a recent upgrade where MI's were swapped, the old engine became the lookup/GPS server, and a new engine was installed,   I have a phantom host in the health monitor.   It appears in all the health monitors,  and throws them all to red alert status, as it's not real, and therefore can't be found.    

Anyone seen this,  or killed it?

TIA

JDS

Is it a hostname you recognize? What happens if you try to ping that machine? Something, somewhere is running Framework that you don't know about. When you set up your new GPS/Lookup, did you wipe the slate clean or uninstall MI and reinstall Lookupand stuff?

Lastly, what version of Interplay are you using?

1.5,  the hostname was the original "workgroup" name-

It's not someone running framework, as it would show processes,  this has no "friends" that way.

this was an Uninstall the engine, and re-install lookup & stuff.

If the phantom wasn't running Machine Monitoring service, then it wouldn't show up in the Health Monitor, correct?

I'm assuming you changed the hostname of the system when you changed it from an Engine to a GPS. Was it a member of an AD domain? Did you unjoin the domain, also? I'm just throwing darts here.

But if it was running the machine monitoring service, it would show processes I would think,  even just the free disk size.

yep,  hostname changed, and we aren't active directory.   The old hostname of that GPS server is attached to the new hostname of the Primary Engine, at a different IP address.

Hi Jeff,

If you look in the registry settings of the LookUp server(s), there may be an instance of your old workgroup lingering.

Look in:

HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs\avid\workgroups\avid technology incorporated\data\com\avid\workgroup\remoting\setting\groups

There may also be a group locator folder in the key above groups:  group locators, delete that key. There should only be your current workgroup.

Also look for and delete old hostname ServiceIDs, but Not your current/new hostname ServiceIDs.

Deyner Seals

I'll take a gander tomorrow,  thanks, Deyner.

JDS

Found it-

Wasn't the registry,  it was an "expected machine" entry in the Lookupserver's System configuration service tab.   Removed it, and clean.

No more false failures,   WIN.

JDS

Good one to know.