SageTV service error 1053

[GoldenTiger]

Hey all,

I'm using SageTV v5.0.4 on Windows Vista, and whenever I have the SageTV media center application running, it kills the service, and if I try to re-enable it I get the following message "Error 1053: The service did not respond to the start or control request in a timely fashion". I have owned Sage for awhile, and with Windows XP this was able to be solved by, under service properties, checking the "Allow this service to interact with the desktop". Now, however, under Vista, it's having no effect.

Any ideas? I have heard version 6 is fully compatible with Vista, but I don't want to pay for all the new features JUST to use it with Vista since that's all I need.

[BobPhoenix]

Hey all,

I'm using SageTV v5.0.4 on Windows Vista, and whenever I have the SageTV media center application running, it kills the service, and if I try to re-enable it I get the following message "Error 1053: The service did not respond to the start or control request in a timely fashion". I have owned Sage for awhile, and with Windows XP this was able to be solved by, under service properties, checking the "Allow this service to interact with the desktop". Now, however, under Vista, it's having no effect.

Any ideas? I have heard version 6 is fully compatible with Vista, but I don't want to pay for all the new features JUST to use it with Vista since that's all I need.Have no idea if this will work or not but I would suggest you give the Service a user id and password rather than using the system account. You might have better results.

[GoldenTiger]

I did try that, but it didn't work still, unfortunately. However, after a reboot, it now seems to be starting up properly upon reboot, so that will do since I won't be disabling the service under normal usage anyway :). What did throw me off is that it is listed under the Services tab in task manager instead of the Processes tab like it was in XP.

EDIT: Apparrently, the service starts fine if the client isn't open (the actual SageTV application), but if it is open it gives me this error. So, my workaround is going to have to be to run it in service mode with the UI not loading at startup, then just launch the app itself when I want to watch something.