UNABLE TO PLAY: STREAM2.0 (1 Viewer)
- Thread starter robbo100
- Start date
- Thread starter
- #33
Bugger!!
Try running TCPView to see what is using the port
To keep wifey happy switch to UNC (just a temporary fix) until RTSP is fixed
J.
Jay
This is a different problem to the port issue now, it is a problem with the tuners becoming unavailable.
- September 1, 2008
- 21,544
- 8,236
- Home Country
-
New Zealand
- Thread starter
- #36
The logs give the same as before. But I will double check and post them if they differ in any way.
I wonder if it might be simpler to just have a batch file that runs after recovery from standby which stops the TV service, pauses for 3 secs and then starts the TV service?
I wonder if it might be simpler to just have a batch file that runs after recovery from standby which stops the TV service, pauses for 3 secs and then starts the TV service?
Its crude to do that...if its MP related, then lets try and fix it - as opposed to work around the issue.
If its a driver/hardware issue...then lets bodge away
You could look at something like StandbyHelper....or if running W7 simply use Task scheduler with the relevant power/kernel based triggers to stop and start the service.
Have you tested to seee if its purely a timing issue - increased th TVServer delay right up high....
J.
If its a driver/hardware issue...then lets bodge away
You could look at something like StandbyHelper....or if running W7 simply use Task scheduler with the relevant power/kernel based triggers to stop and start the service.
Have you tested to seee if its purely a timing issue - increased th TVServer delay right up high....
J.
- Thread starter
- #38
Thanks Jay,
I have increased the timing and I will see how things go again.
This all went wrong when I moved all the components (of my new server), into the final ITX case (the case arrived 4 days after the rest of the kit). Before the case change, everything was working correctly, so maybe there is some problem with heating or something (it is a tight fit with few fans). That said, the failure can occur if you turn the server on for very short times, so I don't think it would have the chance to heat up enough to be the cause of the problem. I wonder if it might be a porrly seated card or connector or something (I might try to reseat them all tonight.
I will keep kicking the can!
I have increased the timing and I will see how things go again.
This all went wrong when I moved all the components (of my new server), into the final ITX case (the case arrived 4 days after the rest of the kit). Before the case change, everything was working correctly, so maybe there is some problem with heating or something (it is a tight fit with few fans). That said, the failure can occur if you turn the server on for very short times, so I don't think it would have the chance to heat up enough to be the cause of the problem. I wonder if it might be a porrly seated card or connector or something (I might try to reseat them all tonight.
I will keep kicking the can!
- Thread starter
- #40
I did quite a lot of work to it, including "modifying" my PSU. It is not a modular PSU and it is a tight case with little ventilation, so I cut off the unwanted molex connectors close to the PSU and isolated them, but I can't see how that would be a problem (since they weren't connected before in any case). I will open up the case again and make sure everything is pressed home correctly just in case.