Mac MBServer, Windows ServerWMC: The socket is not connected

[c0g 0]

I have ServerWMC on my windows box and MBServer running on my mac server. I can telnet to the ServerWMC instance from the mac and it seems to connect okay so I don't think there's a problem with my firewall.

 

I edited wmc2mb.xml directly on the file system because it didn't seem to stick when I edited in the user interface. I get a popup "The socket is not connected" when setting it in the UI and see Status: Unavailable (The socket is not connected) in the LiveTV section of the UI.

 

ServerWMC log: http://pastebin.com/UWqaHYNL 
MB log: http://pastebin.com/0xuLAq7D

Edited July 2, 2014 by c0g

[krustyreturns 191]

In the swmc log, it seems to not be able to access its config file.  See:

Error: Access to the path 'C:\ProgramData\VDsoftware\ServerWMC\config.xml' is denied.

 

Is there a chance the first time you ran swmc it ran with elevated privileges?  That would explain why it can't access this config file now.  Try blowing away the VDsoftware directory above by hand and re-running swmc.  

[c0g 0]

Fixed that, SWMC now seems to notice the MediaBrowser try to talk to it but MB still says the thing about sockets not connected. In SWMC's UI it says Clients online: MediaBrowser.

 

http://pastebin.com/V95sf73J

 

Tom

[krustyreturns 191]

Well swmc says everything is fine, it shows that mbs has connected (looks like you switched ports back to 9080).  You cut off the log there, but it would be interesting to see if swmc gets any other command from mbs after the connection.  I don't know why mbs is reporting the socket is still not connected.  

[c0g 0]

That was the full log. Nuking VDsoftware changed the port for me.

 

I've left it running since but it just mentions a maintenance timer: http://pastebin.com/RTdpP56r

[krustyreturns 191]

Did you change the port to 9080 in the plugin too?