• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2270
  • Last Modified:

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).
0
GeertWillemarck
Asked:
GeertWillemarck
  • 2
  • 2
2 Solutions
 
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
 
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

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now