Skip to main content
D
Donny Rowles
Participant
June 11, 2018
Answered

Can't save a .fla file to my server.

  • June 11, 2018
  • 1 reply
  • 600 views

Hello. I have a NAS server - I'm on a Mac and my server is a QNAP server.

I've been (for the first time) trying to create .fla files, and it will save an initial file to the server,

but when I try to resave the file after working on it - it says "unable to save document."

Is anyone else running into this?

Thanks,

Donny

This topic has been closed for replies.
Correct answer _keyframer

That's great Clay - having configured windows shared servers for team collaboration is ideal.

For anyone else who doesn't share the same setup and maybe not working within a team environment, writing to a network drive with the same file open is simply risky. Always has been and probably always will be as long as we're on a giant rock hurdling through space at thousands of miles per hour. I stand behind my advice and still recommend working locally and then copying files to a network drive. It has worked for me for too many years. As for version control, I have my own system in place to handle that by keeping it simple: simply save the file with a new name that involves incremental numerical nomenclature.

"MyFile_01.fla"
"MyFile_02.fla"
"MyFile_03.fla"

But I'm just a simple caveman animator

@Donny Rowles can you save other file formats to your server? I would suggest contacting QNAP to ask them about configuring the server to allow you to read/write to it with a file open.

1 reply

_keyframer
Community Expert
_keyframerCommunity Expert
Community Expert
June 11, 2018

Not unusual when saving to a network drive. If you have a file open and during the session there's a network connectivity issue, it can break the connection. Alway better to save locally and then copy the files to a network drive.

Animator and content creator for Animate CC
    C
    ClayUUID
    Legend
    June 11, 2018

    _keyframer  wrote

    Alway better to save locally and then copy the files to a network drive.

    It's never better to do this, because it can very easily lead to your local and network drives falling out of sync. My team has been editing FLAs directly on a Windows Server shared drive for years, and outside of occasional problems that affect the entire network, it's always worked perfectly.

    In this case though it sounds like his file server isn't configured correctly and he has no choice but to work around its issues.

    _keyframer
    Community Expert
    _keyframerCommunity ExpertCorrect answer
    Community Expert
    June 12, 2018

    That's great Clay - having configured windows shared servers for team collaboration is ideal.

    For anyone else who doesn't share the same setup and maybe not working within a team environment, writing to a network drive with the same file open is simply risky. Always has been and probably always will be as long as we're on a giant rock hurdling through space at thousands of miles per hour. I stand behind my advice and still recommend working locally and then copying files to a network drive. It has worked for me for too many years. As for version control, I have my own system in place to handle that by keeping it simple: simply save the file with a new name that involves incremental numerical nomenclature.

    "MyFile_01.fla"
    "MyFile_02.fla"
    "MyFile_03.fla"

    But I'm just a simple caveman animator

    @Donny Rowles can you save other file formats to your server? I would suggest contacting QNAP to ask them about configuring the server to allow you to read/write to it with a file open.

    Animator and content creator for Animate CC
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices