Windows 7 x64 Service not working

General discussion about PS3 Media Server (no support or requests)

Windows 7 x64 Service not working

Postby Torpedro » Wed Dec 01, 2010 10:20 pm

Hi,
I'm using Windows 7 x64 and a Samsung TV.
When i start PMs in a normal User Session i immediately get the new Device on My Samsung. -EVERYTHING is ok, i can view media files.
If i start is as a Service (configured to ma User account) everything looks good (no Errors), but i don't see it on my TV.
I don't know what else i could do, please help me!

I already tried:
  • Start as Local Service
  • Start as my User
  • Start with wrapper.conf:
    wrapper.ntservice.account=.\MyUser
    wrapper.ntservice.password=Password

Java 1.6.0_21
Port 5001 are open and webservices (browser from PC)are working

PC: 192.168.0.199
TV: 192.168.0.196

The Debug Log for Normal Run looks like this, starting at Line 310 (before this line everything is identical):
Code: Select all
...
[New I/O server worker #1-1] DEBUG 21:56:24.098 Sent to socket: Expires: 0
[New I/O server worker #1-1] DEBUG 21:56:24.098 Sent to socket: Server: Windows_7-x86-6.1, UPnP/1.0, PMS/1.20.412
[New I/O server worker #1-2] DEBUG 21:56:26.553 Opened handler on socket /192.168.0.196:3532
[New I/O server worker #1-2] DEBUG 21:56:26.554 Handler infos: HTTP/1.0 : GET : description/fetch
[New I/O server worker #1-2] DEBUG 21:56:26.554 Received on socket: ACCEPT-LANGUAGE: en-us
[New I/O server worker #1-2] DEBUG 21:56:26.554 Received on socket: HOST: 192.168.0.199:5001
[New I/O server worker #1-2] DEBUG 21:56:26.554 Received on socket: USER-AGENT: SamsungWiselinkPro/1.0
[New I/O server worker #1-2] TRACE 21:56:26.554 Renderer Samsung Wiselink found on this address: /192.168.0.196
[New I/O server worker #1-2] INFO  21:56:26.558 Starting ping -n 3 -l 64000 192.168.0.196
[Thread-19] DEBUG 21:56:26.583 Pinging 192.168.0.196 with 64000 bytes of data:
[Thread-19] DEBUG 21:56:26.598 Reply from 192.168.0.196: bytes=64000 time=14ms TTL=64
[New I/O server worker #1-3] DEBUG 21:56:27.420 Opened handler on socket /192.168.0.196:3533 // Samsung Wiselink
[New I/O server worker #1-3] DEBUG 21:56:27.420 Handler infos: HTTP/1.0 : GET : description/fetch
[New I/O server worker #1-3] DEBUG 21:56:27.423 Received on socket: ACCEPT-LANGUAGE: en-us
[New I/O server worker #1-3] DEBUG 21:56:27.423 Received on socket: HOST: 192.168.0.199:5001
[New I/O server worker #1-3] DEBUG 21:56:27.423 Received on socket: USER-AGENT: SamsungWiselinkPro/1.0
[New I/O server worker #1-3] INFO  21:56:27.423 HTTP: description/fetch / 0-0
[New I/O server worker #1-3] DEBUG 21:56:27.425 Sent to socket: Accept-Ranges: bytes
[New I/O server worker #1-3] DEBUG 21:56:27.425 Sent to socket: Cache-Control: no-cache
[New I/O server worker #1-3] DEBUG 21:56:27.425 Sent to socket: Connection: keep-alive
[New I/O server worker #1-3] DEBUG 21:56:27.425 Sent to socket: Content-Length: 2056
[New I/O server worker #1-3] DEBUG 21:56:27.425 Sent to socket: Content-Type: text/xml; charset="utf-8"
[New I/O server worker #1-3] DEBUG 21:56:27.425 Sent to socket: Expires: 0
[New I/O server worker #1-3] DEBUG 21:56:27.425 Sent to socket: Server: Windows_7-x86-6.1, UPnP/1.0, PMS/1.20.412
[Thread-19] DEBUG 21:56:27.598 Reply from 192.168.0.196: bytes=64000 time=14ms TTL=64
[Thread-17] INFO  21:56:28.558 Stopping process: ping
[New I/O server worker #1-2] TRACE 21:56:28.561 Renderer Samsung Wiselink have an estimated network speed of: 73 Mb/s
[New I/O server worker #1-2] INFO  21:56:28.561 HTTP: description/fetch / 0-0
[New I/O server worker #1-2] DEBUG 21:56:28.563 Sent to socket: Accept-Ranges: bytes
[New I/O server worker #1-2] DEBUG 21:56:28.563 Sent to socket: Cache-Control: no-cache
[New I/O server worker #1-2] DEBUG 21:56:28.563 Sent to socket: Connection: keep-alive
[New I/O server worker #1-2] DEBUG 21:56:28.563 Sent to socket: Content-Length: 2056
[New I/O server worker #1-2] DEBUG 21:56:28.563 Sent to socket: Content-Type: text/xml; charset="utf-8"
[New I/O server worker #1-2] DEBUG 21:56:28.563 Sent to socket: Expires: 0
[New I/O server worker #1-2] DEBUG 21:56:28.563 Sent to socket: Server: Windows_7-x86-6.1, UPnP/1.0, PMS/1.20.412
[main] DEBUG 21:56:28.806 Waiting 250 milliseconds...
[main] TRACE 21:56:29.058 It's ready! You should see the server appears on XMB
[Thread-21] DEBUG 21:56:29.058 Setting multicast network interface: name:eth3 (Realtek PCIe GBE Family Controller) index: 11 addresses:
/192.168.0.199;



The Debug Log for Service Run looks like this, starting at Line 310:
Code: Select all
...
[New I/O server worker #1-1] DEBUG 21:57:43.825 Sent to socket: Expires: 0
[New I/O server worker #1-1] DEBUG 21:57:43.825 Sent to socket: Server: Windows_7-x86-6.1, UPnP/1.0, PMS/1.20.412
[WrapperSimpleAppMain] DEBUG 21:57:48.797 Waiting 250 milliseconds...
[WrapperSimpleAppMain] TRACE 21:57:49.049 It's ready! You should see the server appears on XMB
[Thread-18] DEBUG 21:57:49.049 Setting multicast network interface: name:eth3 (Realtek PCIe GBE Family Controller) index: 11 addresses:
/192.168.0.199;
Torpedro
 
Posts: 1
Joined: Wed Dec 01, 2010 10:01 pm

Re: Windows 7 x64 Service not working

Postby meskibob » Wed Dec 01, 2010 10:25 pm

I provide NO application support via PM or email, so please post your question to the forum per the Forum Rules.
meskibob
Moderator
 
Posts: 4784
Joined: Mon Jan 19, 2009 4:11 pm


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 3 guests