InDesign can no longer access a file

[Armadillo77]

Twice now I've received this message:

It has prompted me to reinstall ID 2017 because I've lost time and edits. I thought maybe the latest version would have solved this, but no.

I did not move this file in any way.

Any ideas?

[AnneMarie Concepcion]

You usually see this message when you had a file open from a server and now that server is no longer available.

AM

[Armadillo77]

This is my personal desktop computer with 3 internal hdds so there is no server to go down. I closeed the file without saving and reopened the file from within ID 2018 with no problems.

[AnneMarie Concepcion]

Okay. So ... let me make sure I understand the prob. You're saying ID 2017 could not save changes to the file. It kept giving you that message. But InDesign CC 2018 could open the file and save changes, no problem. Is that right? My guess would be something corrupt in its internal tracking of where the file was located. (Assuming it can open/save other files.) Perhaps one of your internal HDs, where the file was stored, temporarily was inaccessible when it was trying to save a file, and it remembered that like an elephant.

Each version of ID has its own separate cache files and pref files. Sometimes, reinstalling ID doesn't clear out the caches and prefs that belonged to it, and that was where the corruption may have been/be.

You can delete the cache files and pref files without reinstalling; the app will just create new ones on the fly. I would try that, assuming you want to continue using ID CC 2017.

Instructions for deleting the Prefs files (don't worry, it won't delete custom keyboard shortcuts, workspaces, PDF presets, etc., just stuff you set in the Preferences panel for the most part) and the cache files are here: Troubleshooting 101: Replace, or "trash" your InDesign preferences

AM

[Armadillo77]

I am working in ID 2018. I save every major edit just to be sure I don't lose my work. At one point I paged to the front cover of my document. I selected and element on the front cover and this Warning Message appears:

I click OK. I try to save once more, but the message is persistent and keeps popping up. I close without saving. From within ID, I reopen the file no problem and continue to work. This is all done while using ID 2018. Sometimes I create an IDML file and reopen in ID 2017 just to avoid this issue.

[BobLevine]

Have you tried saving to a different internal drive.

This really looks more like a system issue than an InDesign issue.

[Scott Citron]

Can you Save As under another file name?

[Armadillo77]

I did try to save as, but it wouldn't let me. I didn't try to save to a different HDD, but Tech tools reports my HDDs are all operating perfectly.

[SanyamTalwar]

Did you face similar issue with InDesign CC2017?

[Armadillo77]

No.

[RaviKiran]

This could happen if the file at the original location has been renamed while the file is still open in InDesign.

Say, you have a file, called A.indd saved to the desktop and it is open in InDesign. You rename the file on the desktop to B.indd. InDesign will show that the file name is now B.indd but if you make some changes to the file and try to Save OR without making any changes, try to Save As..., it will throw the dialog (like the one you have shown). Please see if that is the case.

[Armadillo77]

This is true. But I didn't rename the file.

[Laubender]

Hm…
Could it be the folder name?

*FINAL

Do you see problems like that with files where the folder or file names do not have an asterisk at the beginning?

Regards,
Uwe

[harpetmoo]

Hi there, I'm having the same issue, but I renamed my file whilst it was open. How do I un rename it?

[rosam94839340]

This is happening to me too, but I renamed my file while it was open. Now it won't even let me "Save As...". It refuses to let me save the file at all. Same message/prompt as the original poster.

Any workarounds?

[Laubender]

A workaround would be to export to IDML and working on with the IDML file.

BTW: It's always a very bad idea to rename files in the file system while the file is open with an application.

Did you try to rename the document to the name it was before?

Regards,
Uwe

[Lkretschmar]

I have the same problem. This has only started happening since updating Indesign. I have tested other software and it's only Indesign that has this issue.

It happens when a file name is changed while the file is open. It also happens when the folder name (that the indesign file is in) is changed.

The only thing that has fixed it is to change the file name (or folder) back again, close the document and save, rename and then reopen. It never used to be problem to change names while files were open.

[BobLevine]

I have to ask…why would change the name of a file or folder while it was in use?

[Lkretschmar]

There's lots of reasons why this might be done. Maybe you notice the spelling is wrong, maybe you change your mind about what it should be called once you start to work on the project. It's not a big deal 'why'. It's just frustrating that this could always be done in the past but since updating you can't do it.

[rosam94839340]

Agreed. The software should account for the possibility of the user performing this action (renaming file while open).

It has never been a problem before in any of the Adobe apps In my experience. Even the new file name appears on the InDesign file tab once it has been changed.

Im on the latest Mac OS For reference.

[BobLevine]

I can't even begin to tell you how strongly I disagree with both of you. This is such a horrible idea that I can't even believe that the operating system allows it.

Windows will throw and error and tell you the file is open and can't be renamed.

Bottom line: just because you can doesn't mean you should.

[hammer0909]

I have to agree with Bob here. Renaming a file while it is open is just poor file management and a horrible idea. You're just asking for problems. That's like changing your name in the middle of a meeting and then yelling at people for referring to you by the wrong name 😉

Anyway, to Armadillo77, is One Tee Two the name of your hard drive? The external one? If so, have you tried actually saving the file to your internal drive? Does the same issue happen?

[lil-ro]

Right, so let's all blame the users instead of the OS and apps that absolutely do not account for this obvious interaction...because all users must be developers and have complete knowledge of what happens in the background when a file is renamed while open, RIGHT?

This is a major usability issue that has been unaccounted for by OS developers and possibly app developers. If it's going to cause things to break, why allow it in the first place? Let's not put the onus on the users here and instead appropriately place it on a huge usability miss by those who allowed the interaction in the first place. It's like having a button that will undoubtedly cause an error and leaving it there for all users to inevitably click. User's fault, of course! {insert eyeroll here}

Claiming it is "poor file management" is completely missing the point. Also, extremely unhelpful and condescending. The pattern of blaming the user for poor interface design decisions needs to die, honestly. Chad Chelius​ BobLevine​

[Derek Cross]

You must have a lot of confidence in your opinions (which you are entitled to) to trash the advice of some of the world’s leading experts!

[lil-ro]

I am not trashing. I am disagreeing and clearly frustrated with the assumption that "users are dumb for doing that." Which doesn't address the issue at hand at all.

Also, you don't have to be a "world's leading expert" to understand that the user is not to blame in this situation.

Pages for Mac addresses this file renaming problem quite elegantly by incorporating a renaming feature right within the app. Good, design. Imagine that! Instead of being quick to place the blame on the user, how about addressing and coming up with solutions to the real problem.

I am rightly offended, because the assumption that I am poorly managing my files = user is wrong and dumb therefore it is their problem. When instead, you could be asking questions like:

How might we prevent the user from renaming the file?

How might improve the interface to allow renaming of the file?

How might we make renaming files a quick and easy interaction?

and so on...