AfterEffects 2026 with RR stop rendering randomly

[Martin Hebermehl]

Hi there,

RR v9.1.22 with submitter 9.1.21, i was testing first time ever RR with After Effects 2026.

Sending a Job with imagesequence. The slave will render some images and then will stop (but RR client says is still rendering)

This will happened randomly.

Will say, i have a composition with 1000 frames.

Sometimes client will be render only 40 Frames and then stop,

sometimes the same job will render 200 Frames and then stop.

The same is with rendering MP4-Files on a single client over RR.

Maybe a problem with sequence divide ?

Here is the Log-file if i abort the job (please note, there is an error "File couldn´t be opened for writing ((and then the path))", but RR is writing image sequences to the network folder and then randomly stops and will produce this error):

Current time:Feb 13. 10:04.47
Total processing time: 00:02.38 h:m.s
Max memory usage: 30.8GB (of 63GB installed, total system usage at same time: 38.7GB.   Feb 13. 10:03.01)
Max CPU usage: 48%   11.4 of 24 cores    (total system usage at same time: 0.0.   Feb 13. 10:02.39)
.
Max GPU usage:20%  0.2 GPUs (of 1 GPUs assigned to this thread.  Max system GPU usage at same time: 0.2/1. Feb 13. 10:02.50)
Max GPU memory usage: 7.0GB (of 31GB installed. Feb 13. 10:03.01)
TCP data: IN: 495MiB OUT: 289MiB.    Max TCP speed: IN: 8MiB/s (Feb 13. 10:02.57)   OUT: 11MiB/s (Feb 13. 10:02.57)

************************* FILESERVER RENDER INFORMATION *************************
Total render files found:   205
************************* CLIENT REPORTS DURING THIS RENDER *************************
Frame pre-processing time: 00.11 m.s
Render process finished, but there are still render processes (0 min.)
########## 1 Processes ########## (10:04.02)
PID:27100 (ppID:15916) CPU:0.0c  Mem:   11  Name:ADOBEIPCBROKER.EXE
Total      CPU:0.0c  Mem:   11
-------------------------------------------------------------------------------
************************* Status before abort (10:04.37) *************************
GPU usage: 0.0GPUs  3% (of 1 GPUs assigned to this thread. Total machine GPU usage: 0.0/1)
PID:27100 (PPID:15916) CPU:0.0 Mem:   11 Name:ADOBEIPCBROKER.EXE
Total     CPU:0.0c Mem:   11

Possible issue found in this log file (line 304): PROGRESS:  An unexpected error occurred while exporting a composition.
Possible issue found in this log file (line 306): Error Code: 790
Possible issue found in this log file (line 313): WARNING:After Effects warning: logged one error - "error: File couldn't be opened for writing: "\\de-mst-s3d01\Projekte\!Blender_AssetLibraries\!aaOcean\aaOcean_blender_water_bump\Ocean_ruhig_A\presentation\RR_Test\aaOcean_ruhig_A_RR_Test_ID2438_0195.jpg". (3  ::  0)"

Job task completed successfully.

________

[RR, Schoenberger]

Hi

 

Sequence Divide in RR cannot cause that AFX crashes.
And if you render .mp4 files, then Sequence Divide is not used at all.

Note that the message

WARNING:After Effects warning: logged one error - "error: File couldn't be opened for writing: "\\de-mst-s3d01\Projekte\!Blender_AssetLibraries\!aaOcean\aaOcean_blender_water_bump\Ocean_ruhig_A\presentation\RR_Test\aaOcean_ruhig_A_RR_Test_ID2438_0195.jpg". (3  ::  0)"

is caused by After Effects.
So RR does not have an influence on the file access.

Recommendation:
Please enable Local Render Out for the  job.
In this case the render app writes to C:\ and RR takes care of copying the files to the network.

Local Render Out has multiple advantages.
You should always keep it enabled if the render app or your scene does not have an issue with it.

 

So far I would assume that there is an issue with the fileserver or network.
Because it stops after some time.
Other render apps render fine directly to the fileserver and that folder?

Side-note:
I noticed that you are using exclamation points in the path.
While this works on Windows, Linux and Mac machines and some network fileservers have issues with it.
In your case it does not seem to cause a larger issue as some files are written.
But you should still know about it.

About your first report:

Will say: mp4 is created, but RR render it again and again and will never stop...

 

But in the other case AFX did NOT crash.
Or at least I have not seem any crash info in the log snipplet you had send.

If AFX would have crashed, then the file was not completely written.
And in this case deleting the broken mp4 is the right behaviour.
If it has not crashed, then I need a complete job debug file (or at least app log file + render log file)

Please upload via www.RoyalRender.de/upload_r.php

 

 

 

 

 

regards,
Holger Schönberger

Craftsman and Keeper of the Royal Render Flame

Please use the rrKnights Tavern
or our support system for new questions.

 

[RR, Schoenberger]

 

PS: Another advantage of local render out:  RR will write a more detailed error.
Not only that a file cannot be written, it states the reason/answer of the fileserver/OS as well.