PowerScheduler Client not able to connect to server

[MaJo]

TV-Server Version: 1.0
MediaPortal Version: 1.0 RC2
MediaPortal Skin: Blue wide
Windows Version: Windows XP sp3
CPU Type: Athlon 64 3200+
HDD: 250 GB + 120 GB
Memory: 1 GB PC3200 single channel
Motherboard: Soltek K8T890 PRO-939
Video Card: ATI Radeon X600
Video Card Driver: 8.522.0.0
Sound Card: VIA on board - Vinyl AC'97
Sound Card AC3: Optical
Sound Card Driver: 6.14.1.4180
1. TV Card: Hauppage HVR 1300
1. TV Card Type: analog/DVB-T
1. TV Card Driver: 2.119.25023.0
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: MPV
MPEG2 Audio Codec: MPA
h.264 Video Codec: CoreAVC Pro 1.7.0.0
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: Hauppage
TV:
TV - HTPC Connection: DVI

I have recently for the first time ever installed a TV-server. Everything is on a new clean Windows, and I'm running both server and client on the same machine. I get everything to work, including TV (at least the DVB-T. Having problems with switching between analog/digital), but when I enable the PowerScheduler Client I get the following error message from MP:

2008-09-18 20:10:32.343750 [ERROR][MPMain]: Unable to start plugin:MediaPortal.Plugins.Process.PowerSchedulerC lientPlugin exceptionystem.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Bool ean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---

Server stack trace:
at System.Net.HttpWebRequest.GetRequestStream()
at System.Runtime.Remoting.Channels.Http.HttpClientTr ansportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream)
at System.Runtime.Remoting.Channels.Http.HttpClientTr ansportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.SoapClientFormatt erSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleRe turnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateI nvoke(MessageData& msgData, Int32 type)
at TvEngine.PowerScheduler.Interfaces.IPowerControlle r.RegisterRemote(String standbyHandlerURI, String wakeupHandlerURI)
at MediaPortal.Plugins.Process.PowerScheduler.OnResum e()
at MediaPortal.Plugins.Process.PowerScheduler.Start()
at MediaPortal.Plugins.Process.PowerSchedulerClientPl ugin.Start()
at MediaPortal.GUI.Library.PluginManager.Start()

So, it seems like the client cannot properly connect to the remote (?) server. MP works fine with PS enabled but it will not go to sleep (S3) or wake up automatically. With the remote I can turn off and on without problems. I have both client and server PS set on suspend after 10 min. Does anyone understand the error message or where I should start digging? As digital TV works the client apparently is capable of connecting to the server sometimes...

I'd be very grateful for some help!

/MaJo

[hoborg]

Hello. I have exactly same problem. Did you find solution?

XP SP3+MP RC3

My error log:
2008-10-13 16:32:20.531250 [ERROR][MPMain]: Unable to start plugin:MediaPortal.Plugins.Process.PowerSchedulerC lientPlugin exceptionystem.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:31457
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Bool ean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---

Server stack trace:
at System.Net.HttpWebRequest.GetRequestStream()
at System.Runtime.Remoting.Channels.Http.HttpClientTr ansportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream)
at System.Runtime.Remoting.Channels.Http.HttpClientTr ansportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.SoapClientFormatt erSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleRe turnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateI nvoke(MessageData& msgData, Int32 type)
at TvEngine.PowerScheduler.Interfaces.IPowerControlle r.RegisterRemote(String standbyHandlerURI, String wakeupHandlerURI)
at MediaPortal.Plugins.Process.PowerScheduler.OnResum e()
at MediaPortal.Plugins.Process.PowerScheduler.Start()
at MediaPortal.Plugins.Process.PowerSchedulerClientPl ugin.Start()
at MediaPortal.GUI.Library.PluginManager.Start()

EDIT:
Ok, the solution is simple, just enable powersheduler plugin inside TV Server.