Hi,
We’re having a problem trying to get Deadline 6 running as a service. It runs through all the installation properly but at the end throws up the error “Unknown error executing action” and doesn’t start the service. Just wondering if there’s any additional information we can get on why it might have failed.
Deadline 6 Beta 17
System:
Win 7 Pro SP1 64-bit
Intel Core i7-2600@3.4GHz
8GB Ram
Nick
Hey Nick,
After the installation runs, is the Deadline 6 Launcher Service shown in your Services list? If it is, are you able to start it manually, or do you get an error?
Thanks!
Hi Ryan,
No, only the Deadline Launcher is available as a service after installation.
Cheers
Nick
Strange, so it sounds like the service fails to even get created.
The installer writes to a bitrock_installer log in the temp folder (%TEMP%), so can you try running the installer again, and then send us the most recent bitrock_installer log after you get the error?
Thanks!
Hi Ryan,
Sorry for the delay. I’ve attached the error message and the bitrock installer log. Weirdly we’ve got it working on the 1st machine but we’ve since been unable to get it working on any of the other machines. Not sure the log really helps though because it says it created the service…
Nick
Hey Nick,
I wonder if it’s a permission issue that prevents the service from being created. When you’re prompted for your admin credentials at the beginning of the installation, are you entering the local admin credentials or a different user’s credentials? If it’s a different user, do you know if that user has permissions to create a service on that machine?
Cheers,
Hi Ryan,
Doing a little bit more digging it does look like it might be a permissions problem. We’re using our domain render user both to install and run the service which does have admin privileges on the local machine. We did have some issues over how the username should be put in to make it work with the service. We’ll do some more checking with different users and see if we can get to the bottom of it. I think part of the problem is the error’s a bit vague as to why it hasn’t worked…
Cheers
Nick
So I think we’ve now resolved this. It looks as if we weren’t allowing any users other than system to ‘Log on as a service’ in the local security policies on the machine. Once we fixed this it installed properly. One of the failed installs actually created the service but couldn’t run it so we manually input the login information and it started the service. This triggered windows to unlock the security options.
Thanks for you help.
Nick
