Skip to main content
M
Morriswald
Participant
September 4, 2010
Answered

Rendering error while writing to file in After effects CS 5

  • September 4, 2010
  • 11 replies
  • 101028 views

Hi

I have a problem with After Effects CS 5 on Windows 7 64 bit.

When I try to render out quicktime formats in After Effects I get an error message:

---------------------------

After Effects error: Rendering error while writing to file "E:/ . Unable to open file. (-1610153459)


--------------------------

Rendering  to other drives, like C: or 😧 works fine but as soon as I try to render to the E partiton

I get this error.... It must have something to do with permissions on that partition.

I dont want to reinstall windows,- any help would be wonderful.

This topic has been closed for replies.
Correct answer pfm_nj

I was having a similar problem where After Effects, Premiere, and Sony Vegas could not create QT files on certain drives. After a lot of forum searching I finally found a solution thanks to a tip from Rob Maybury on CreativeCow.net

It looks like QT will only write to drives with a unique name. My volumes were set up as follows (looking at Windows File Explorer)

  •     Local Disk (C:)
  •     New Volume (F:)
  •     New Volume (G:)
  •     New Volume (H:)

I could create files in C: and F: but not in G: and H:. After changing the Volume names so they all were unique:

  •     Local Disk (C:)
  •     SSD Volume (F:)
  •     Main Volume (G:)
  •     New Volume (H:)

I could now create files on any drive.

To change the Volume name, right click on the drive and select 'rename' or bring up the properties window and rename it there.

11 replies

K
ke57650003
Participant
November 25, 2016

아..진짜 감사합니다.. 정말 어디에도 안나오던데 안되던게 바꾸니까 바로 되네요!

Thanks a lot...:)

I
insanyrivas
Participant
October 5, 2016

For some reason the render would fail if I export audio as AAC but works with Uncompressed. Using After Effects CC (2015.3).

C
charleeb18446598
Participant
December 9, 2015

i had the same issue and this helped me so much thanl you!!!

S
soheil1987
Participant
September 16, 2015

After many years I found the solution and it so funny that quicktime care about volume drive.
I think it's because of different way to address files in mac and win.
Anyway thank you so much "pfm_nj's" . It work very well.

R
rayraymalibu
Participant
May 25, 2014

I am having this problem on Windows 7 64bit too. I was rendering to a sata drive that had a folder on it mapped to a network drive. I reformatted the drive and it rendered to it just fine. After that, I remapped the network drive back to the same folder location on the drive and immediately the render error came back. This time, I tried to render by picking the mapped network drive and it rendered just fine. I can't however render to the actual drive root. I'm going to move the folder that I map as a network drive to a different physical drive so my render drive will not have the network mapping associated with it. Really weird but at least I got it figured out on my machine. Good luck!

P
pfm_njCorrect answer
Participant
April 17, 2015

I was having a similar problem where After Effects, Premiere, and Sony Vegas could not create QT files on certain drives. After a lot of forum searching I finally found a solution thanks to a tip from Rob Maybury on CreativeCow.net

It looks like QT will only write to drives with a unique name. My volumes were set up as follows (looking at Windows File Explorer)

  •     Local Disk (C:)
  •     New Volume (F:)
  •     New Volume (G:)
  •     New Volume (H:)

I could create files in C: and F: but not in G: and H:. After changing the Volume names so they all were unique:

  •     Local Disk (C:)
  •     SSD Volume (F:)
  •     Main Volume (G:)
  •     New Volume (H:)

I could now create files on any drive.

