I got this error when trying to submit from the in program script in mac OSX - any clues? I’ve allowed scripts to access the network and I have the new 4.1 launcher up and pointing at the repository
sanityScriptPath = root + “/submission/AfterEffects/CustomSanityChecks.jsx”;
Im going to restart and see what happens - thanks
-update-
I submitted through the deadline launcher the same comp and it seemed to work fine - I am just having trouble with the in program script it seems -
here is the exact wording “Unable to execute script at line 234. root is undefined”
the older submission actually works but keeps submitting an older job from cs4 so no luck so far - do you have a download link to your AE CS5 submission scripts anywhere? alright I’ve hit a wall, talk later!
-tony
Hi Tony,
When you copied over the jsx submission script, did you grab it from the clientSetup or the submission folder in the repository? The one in the clientSetup folder is the correct one to use.
Cheers,
I was happy to see that that i was using the wrong script but after I set up everything and submitted again I received this warning -
It looks like there may be some permission issues with the repository folder, as something is preventing the machine from writing to that history log file. Which OS do you have the repository installed on?
windows server 2003 R2
x64 edition SP2
OSX tends to do that if there is already a folder with the same name in /Volumes. If you delete that old folder, disconnect from the repository and reconnect (using Finder), it shouldn’t add the “-1” to the end.
For the permission issues, check out these two links
software.primefocusworld.com/sof … haring.php
software.primefocusworld.com/sof … ssions.php
The first handles the permissions for the share, the second handles the security settings for the actual folder.
Hope that helps!
ok that fixed the permissions problem but its still rendering a different comp - It has to be referencing another job somewhere, here are some screenshots from my submission - the jobs names are different and also I cant seem to access any group information under the group pulldown -
I’m going to reinstall deadline for the mac and mac sure there isn’t any leftover cache -
Weird. I wonder if there are permission issues writing to this file:
/Users/Octomac2/Deadline/temp/ae_plugin_info.job
If that file can’t be overwritten, then that would explain why old job data is submitted with the job…
Cheers,
ok everything has been installed fresh - I have something new going on now -
yes looks like there are issues submitting to that file - any help on that?
I wonder if you need to set permissions on that /Users/Octomac2/Deadline/temp/ folder to allow reading/writing. I would assume by default it would be fully open because it’s the user’s home folder (that’s how it is on our macs anyways).
I should note that the Gtk message is just a warning. It’s probably being highlighted by AE because it would be the first line of the error message (even though it’s completely unrelated to the permission problem).
Cheers,
so I allowed read write access and then the folder doesn’t save the info - it goes back to a locked folder - is there a “save” function after you allow this? It keeps reverting back to being locked however after I close the window - arrrg!
So I did a test on the pc side of the AE submission script and it worked fine - I’m still having problems on the Mac side however - the script can see deadline and the groups that i have created but still does not want to write to /Users/Octomac2/Deadline/temp - I have granted full permissions for this folder as well so there shouldn’t be a problem accessing the folder - I’m thinking it that the Mac script may have to be appended? any clues would help out greatly -
tried the same script on another mac here at the shop and same exact error - can’t write to the temp directory - It has to be a mac side error - alright lemme know what comes up - thanks
We can’t reproduce this problem on our end, so that’s strange that you can produce it on 2 different Macs. If you haven’t done so already, can you try deleting the “temp” folder in /Users/Octomac2/Deadline, restarting After Effects, and submitting a new job to see if the script at least creates the “temp” folder? If it deletes the temp folder, but still can’t create the submission files, then something really strange is going on.
If that doesn’t work, then you may have to modify your submission script to hardcode a predefined temp path.
Cheers,
yes - after submitting the temp folder is created, when the temp folder is created it has read privileges only so I went ahead and modified it to read and write, but I get the same error that it can’t write to the temp folder, any ideas? Any help on modifying the script would be useful as well -
Weird…
Before modifying the file, let’s try copying over it with our current working copy. Note that the only change made between 4.1’s release and now is the wording of one of the settings in the UI. Unzip the attached file to \your\repository\submission\AfterEffects, and overwrite the existing SubmitAEToDeadline.jsx file. Then restart After Effects on your Mac and try submitting again.
If that doesn’t work, then let’s try modifying the file. Open SubmitAEToDeadline.jsx in a text editor, and find this line (should be on line 647):
var submitInfoFilename = tempFolder + "ae_submit_info.job";Earlier in the script, tempFolder is being set as “/Users/Octomac2/Deadline/temp”, which we’ve confirmed is working because the temp folder gets created properly. So for testing purposes, we need to change this line to use a hardcoded path. For example:
var submitInfoFilename = "/Users/Octomac2/ae_submit_info.job";This will cause the file to get created in the root of your user folder. Give that a try and let us know if you see a different error message. I’m expecting that if the “ae_submit_info.job” file is created successfully, you’ll still get an error about a missing “ae_plugin_info.job” file which is also created in that temp folder.
Cheers,
doesn’t seem like it can create the submit file anywhere locally - I made all of the mods and received a similar error
