Skip to main content
R
r1r90530564
Inspiring
September 11, 2018
Answered

not enough disk space to write file. (45 :: 32)

  • September 11, 2018
  • 5 replies
  • 1647 views

I haven't been able to find any other posts with this 45 :: 32 error - so im hoping someone at Adobe can help.

This error is coming up anytime I try to render to a specific folder (or any of it's subfolders) of a specific SMB share (happens to be a G-Rack raid).

Saving project files (or saving any files for that matter) onto that volume doesn't cause an error - the error just comes up when I try to render using the render queue.  The extra weird thing is that this error comes up consistently regardless of which Windows 10 PC that I try to render from on my network (doesn't seem to be an issue on MacOs).  I thought it might be a folder permission issue, but all the permissions for this folder and subfolders appear correct (with full read/write access to the user).

The SMB share I'm trying to render to has over 20TB of free space.

Running After Effects CC 2018 - 15.1.2

This topic has been closed for replies.
Correct answer r1r90530564

FIXED!! Turns out this ended up being a bug related to the latest firmware on our G-Rack 12 NAS RAID.  We had updated to firmware 1.0.8 originally, when these errors started happening. Then this week I  rolled back to 1.0.7 and the errors in After Effects went away. I've been in contact with G-Rack/WDC to figure out why this is happening so that they could update their firmware moving forward.

I should point out that Adobe's support was pretty bad to work with unfortunately. They had a support person remote into one of our workstations at the studio and after 2 hours of troubleshooting, simply gave up and said "we don't support rendering to network attached storage".  I called Adobe a 2nd time and had another support person remote into the system and spent another hour or so trying to troubleshoot. When he couldn't figure out what was causing the issue he said he would escalate the issue to a senior technician. I was told I'd get a call back the next day, but instead I had to follow up every day via e-mail. About a week later I called them again, they said they'd have a senior support person call me and yet again they didn't.  Luckily I was able to sort out the issue on my own, but I was not impressed with Adobe's support at all.

5 replies

R
r1r90530564AuthorCorrect answer
Inspiring
September 30, 2018

FIXED!! Turns out this ended up being a bug related to the latest firmware on our G-Rack 12 NAS RAID.  We had updated to firmware 1.0.8 originally, when these errors started happening. Then this week I  rolled back to 1.0.7 and the errors in After Effects went away. I've been in contact with G-Rack/WDC to figure out why this is happening so that they could update their firmware moving forward.

I should point out that Adobe's support was pretty bad to work with unfortunately. They had a support person remote into one of our workstations at the studio and after 2 hours of troubleshooting, simply gave up and said "we don't support rendering to network attached storage".  I called Adobe a 2nd time and had another support person remote into the system and spent another hour or so trying to troubleshoot. When he couldn't figure out what was causing the issue he said he would escalate the issue to a senior technician. I was told I'd get a call back the next day, but instead I had to follow up every day via e-mail. About a week later I called them again, they said they'd have a senior support person call me and yet again they didn't.  Luckily I was able to sort out the issue on my own, but I was not impressed with Adobe's support at all.

Warren Heaton
Community Expert
Warren HeatonCommunity Expert
Community Expert
September 30, 2018

For what it’s worth, yiu really want to be using a SAN (not a NAS).

R
r1r90530564Author
Inspiring
October 1, 2018

Thanks Warren.. we had used a SAN for a few years prior. Switched to G-Rack NAS recently and it's been great (up until this issue).

Not sure how using a SAN instead of a NAS would have made a difference here as it was very much a specific issue with a firmware of the RAID. Why do you recommend using a SAN over a NAS for After Effects work?

angie_taylor
angie_taylor
Legend
September 12, 2018

Also, is the Disk  Cache in the same drive /directory? If so, can you try emptying that and then seeing if the same issue occurs?

    R
    r1r90530564Author
    Inspiring
    September 12, 2018

    theangietaylor  wrote

    Also, is the Disk  Cache in the same drive /directory? If so, can you try emptying that and then seeing if the same issue occurs?

    Disk cache is set locally on each Windows workstation and we tried emptying all of them but that didn't help.

      Warren Heaton
      Community Expert
      Warren HeatonCommunity Expert
      Community Expert
      September 12, 2018

      If it's not a SAN, render locally and then copy the rendered file over.

      R
      r1r90530564Author
      Inspiring
      September 12, 2018

      That’s our current workaround but would really like to find a solution.

      Roland Kahlenberg
      Roland Kahlenberg
      Legend
      September 12, 2018

      Does the drive-folder-subfolder(s)-filename exceed this many characters - 187 characters

      Krung­thep­maha­nakorn­amorn­ratana­kosin­mahintar­ayutthay­amaha­dilok­phop­noppa­ratrajathani­burirom­udom­rajaniwes­mahasat­harn­amorn­phimarn­avatarn­sathit­sakkattiya­visanukamprasit

      That's Bangkok's rather elongated name, official name - city/town with the world's longest name. ;-)

      I'm now trying to see if there is an issue with long file paths/names. And I'm also going to double-check with you that you've used other apps to save to this exact same folder that AE is not able to save to - please double-confirm.

      Very Advanced After Effects Training | Adaptive & Responsive Toolkits | Intelligent Design Assets (IDAs) | MoGraph Design System DEV
        R
        Community Expert
        RobShultzCommunity Expert
        Community Expert
        September 12, 2018

        By any chance is there a lot on your recycle bin? Perhaps emptying would help.

        R
        r1r90530564Author
        Inspiring
        September 12, 2018

        Nothing in the recycling bin.

        Roland Kahlenberg
        Roland Kahlenberg
        Legend
        September 11, 2018

        Have you tried with another software, to write files of a similar size to the drive? I'm trying to see if it's a drive or an AE issue.

        Very Advanced After Effects Training | Adaptive & Responsive Toolkits | Intelligent Design Assets (IDAs) | MoGraph Design System DEV
        R
        r1r90530564Author
        Inspiring
        September 12, 2018

        Yes I’ve tried writing files of similar size using premiere, media encoder and Cinema4D and all of those work. I should also clarify that rendering to that drive outside that offending folder works. ie: if I try to render to the root folder of the drive it’s fine... it’s only that specific folder and any of its subfolders that causes the error.  Even when I copy one of those sub folders outside to the root I get the error when I try to render to that folder. So its almost like those folders are infected regardless of where they sit on the drive.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices