service monitor strange behaviour (1 Viewer)

[ellismp2015]

I was seeing a client listed twice in Service Monitor so I uninstalled the server and deleted the database then reinstalled. Now the Service Monitor on the server pc is correctly showing the client and updating its connection status BUT the Service Monitor on the client pc shows server not connected and no clients.

If I reinstall the client pc I get the duplicate listing again.

What tells the Service Monitor on the client pc where to get its data? And why is it getting confused? I assume that the client is looking for the previous instance of the server (whereas the server is aware of the client but will show a duplicate entry if i reinstall the client) so how do I tell it I've reinstalled the server?

 

[morpheus_xx]

As soon as the ServiceMonitor is attached once to a Server, it remembers this connection.

After your reinstall (with deletion of DB/config), the new installation got also a new Server ID. To force a redetection in ServerMonitor on your client, please delete "C:\ProgramData\Team MediaPortal\MP2-ServiceMonitor\Config" and restart the monitor, it should automatically find your new installtion

 

[Lehmden]

By reinstalling the Server it most likely got a new ID. That's why the Service Monitor on the client did not show the connection because it still uses the old ID. You can change this by stopping Service Monitor and remove the following files from "C:\ProgramData\Team MediaPortal\MP2-ServiceMonitor\Config\" (assuming you did not change the default installation path of MP2)...
MediaPortal.Common.Services.SystemResolver.Settings.SystemResolverSettings.xml
MediaPortal.ServiceMonitor.UPNP.Settings.ServerConnectionSettings.xml

and, if exists, the corresponding .bak files...
Then start Service Monitor again and it should find the new server...

A similar cause is for the duplicate entries in Client lists. Also the client gets a different ID once you've reinstalled it...
But here the ID are stored in the Database (datastore.s3db) so you need to remove the DB or modify it with external tools to get rid of those entries. This is completely at your own risk. Never fiddle with DB or config files without a proper backup...

 

[ellismp2015]

Wow that was quick thanks!!