"Document in use" icons not going away thus causing corruption 1

[jbrowndailysun]

Hello,

I work for a newspaper. Today, during our major deadline push, we discovered that InDesign (or maybe our LaCie disk server/hard drive) had some major problems.

We all use a macintosh platform, and there are several computers using this LaCie disk. We use it to hold all of our files for the newspaper, as the disk is HUGE. It's not anywhere near full, so we have doubts that it is our disk that is the problem.

What's happening is, whenever someone opens an InDesign file (today), we all will see a "~openfilename" kind of icon that shows us that the page that someone is working on is open. InDesign (today) has crashed on us while working on our pages, and when it closes, those "~openfilename" files don't close. So, in essence, our files get corrupted (we can't open them, or when we can, they lock up and won't allow us to save). Also, when we can open them after a crash, it keeps making new "~openfilename" files. So . . . it's also filling up our LaCie disk with rubbish.

Does anyone have any idea what the source of this glitch might be? Do you think it's our server, or do you think it's InDesign?

Thanks.

 

[jbrowndailysun]

BTW, I did happen to get the exact name of an example (one of many) of the open document file I was talking about.

~7-19 Memory Hall a~ey-pa_.idlk

This is what opens along with the files we are using while on the LaCie disk (or desktop, wherever the file is opened). For some reason, these icons (have a padlock icon with them) don't go away now when we close a document, and they used to. I have a feeling more and more that this is a LaCie disk problem after all . . .

Anybody know anything about that?

 

[jbrowndailysun]

I think we figured it out.

I dug around on the Adobe site for this one, and we basically realized that we need a server . . . badly. It was most likely the fact that we were all updating items that were on this external harddrive, and it just couldn't take it. So . . . we're good to go.

None of our files were destroyed as we were able to copy files locally and get the job done. The key is to know who the administrator of the hard drive is, as they have the ability to delete those ugly .idlk files (but be careful that nobody has the file open).

Our temporary solution (final solution being that we'll get a real server) is to save these files to the computer of the guy who has the LaCie. At least then, maybe there won't be major crash issues. It's a more direct connection as well.

Thanks.

 

[signal49]

Thanks for keeping us up to date on that! Glad you figured it out