starting launcher via psexec

[LaszloSebo]

We have an issue where the launcher stops working on a bunch of slaves (Jon is aware, its been reported earlier).

To work around this (and so that i dont have to manually log into 200 machines and start the slave), i am setting up a remote script, that starts the launcher via psexec.

However, it seems that the psexec started launcher process can not be communicated with… any ideas why?

I start it with this command:

psexec \lapro0104 -u -p -d -i 0 -w “C:\Program Files\Thinkbox\Deadline6\bin” “C:\Program Files\Thinkbox\Deadline6\bin\deadlinelauncher.exe”

It starts the launcher, the icon shows up on the toolbar (well, at least on our xp machines,… still trying to figure out what hte heck is going on on win7). But when i then try to send that launcher remote commands, i get the usual:

Machine Name Command Time Stamp Status Results
lapro0104 ForceRelaunchSlave LAPRO0104 2013/08/29 16:56:46 Failed Failure: cannot accept a connection because Remote Administration has been disabled under the Launcher Settings in the Repository Options

Any ideas?

[LaszloSebo]

The launcher log has a couple of these lines, which im sure is related:

2013-08-29 17:02:08: WARNING: An error occurred while trying to obtain user’s access level for Launcher Features; falling back on default access level

[LaszloSebo]

If i run it as an administrator, it seems to be fine… Would i have any issues if the slave is ran as admin though?

[rrussell]

It sounds like as a normal user, the Launcher might be having problems connecting to the Repository and/or the database. Is there anything else in the launcher log besides that WARNING message?

There shouldn’t be any issue running it as admin, but it would be nice to figure out why it’s not working as a normal user.