Page 1 of 1

Please help - SABnzbd only starts when I RDP in on WHS 2011

Posted: December 7th, 2011, 1:56 pm
by Finchy
Hi guys

I'm having trouble with SABnzbd+ on my Windows Home Server 2011 since I installed it as a service a while back. I have installed 0.6.12 but have had the same problems on 0.6.10 for quite a while.

Basically, SABnzbd only seems to start running when I remote into the home server, and I just cannot work out what I need to do to fix it. I have followed the instructions for installing the services, have set it to log on with the administrator username/password, but it still won't run properly unattended. The helper is set to logon on as the local system account as per the instructions. Can anyone help me out please?

Also, why should it be installed as a service? I read that it 'should be' but haven't seen why. For info, it still does the same even if it's not installed as a service!

Thanks!

Re: Please help - SABnzbd only starts when I RDP in on WHS 2

Posted: December 7th, 2011, 2:15 pm
by shypike
Only when it runs as a service, it's independent of any logged-in user.
That's the way Windows works.
When running as a service it's also more robust as there is a helper service
that will restart the main service in case it crashes or becomes unresponsive.

BTW: WHS2011 is not a supported platform.
As long as it behaves as a normal Windows Server, it should work.

Re: Please help - SABnzbd only starts when I RDP in on WHS 2

Posted: December 8th, 2011, 1:47 pm
by Finchy
Ah, ok, thanks, that explains why it's best run as a service.

Any ideas why mine only runs when I RDP in? It seems to only start when the Admin account logs in, I need it running all the time (as it did before).

Thanks

Re: Please help - SABnzbd only starts when I RDP in on WHS 2

Posted: December 8th, 2011, 5:19 pm
by shypike
I setup WHS2011 under VMWare.
No issues so far.
When run as a service, it starts fine.
You did set service to "Automatic"?
Don't use "Automatic (Delayed start)".
Make sure you have the Helper service too, which should run under "Local System".
Should you want to access shares, make sure you run the main service under an appropriate account.