0: STDOUT: WARNING:After Effects warning: Could not create the file ****destination path*****.
Again, renders complete just fine. I have always accounted it to I/O collisions at the destination server. Just looking for ideas on how to avoid them. People tend to see errors and think their jobs are failing and panic. The output destination server is not overloaded and never shows signs of not being able to handle the IO.
For reference, current job is 13000 frames (png sequence), is about 50% completed and has thrown 25 of these errors. All frames so far are just fine. Reports_Job.zip (5.08 KB)
Considering the Monitor wasn’t able to load the logs from the Repository, I think you may in fact have some problems with permissions on one or more servers over there. The job reports you sent contain this:
Could not stream log from Pulse because it has not been configured in the Repository Options. Log streaming from Pulse can be disabled in the Monitor Options.
This usually means that the log was saved properly, but can’t read them (not sure if they’re missing or permissions are preventing things.
Can you check to see the permissions on those frames that are created? The process that wrote the files should be able to read them, so I’m not sure why you’re getting access denied errors.
I did have a typo in the pulse configuration in the registry which may be this error. I did verify, however, that the destination directory is wide open on security (Everyone can read/write)
Mike reminded me I’m wrong about the above. The error in those logs is usually because Pulse has failed to stream the log. If it were permissions, it would say “could not open file”. Can you try disabling log streaming? You can find it at the bottom-right of the “Monitor Options” in the “Tools”->“Options” dialog on Windows or as “Preferences” on the Mac. The checkbox is labelled as “Stream Job Logs from Pulse”.
I should mention that I did dig into the text you mentioned and I’m honestly not sure what causes it or how to prevent AE from throwing that unnecessarily. It’s possible for Deadline to eat those errors and not show them to the end user (It’s called “SuppressThisLine()”), but that’s not safe in case it would make the render fail to write out.
Can you try sorting out the log viewing and sending one job report?
I am not sure what Edwin’s thinking was on this so I will have him take a look when he has a chance, however he is out at a client’s office at the moment, so might not be until tomorrow.
I wanted to see what was throwing these errors. It does look like they’re very much fatal, but I’m not sure what’s causing them.
The only reference to “INFO:AEGP Plugin PNGIO Support: Unable to create PNGIO” suggested that it was a core plugin that was corrupted. If it’s always happening on the same machine, a re-install of AE might be in order.
As far as “can’t overwrite file”, I’d blame the file server for not telling AE the file exists properly. You could probably avoid that one by turning off multi-machine rendering and picking the task size intelligently. That way the different running instances aren’t allowed to render the same frames as others.
The errors arent killing the render. We have just over-ridden the error limits and everything comes out just fine. I havent noticed that the PNG error is coming from a certain machine so I will investigate that and see. We have seen that error before and have found it was typically from an embedded color profile in Mac generated project. One of our artists likes to embed linear color profiles that dont translate to the windows slaves. Not embedding the color profile usually ends these errors. I will look at the project and see if it has that set somewhere.
As far as multi-machine rendering, our project takes a couple of minutes to start up so we find multi-machine can save us a significant amount of time. And my artists usually dont want to take the time to do math and figure out task sizes.
I will re-render with multi-machine off and see if that eliminates the errors. If it does, i’ll just buy everyone a calculator!
