Running spawner (and backburner) as a service problem

[tricky]

We have 'vanilla' installations of XP64 on a number of frshly built render slaves. I have installed vray and backburner server as services. I have instructed them to automatically start on the administrator account (manually entering the user 'Administrator' and the password 'password'). When I then tell the services to start, i get the following error:-

Error 1069: The service did not start because of a logon failure.

Any ideas what I am doing wrong? The install of these machines is a very basic install, and then we add it to the domain with the administrator account.

[flino2004]

I got some problems too installing them as a service, in the end I copied BBserver shortcut inside the the startup folder, and I run/kill vrayspawner using RefaMo...It works very well that way.

[tricky]

This is so frustrating. We have both vray spawner and bb server running as services on all our other render nodes (and they too are running XP64), so I don't know why we are having these problems.

Unfortunately, I think your solution involves having the nodes log in, but don't want them to have to log in at all. We just want them to be powered on, and once they have booted (but not logged in), the services will be running.

[tricky]

It seems that I can have spawner (and backburner) running as services on the Local System Account, but when I try to have it login with the administrator account, it will not run.

[tricky]

Sod it. TweekUI to the rescue!

[flino2004]

good for you. I'm curious maybe there is something that I don't know here, If you need BB server anyways, having it as server or startup Is not the same thing?

thanks,

Fernando

[instinct]

Having it as a service has quite some advantages/differences. Services can be monitored and autorestarted on crash for example. You can only have one instance running at a time. Services are more like "per workstation" whereas standard processes are "per user". Services work without logging in at all. For the last one this means they do not have a direct connection to the gui part of the explorer shell and hence can not have a UI at all. In addition if you have an Active Directory in a Windows Server environment you can control services remotely rather nicely.

Regards,
Thorsten

[flino2004]

Thanks Instinct for the explanation!!!
Ok, I'll try to get work as a service.

Fernando

[Morne]

I was also having issues running it as a service, so I ended up setting the nodes to autologon and then just added everything to windows startup as normal
works great. So all I do is switch on the pc and it works. (but without the extra benefits as Thorston mentioned)