Nexrender: render fail : (node:4188) UnhandledPromiseRejectionWarning: Error: spawn EBUSY

[bdb400]

I thought it was because I installed node.js, but on my other pc that I didn't install node on the same error happened.

[inlife]

A see that issue appearing more and more. Have you recently also updated windows by any chance?

[bdb400]

I updated windows after the error started happening.

[FRANK-AND-FREE]

I'm experiencing this , too, now. Suddenly the @action/encode part using ffmpeg produces this error, The video rendering with aerender works fine though and the ffmpeg.exe file was placed into the job-folder.
I can't explain either. I haven't changed anything relevant to my system, that I could recall.
Both node v12.14 LTS and v13.5 behave the same.

This is my console output:

D:\mvm-workspace\nexrender>.\nexrender-worker-win64.exe --binary="D:\Adobe CC\Adobe After Effects 2020\Support Files\aerender.exe" --workpath=".\job-workdir" --host=http://localhost:3001 --debug --reuse --multi-frames

starting nexrender-worker endpoint http://localhost:3001; using secret: no
adding default render-only-node licenses for After Effects at:

• C:\Users\Frank Bruns\Documents\ae_render_only_node.txt
• C:\Users\Frank Bruns\Documents\Adobe\ae_render_only_node.txt
  checking After Effects command line renderer patch...
  command line patch already is in place
  [QthTR7Riz_F0MdZRBEH3z] setting up job...
  [QthTR7Riz_F0MdZRBEH3z] working directory is: D:\mvm-workspace\nexrender\job-workdir\QthTR7Riz_F0MdZRBEH3z
  [QthTR7Riz_F0MdZRBEH3z] downloading assets...
  [QthTR7Riz_F0MdZRBEH3z] applying prerender actions...
  [QthTR7Riz_F0MdZRBEH3z] running script assemble...
  [QthTR7Riz_F0MdZRBEH3z] rendering job...
  [QthTR7Riz_F0MdZRBEH3z] spawning aerender process: D:\Adobe CC\Adobe After Effects 2020\Support Files\aerender.exe -project D:\mvm-workspace\nexrender\job-workdir\QthTR7Riz_F0MdZRBEH3z\test-template-480x270.aep -comp main -output D:\mvm-workspace\nexrender\job-workdir\QthTR7Riz_F0MdZRBEH3z\result.avi -s 0 -e 250 -r D:\mvm-workspace\nexrender\job-workdir\QthTR7Riz_F0MdZRBEH3z\nexrender-QthTR7Riz_F0MdZRBEH3z-script.jsx -mp -reuse
  [QthTR7Riz_F0MdZRBEH3z] rendering took ~24.078 sec.
  [QthTR7Riz_F0MdZRBEH3z] writing aerender job log to: D:\mvm-workspace\nexrender\job-workdir\aerender-QthTR7Riz_F0MdZRBEH3z.log
  [QthTR7Riz_F0MdZRBEH3z] applying postrender actions...
  [QthTR7Riz_F0MdZRBEH3z] starting action-encode action (ffmpeg)
  [QthTR7Riz_F0MdZRBEH3z] action-encode: input file D:\mvm-workspace\nexrender\job-workdir\QthTR7Riz_F0MdZRBEH3z\result.avi
  [QthTR7Riz_F0MdZRBEH3z] action-encode: output file D:\mvm-workspace\nexrender\job-workdir\QthTR7Riz_F0MdZRBEH3z\encoded.mp4
  (node:16824) UnhandledPromiseRejectionWarning: Error: spawn EBUSY
  at ChildProcess.spawn (internal/child_process.js:394:11)
  at Object.spawn (child_process.js:540:9)
  at childProcess.spawn (pkg/prelude/bootstrap.js:1413:27)
  at C:\snapshot\nexrender\packages\nexrender-worker\node_modules\@nexrender\core\node_modules\@nexrender\action-encode\index.js
  at runMicrotasks ()
  at processTicksAndRejections (internal/process/task_queues.js:93:5)
  (node:16824) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  (node:16824) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  PS D:\mvm-workspace\nexrender>

[FRANK-AND-FREE]

Ok, looks like I found the issue (at least on my machine). The Windows malware defender/anti-virus service must have blocked access to the files. You just need to exclude the nexrender working directory folder from the malware protection.
See here how to do that:
https://support.microsoft.com/en-us/help/4028485/windows-10-add-an-exclusion-to-windows-security

[bdb400]

Thank you! It worked!

[inlife]

Oh no. It seems we found the issue.
@johnrico2000 thank you!

[brassel]

Since I get the same error I would be interested in the solution for this issue.
But I am not fully sure if we would need to follow the instructions @FRANK-AND-FREE suggests or if @inlife has found some other fix for this. In the latter case I would have a different problem maybe?

Error: Error loading postrender module @nexrender/action-encode: Error: Error in action-encode module (ffmpeg) Error: spawn EBUSY

[inlife]

@brassel so far from browsing the web this kind of error seems to appear on windows for exact same reasons: system telling nodejs that It can't allow it to touch the specific file for reasons of it doing something with that file already. Like antimalware software reading into it or blocking it altogether.

That is at least the consensus that comes from my small research. Unfortunately, I'm not sure if there is anything we can do about it.