SageTV serivce with network encoders

[cheesyfan1]

Hey all,

I'm currently in the process of switching from another PVR service to SageTV. So far, I'm finding that SageTV is probably a much superior program after spending just a little bit of time with it. I'm running into a little problem and hope someone out there may be able to help.

My problem is that I can't get SageTV to recognize/find network encorders if the service is running. If I stop the service, the network encoders show up in the setup and all is good but as soon as I start the service up again they are no longer availble. I suppose I could just not use the service but that's actually one of the features I like best plus if the SageTV window gets closed accidently I know that recordings will still take place. I've done a little searching through the forums here and haven't found anything that directly correlates with my issue. The best thing I've found so far is that I should delay start the service but I haven't had the chance to try that yet.

Any advice would be most appreciated.

Thanks in advance.

[Skirge01]

Sounds like a permissions issue. What user account are you using to start the service? My guess would be "local system". If so, change it to a real user with admin access to everything, like your own user account has.

[cheesyfan1]

Skirge01,

Would you do that through the Control Panel->Admin Tools->Services->SageTV?

[razrsharpe]

either there or with the SageTVServiceControl.exe app (in your SageTV start menu folder)

[stanger89]

Are you running Vista or Win 7? It sounds like Sage is using a different sage.properties file when you're running in service mode and thus not seeing the definition for your network encoders. Make sure you've got them defined in the right properties file.

[owilsky]

I'm using DVBViewer Recorder unter Win7 32bit with UAC enabled. And I use service mode running as local system. But I recommend installing SageTV outside of C:\Program Files because of UAC. I installed in C:\SageTV and have given that folder full access rights to everyone.
Everything runs fine this way.

[Fuzzy]

I'd concur that it sounds like a problem of different sage.properties files being used. this would be caused by UAC, where the service is being run as a different user, so it is using the sage.properties in a different VirtualStore folder. As you are early in your sage setup, I'd do as Oliver recommended, and install sage in C:\SageTV. This will completely eliminate UAC concerns in regards to sage (which is NOT UAC aware), and simplify quite a bit on the road forward.

[cheesyfan1]

You guys nailed it. I was editing the wrong file. Thanks for the help.