guscebru
Level 1 (0 points)

Q: Quicktime would fail to write/export to server windows share with "Error -43: file not found" errors

Summary:

 

With the combination of Windows 7 and Quicktime 7.x, Quicktime would fail to write/export to server windows share with "Couldn't create output movie storage" and "Error -43: file not found" errors

 

Steps to Reproduce:

 

 

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.

 

Any help would be appreciated.

 

Cheers!

 

Expected Results:

 

Error -43: file not found

 

Actual Results:

The workaround seems to be to use the full path to the servers instead of the mapped mount point (ie //server/z/... instead of Z:/...

Regression:

All versions of quicktime 7 in combination with windows 7 client and more than one smb share point mapped in a letter.

 

Notes:

All software that uses quicktime movie exports showed this error.

Posted on Nov 16, 2011 3:30 AM

Close
guscebru

Q: Quicktime would fail to write/export to server windows share with "Error -43: file not found" errors

  • All replies
  • Helpful answers

  • by benohart,

    benohart benohart Feb 13, 2013 2:51 AM in response to guscebru
    Level 1 (0 points)
    Feb 13, 2013 2:51 AM in response to guscebru

    Exact same issue here!  Has this 'BUG' seriously been forgotten?

     

    There are obviously a few simple work arounds, UNC paths or rendering to the 1st mapped drive on your system however, does Apple realise how many people are pulling there hair out trying to resolve what 'appears' to be a permissions issue, but is actually a stupid bug related to the Alphabetical order of the mapped drives.

  • by Jacumba,

    Jacumba Jacumba Feb 13, 2013 4:21 AM in response to guscebru
    Level 4 (2,349 points)
    Feb 13, 2013 4:21 AM in response to guscebru

    Could it be the underscore as pointed out by jh317 in this post, your file appears to have one

     

    https://discussions.apple.com/message/12563573#12563573

  • by benohart,

    benohart benohart Feb 13, 2013 4:46 AM in response to Jacumba
    Level 1 (0 points)
    Feb 13, 2013 4:46 AM in response to Jacumba

    Not sure what file your are referencing?  Thanks for your suggestion, however, it's not relavant.

     

    It renders fine if you render to either the UNC path or the first mapped drive.

     

    i.e. If you have two mapped drives G: and H:

     

    they both point to \\fileserver\share1\folder

     

    If you render to H: it will fail, if you render to G: it works!  Same path, same user, same permissions.

     

    The only difference is H comes after G, so it fails... BUG.  If it was to do with anything else, underscores, permissions etc, it would fail on both.

  • by rod1111t,

    rod1111t rod1111t Jun 20, 2016 1:57 AM in response to benohart
    Level 1 (4 points)
    Jun 20, 2016 1:57 AM in response to benohart

    Hi there,

     

    Not sure if this helps but after a lot of research I managed to fix this problem just changing the "privilege level" of the exe file (I tried with After Effects and Davinci Resolve and in both cases it fixed the problem).

     

    On Windows 7

    Just right-click over the exe file, click "Properties", click tab "Compatibility" and turn on "Run this program as an administrator".

     

    Hope it helps,

     

    Cheers,

     

    R