SageTV Service Will Not Start - XP SP2

[jason531]

Hi,

I cannot get the SageTV Service to run. When I try to start it, I get "Could not start the SageTV service on Local Computer. Error 1068: The dependency service or group failed to start."

If I look at the Event Viewer, I get the following error for the Net Logon service "This computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration."

I also get this error in the Event Viewer: "The SageTV service depends on the Net Logon service which failed to start because of the following error:
%%0".

It looks like the SageTV service depends on the Net Logon service, but the Net Logon service will not run because I am part of a workgroup, not a domain.

Any ideas? Thanks.

JasonH

[gplasky]

Reboot your machine and then try it.

Gerry

[jason531]

I was pretty sure that I already tried that, but I tried it again and it works. Thanks.

[Alwayslearnin]

I am having the exact same problem. I am using the trial version of Sage for WAF trial.

I installed an additional slave hard drive to store the videos and Sage service stopped working. It had been working up until now.

I have both Sage and Sage Client installed on the same machine. I am also testing the MVP client.

I have rebooted several times. I am running the current version available for trial download.

Thanks for your help!

[gplasky]

Make sure you're using a user with a password to log in for the service. Make sure you are using UNC and not mapped paths for the drives.

Gerry

[Alwayslearnin]

Originally Posted by gplasky

Make sure you're using a user with a password to log in for the service. Make sure you are using UNC and not mapped paths for the drives.

Gerry

I've done that and I have attempted to add another video directory labelled \\mycomputername\mydrivelabel\myfolder, but sage does not recognize it. It appears to be an issue in XP, I can see the folder, and through windows explorer, I can access it with no problem. If I try to map using the UNC, no luck, If I try to access it via Internet explorer, I can see it but I cannot access it. Sage records to it as long as Sage is open.

I am an administrator on the box, so that should not be an issue. The ID I created to run the sage service is also an administrator, and I have added a password for it. The drive and the folder have been set to share on the network.

This obviously can be done, as many of you are doing it, but perhaps those of you that are more familiar with XP security can provide some ideas here?

Oh, I deleted my letter drive mapping in sage, and rebooted, but the services still would not start. I received the same error as mentioned in the first post of this thread.

Thanks

[bbig119]

Any updates on this? I'm getting this error.

[MattJackson86]

Same here...installed the latest beta and getting this issue. HELP!!

EDIT: Must set Net Logon Service to Auto and Reboot.

[Slickferret]

I installed 6.0_19 and rebooted. Suddenly I can't start the SageTV Service. I reinstalled 6.0_18 and it does not fix the problem. Version 6.0_18 used to start the service with no problem. Now that I have gone to 6.0_19 and back, even 6.0_18 will not work. It does not matter how many times I reboot. Manually restarting the service fails with error #1053. I hate software updates with bugs!!

SageTV service not running properly is currently a common problem on several threads here. It was working just fine on my system until I went from 6.0_18 to 6.0_19. That was the fatal flaw. I cannot even go back to 6.0_18 to get it to work again. Serious programming bugs.

I just installed 6.0_19 over 6.0_18 two days ago. Version 6.0_18 worked fine with the usual Sage bugs (can't see all of the import files, etc.). Upon upgrading to 6.0_19 and rebooting I cannot start the SageTV Service. If I manually start the service I get error #1053. I then reinstalled 6.0_18 over 6.0_19 and rebooted (copious amounts of rebooting). Even going back to 6.0_18 does not fix the problem. My guess is that 6.0_19 puts something into the registry which prevents the service from running. Switching back to 6.0_18 apparently does not remove that bug in the registry and so 6.0_18 does not work, even though it worked in the past. I am running fully patched Windows Media Center SP2; windows firewall off; Hauppauge 500 and Hauppauge PVR-USB; Most of the suggestions by SageTV so far sound like garbage. I think we have a registry problem from the new software.

[Opus4]

Is the UI starting automatically at boot time also? If so, try having it not start automatically & manually start it after the service is running.

The Windows MCE services that grab the tuners are stopped?

Have you configured the service to log in as a user w/a password? Have you tried using services.msc to configure the service to allow it to interact with the desktop?

- Andy

[Opus4]

Slickferret: please post your service problem in a single place, instead of every thread you can find via the forum search tool. I merged all your similar posts into the one above.

- Andy

[gplasky]

Originally Posted by Slickferret

I installed 6.0_19 and rebooted. Suddenly I can't start the SageTV Service. I reinstalled 6.0_18 and it does not fix the problem. Version 6.0_18 used to start the service with no problem. Now that I have gone to 6.0_19 and back, even 6.0_18 will not work. It does not matter how many times I reboot. Manually restarting the service fails with error #1053. I hate software updates with bugs!!

SageTV service not running properly is currently a common problem on several threads here. It was working just fine on my system until I went from 6.0_18 to 6.0_19. That was the fatal flaw. I cannot even go back to 6.0_18 to get it to work again. Serious programming bugs.

I just installed 6.0_19 over 6.0_18 two days ago. Version 6.0_18 worked fine with the usual Sage bugs (can't see all of the import files, etc.). Upon upgrading to 6.0_19 and rebooting I cannot start the SageTV Service. If I manually start the service I get error #1053. I then reinstalled 6.0_18 over 6.0_19 and rebooted (copious amounts of rebooting). Even going back to 6.0_18 does not fix the problem. My guess is that 6.0_19 puts something into the registry which prevents the service from running. Switching back to 6.0_18 apparently does not remove that bug in the registry and so 6.0_18 does not work, even though it worked in the past. I am running fully patched Windows Media Center SP2; windows firewall off; Hauppauge 500 and Hauppauge PVR-USB; Most of the suggestions by SageTV so far sound like garbage. I think we have a registry problem from the new software.

Any time you update SageTV you have to setup the username and password again. It's a Microsoft thing.

Also on the 1053 error, normally this error comes from:
a) the account that the service is starting under doesn't have permission to
read from a required directory (usually the one where a dependent DLL is
located),
b) the account that the service is starting under doesn't have the privilege
to "run as a service" on the local box, or
c) the application is configured to run in the local logged on user account,
and no one is logged on.

