After Effects 25.0.0 (Build 53). Render does NOT work with UNC paths.

[torgeirholm]

When attempting to render to a UNC path the Render Queue removes the first \ (backslash) of the path, resulting in an error message.

We mainly work on server that we access using UNC paths. Opening and working with the project works fine. Saving works fine. But when attempting to render we run into problems. We can navigate to the correct folder, and set a file name. But when pressing render we get the attached error message. 

Opening the output module reveals that the path now lacks the first \ (backslash) in the \\ UNC path. 

See screenshot.

After Effects 25.0.0 (Build 53)

Windows 11

[jenkmeister]

Thanks for the report. We will work on reproducing the issue internally and let you know what we find.

[Konrad5E05]

Rendering to a network drive does not work.

After updating to AE 25, rendering to network drive is no longer available. On AE 24 it still works.

[Konrad5E05]

I have to add something I can't believe.
Aerender writes in the log that it is looking for a network drive (unity.tvp.pl) starting from the C:

[nishu_kush]

Can you check the network path if it's correct or not? I saw another report similar to yours. In that report, Ae removed the leading "\" from the network path. Let us know if that's the case. 

Thanks,
Nishu

[Konrad5E05]

The write path is obviously wrong, which is probably why it tries to add C: at the beginning:

''aerender Error: After Effects error: Error in output for render queue item 1, output module 1.
Directory does not exist:

C:\unity.tvp.pl\TVPWORLD\GRAFIKA\RENDERY-UNITY\10_PAZDZ\15."

it should be:

"\\unity.tvp.pl\TVPWORLD\GRAFIKA\GOTOWE\10_PAZDZIERNIK\15\"

[Konrad5E05]

So only two people are rendering AE on network drive? That's a bit strange 🙂
I assure you that there are several people working here and we really need rendering to the network drive.

So we ask for an efficient repair.
When can we expect it? 🙂

Let me also suggest that the window informing about the alleged “missing directory” should state exactly what directory (path!) AE was expecting.
Just writing:
"The directory originally specified in the selected output module no longer exists."
says absolutely nothing.

And finding this obvious error in the logs required some special handling.

[jenkmeister]

We have a fix now in testing and should be in our 25.1 beta build soonish (next few days), and we are actively looking at when we can patch 25.0 to fix this issue. 

[torgeirholm]

Awesome. Thank you for the quick response! 

[Enzo23420547qoai]

Same issue. I have to render to local and then copy to our server.

I just hate Adobe each day more and more ... instead of making us gain time on creativity ...

I should stick to Davinci Resolve and Fusion. Everytime I come back to Adobe, it is back to 1996. 😞

[CAST Main Account]

We are experiencing the same problem when rendering to the network.
Workaround: Rendering the composition via Media Encoder and changing the path there seems to be working. 

[jenkmeister]

I am extremely sorry this has impacted all of you. If you need a fix today, the AE Beta 25.1x43 is currently rolling out and will be available in the next couple of hours. That has the fix in it. 

We are also working on a 25.0.1 update that will contain the fix. 

[BC_KPRC]

Thank you @CAST Main Account  Media Encoder is working 

[torgeirholm]

I downloaded the build 43 beta and tested. Can confirm that it now works fine. Thanks!

[Aman299108307puh]

same issue, they always find ways to destroy whatever is working fine

[Viktors5E3C]

Same problem here!

[Viktors5E3C]

While changing the interface colors for the new release, to make it look kinda new, Adobe dev team now finds ways to break the core functionality!

[Enzo23420547qoai]

It says a lot on the testing methods. Means that only people working locally are testing the app. So ... no professional working with teams etc ... that kind of issue should be released. and why should I use a BETA version to resolve this issue ... ? Why was it working before, and not anymore?

[jenkmeister]

The fix for this issue is now available in 25.0.1 which you can install/upgrade in Creative Cloud Desktop. Again, apologies for the issue. 

[torgeirholm]

Thanks!