Indesign CC file damaged and cannot be recovered

Hi experts,

In our company some of the employees used to work with the Adobe CC Suite on Mac workstations (OS: Mavericks) and with all files residing on an old Mac Server. That server crashed a few days ago.
We transferred all files to a Windows SBS 2011 server; the Mac Workstations are joined in the Windows domain.
Almost everythings works flawlessly, but there are certain issues. One of the most annoying problems happens in Indesign where newly created files cannot not be opened. There is an error message saying "Cannot open xxx.indd. The file is damaged and cannot be recovered. (Error code: 5)
The error message is not very revealing. Any clues why this happens? It happens a lot (with about 20 percent of all freshly created Indesign files).
GeertWillemarckAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

serialbandCommented:
It's likely a problem with SMB sharing problems.  There's an update today that fixes some Samba issues, maybe that will help.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jmpg_70Commented:
Until you have access through SMB, be aware that each file will "broken" and will corrupt permanently when OPENING is attempted.
0
GeertWillemarckAuthor Commented:
Hi, thanks for the replies.
I'm afraid I don't understand both of the suggested solutions entirely.

1. Update SMB. Serialband, I suppose you mean update 10.9.2. for Mavericks, an update that says it should fix some major SMB problems. We are installing this update at this moment and have no result yet. Fingers crossed, this would the fix for us.

2. Access through SMB. Jmpg_70 do you want to know if we're trying to connect with AFP? This is not the case SMB (SMB2) is the only protocol that is being used.
0
jmpg_70Commented:
2. Access through SMB. Jmpg_70 do you want to know if we're trying to connect with AFP? This is not the case SMB (SMB2) is the only protocol that is being used.

We used to access our servers with the two protocols for different reasons, but when working on natives files and fonts AFP was the only reliable manner.
0
serialbandCommented:
If you are using Mavericks, you might also want to change the connection mounts from smb:// to cifs:// if you aren't already doing so.  The smb2 protocol that apple has implemented is causing some issues.  Using cifs forces it back to smb1 and resolves a variety of issues.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Mac OS X

From novice to tech pro — start learning today.