In other words, this is nearly always a permissions issue. From my experience, I suggest that you look again and double check the user you have it configured for.

Gerry.

[deliberate]

Originally Posted by gplasky

Any time you update SageTV you have to setup the username and password again. It's a Microsoft thing.
Also on the 1053 error, normally this error comes from:
a) the account that the service is starting under doesn't have permission to
read from a required directory (usually the one where a dependent DLL is
located),
b) the account that the service is starting under doesn't have the privilege
to "run as a service" on the local box, or
c) the application is configured to run in the local logged on user account,
and no one is logged on.

Is this buried in one of the FAQs someplace?

I'm running the service OK on my Win2k (no user) but I did have a devil of a time when I upgraded from Sage5 to Sage6 this past weekend and got caught in some sort of non-stoppable but never completing Sage Service start-up. I only got out of it by using the best Sage tool I've found so far: **flail mode** Eventually it stopped but only the gods knows why. Working now OK.

TIA,
- Don

[GKusnick]

Originally Posted by Slickferret

I then reinstalled 6.0_18 over 6.0_19...

As a general rule, when reverting to an earlier version of any software, you should uninstall the later version completely before reinstalling the earlier version. Installing earlier on top of later generally does not work, since the installer sees newer versions of the files already installed and declines to overwrite them with older versions.

[rickgillyon]

Before updating Sage always take a copy of the SageTV folder first. Makes backing out a real doddle...

[Slickferret]

Update: I have two SageTV licenses. Both were upgraded from 6.0_18 to 6.0_19 at the same time. Both had the same problem - SageTV service would not start automatically nor would it start manually. Starting it manually would produce error 1053. There are no password or userID's in use here. The software was installed for anyone to use on the computer. The account used when it was installed was a system administrator account. This is the same account being used when trying to start the service or make any changes to it. One computer is running on Window XP Home and the other is running Winodws XP Media Center. I have Trend Micro Antivirus on both computers. Windows Firewall is turned off onboth computers. (The 6.0_18 computer additionally has webroot spysweeper-see below). Both computers have one Hauppauge 500cme card, and either a Hauppauge USB-PVR or USB2-PVR capture card also.

I left 6.0_19 on one computer (XP Home) but reinstalled 6.0_18 over 6.0_19 in the other computer (XP Media Center). Once 6.0_18 was reinstalled in that one computer, the service would not work even after rebooting several times and manually starting it. Error 1053 was always seen. However, the next day, the 6.0_18 version computer would then run the SageTV service. Something occurred overnight. There wasn't any reboot and I didn't mess with it. I have sole access to this computer - no other users. I can only think that SageTV contacted the provider to obtain updated program information. The antivirus program checks for updates every 4 hrs too.

The 6.0_19 computer still will not allow SageTV service to run - error 1053. There is no username nor password issue in play here. SageTV Tech support instructed me to go into the services panel for SageTV service and to check the box for allow it to interact with the desktop. This was done but the service would not run. I rebooted with this option checked and it still will not run the service - error 1053. Neither automatically nor manually. I will check it tomorrow to see if the program contacting the service provider fixes it, if that was the fix for the 6.0_18 issue.

[Opus4]

If you haven't done so already, you can enable debug logging to see if the log has any info.

With the error you are getting, I'm not sure if it even gets to the point of making a log, but it shouldn't hurt to try it.

- Andy

[GKusnick]

Originally Posted by Slickferret

This is the same account being used when trying to start the service or make any changes to it.

The question is not what account you're logged into when configuring the service. The question is what account have you configured the service itself to log into. If you haven't configured an account for that (and typed in a password for it), then very likely the service does not have access to some resource it needs. For some reason the Sage installer resets this to LocalSystem, so you need to reconfigure the service account each time you reinstall. Forgetting to do that is the most common reason for service failures after upgrading.

[Jake]

I think (hope) I have found the ultimate PVR, but have this problem with the tv service not starting as required.

I would like the service to start each time my pc is booted up but it fails with the message below (from the event log).

Timeout (30000 milliseconds) waiting for the SageTV service to connect.

Followed by:

The SageTV service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

I can start the service manually without any problems, I simply cannot understand why it is not starting at bootup?

When checking the entry in the services list from Admin tools, I can see the service has the following attributes:

Startup Type: Automatic
Log On: My admin user account that I use daily
Recovery: Restart the Service
Second failure : Restart the Service
Subsequent failures: Restart the service

I have also tried with the Log On: set to Local System Account and it still doesn't start at boot up.

Any help appreciated as my trial will be up in a few days and I really do need this working.

Thanks in advance.

[Jake]

I have a workaround of sorts for anyone interested.

I have added a task to scheduled tasks to do a net start one minute before my scheduled recordings which are at the same time each day. Far from ideal though.

C:\WINDOWS\system32\net.exe start Sagetv

Obviously replacing the directory to whatever is the path to your system dir.

Any feedback on why the service will not start when the pc boots would be mucho appreciated