Hi, when I edit the property of a job, the Job User field always reset to the first user of the list instead of going to the actual job user…
so when I change any values and apply, the job user is changed. This is true even if the user permission are set to deny the edition of the job user.
I use This verison: Deadline Version: 3.1.0.36430
Thanks
I think this happens when the job’s original user doesn’t exist in the repository, so it’s forced to select the first user that does exist. Does this appear to be the case?
I think I know why… when I submit from XSI, my user name is sylvainberger (all lowercaps), but my user in Deadline is sylvainBerger (with the uppercap B)
That might be it…
Cool. We’re going to tweak this so that if the job’s user isn’t in the repository, it is appended to the list of users in the properties dialog so that the setting isn’t changed.
Cool, but I really think you should check how Deadline handle user names with Upper Cap letters.
There is a bug in there somewhere i’m sure. I created my user name sylvainBerger, the xml file in the repository/user folder is name sylvainBerger.xml
When I submit from XSI, the username in the job file is sylvainberger
when I resumit a frame from the monitor, the username in the job file is sylvainBerger
In the monitor I always see sylvainberger (all lower).
so there are upper and lower cap conflic somewhere.
thanks
Your Deadline.ini file probably contains sylvainberger. Have you tried using the Launcher to change the user to sylvainBerger?
in the launcher change user … dialog, I see the lowercap user name (sylvainberger)
Hey Sylvain,
I was able to replicate this on our end – it looks like it’s a bug. It seems the Monitor maintains the capitalization of the username, as long as you don’t log out/switch user after it has been created. Whenever you log in as an existing user (ie, as you would have done on the slave machine), though, it converts the username to lowercase.
We’ll add it to our list of bugs, and look at fixing this for the next release.
Cheers,
perfect… now I understand why I don’t have this problem today… I relaunched everything