To change the Volume name, right click on the drive and select 'rename' or bring up the properties window and rename it there.

    E
    Exitmult
    Participant
    June 12, 2015

    I just had this problem.  pfm_nj's solution worked like a charm.  Thanks for posting!!!!

      N
      NoMagnolia
      Inspiring
      May 13, 2014

      Am having this problem too: Windows 7 x64 SP1, rendering quicktime files only, and only when we're trying to render to a network share which is the last alphabetically in Windows's list.

      Symptoms are similar to RoFz_55: most of our files are stored on a Linux share mapped to Z:\, but we also have other shares mapped to Y:\, X:\ etc (depending on the user). I can render Quicktimes to any mapped share on the list except the last one (Z:\). This happens from C4D as well as AE, though, so it looks like a Quicktime or Windows issue :/

      A
      Anonymous
      May 9, 2013

      I thought i'd add my situation. I'm getting the same error trying to render to a network drive. I can render fine locally, and I can also render image sequences to the network drive, it's only video files (QT, WMV) that give me errors. I'd also like to add that I get the same issue when rendering from Cinema 4D. This makes me think the issue has something to do with the OS or network setup.

      L
      Lardbros
      Participant
      March 25, 2014

      We're still getting this... ONLY exporting to network drives, and ONLY with .WMV files. We haven't tried QT.

      Any files we export to our C:\ drive or anywhere locally, work fine... any network locations, the .WMV files don't play. There is no error on exporting, and it's the same from AfterEffects, and Premier.

      The file isn't getting written correctly, or the header is broken or something. The file won't play in Media Player Classic, but works in Windows Media Player on Windows 7, but not XP.

      Clearly needs to be sorted out Adobe!!

      It took a huge amount of time a few years ago to figure this issue out, but we've been waiting for it to be fixed for a loooooooong time!

      CS5 and CS6 on Windows 7 Enterprise 64-bit

      B
      balanced_rebel15B9
      Participant
      October 13, 2011

      I have same problem while export to mov but it works fine with AVI, mpg, etc.

      my machine have 2 harddisks with same name ,eg: "Harddisk D:\" and "Harddisk F:\"

      I got the -43 error when I check export video in quicktime pro,

      here's the solution:

      http://www.instant-registry-fixes.org/resolving-error-43/

      try using different name for each harddisk and it will work fine.

      R
      RoFez
      Participant
      October 13, 2011

      That may work for local harddisks. As stated previously by RoFz_55, the error happens with SHARED FOLDERS.

      T
      Toomany3-KEeYrp
      Known Participant
      January 24, 2012

      I'm a little late to jump on this thread, but I have the same problem.  Has anyone come up with a solution at this point?  It happens with DNxHD exports/renders from AE or PR.  But I can export a PSD or TIFF sequence to the exact same drive just fine.

      R
      RoFz_55
      Participant
      March 21, 2011

      Same problem here.

      After Effects 10.0.1.19

      Apple Quicktime 7.6.9 (1680.9) (tried with different versions of Quicktime, since 7.0)

      Windows 7 Professional/Ultimate 64 bits (with and with Service Pack 1)

      We're getting the same error when trying to render to Quicktime files using network shared folders as a destination:

      Unable to open file. (-1610153459)


      The funny thing: it only happens when there are at least two shared folders mapped on the workstation, and the destination folder used for the rendered movie is not the first one.

      If we have only two mapped drives, F: and G: for example, and we try to render something to F:, everything works fine and no error is showed. But, when the destination is the G: drive, rendering never works, the error is showed, but a zero-byte file is created in F: (!!). ODD! If we remap F: drive with a different letter, but a letter BEFORE G:, the problem always happens. If we remap drive F: to any letter AFTER G:, making G: the first available network drive, rendering works. Also, simply unmapping F: and leaving G: as the only connected network folder makes render to work.

      We do not have a D: drive in our Windows 7 workstations, they are all C: only.

      It is a 100% reproducible problem. We tried with three different Active Directory networks and workstations. It has all of the features of a software bug. By software i mean After Effects.

      We tried logging a support ticket with Adobe this morning, but had not heard anything from them yet regarding the situation. And to note: the Adobe guy who provided support asked me to re-format my network shared folders as a solution, which is clearly not the solution, since it happens with different file servers and different workstations. Also, it is not a NTFS security permissions problem, because rendering works fine with any mapped drive, as long as they use the first letter available after the local disks and DVD-ROM. BTW: who could be possibly that insane to ask a customer to reformat three production file servers?

      Any help would be appreciated.

      Cheers!

      O
      Octobit1970
      Participating Frequently
      March 21, 2011

      Hmm that's sounding pretty wierd. If you are running Linux on the file

      server, try tweaking your SMB. If windows, disable your anit-virus on

      the affected machines. On the shared folders, try seeing if the

      problem occurs when access is set to everyone, then i'd try to turn

      off UAC. I'm going to bet it's AntiVIrus. and you'll probably need a

      fresh boot to check.

      This does not sound like an adobe problem, it happens with other soft

      too, I think there is something in the windows unmanaged code that FU

      when folder redirects are used.

      R
      RoFz_55
      Participant
      March 21, 2011

      Weird, indeed, but not that much since it is 100% reproducible.

      No linux on the fileserver. Happens with both Windows Server 2003 and 2008 versions running on the file server. They are fully patched. It also happens when a local workstation's shared folder, such as C:\Temp or any other, is (re)mapped on this same workstation.

      Problem also happens when the Shared Folder has Everyone, Full Control permissions on its root. Also, i would like to emphasize that is not a filesystem issue with the fileserver, since render works fine when the destination folder uses the first available letter or when it is the only mapped drive on user's computer.

      Tried with and without UAC disabled, same behaviour. Tried also with workstation users in the local Administrators group.

      It's not Antivirus either. Tried with three different fileservers, two of them run Symantec Endpoint Protection, and one of them runs no antivirus at all. Tried also disabling antivirus software on both the workstation and the fileserver.

      And, finally, it does not happen with other software, only with After Effects rendering Quicktime movies. Other codecs render perfectly, without any error.

      After Effects is creating zero-byte files on the first available mapped drive, which is a clear indicator of a software bug to me, whether from After Effects or from Quicktime.

      Mylenium
      Mylenium
      Legend
      September 4, 2010

      What exactly makes up your E: drive? Have you already checked the user privileges and file ownership settings? I tend to agree with you asessment, but that realyl is something you must fix in the operating system...

      Mylenium

      M
      MorriswaldAuthor
      Participant
      September 4, 2010

      Yes I checked the user privileges, but I am not sure how to check the file ownership settings?

      Thanks for the fast answer.

      Mylenium
      Mylenium
      Legend
      September 4, 2010

      http://aeerrors.myleniumstuff.de/?page_id=986

      Mylenium

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