Welcome Dialog

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.


InDesign Files Not Opening From Local Server. You May Not Have Permission

New Here ,
Oct 19, 2021 Oct 19, 2021

Copy link to clipboard

Copied

Hello. We have 3 users on 3 macs all with the most recent InDesign 2021 version. We work on the same files from a local server and save back to said server. Often now we are unable to open some InDesign files and we receive the message Cannot open the document "(insert file name here)". You may not have permission or the document may be open already. 

 

The file is not open by others and permissions are set for all to be able to read and write it. If we simply rename the file is will open. Does anyone have an answer on how to correct this so we don't have to change files names and this become less cumbersome? 

 

Thank you in advance. 

Screen Shot 2021-10-19 at 4.34.37 PM.png

TOPICS
Bug, Performance

Views

67

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 19, 2021 Oct 19, 2021

Copy link to clipboard

Copied

Hi there,

 

Sorry to hear about the trouble you are facing. Could you please share a few more details like:

  • Please confirm the exact version of macOS and InDesign 2021
  • Do you recall in which earlier version of InDesign this file was opening?
  • Are you using the same naming scheme for all the files?
  • Do other files have these characters  ":" & "•" in their naming scheme? Does removing these characters help resolve the issue?

 

We are here to help. We just need more information.

 

Regards,

Anshul Saini

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Oct 19, 2021 Oct 19, 2021

Copy link to clipboard

Copied

Sounds like the lock file (.idlk extension) is not being deleted when your files are closed. This is most likely a network issue of some sort.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Oct 19, 2021 Oct 19, 2021

Copy link to clipboard

Copied

What kind of server? What OS is the server running? How do you connect (AFP / SMB)?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Oct 20, 2021 Oct 20, 2021

Copy link to clipboard

Copied

LATEST

Currently experiencing the same issue running on a Mac fileserver running 10.15.7 using AFP. Most clients accessing this server are running OSX 10.14.6

 

The following is from our IT department's research into the issue:

___________

A single file shared folder is provisioned, as users connect with individual access accounts but require access to all content on the share, permission is granted to all users at the root of the share via an access control entry (ACE). The ACE at the root of the share is:

0: group:workgroup allow list,add_file,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity,file_inherit,directory_inherit

This ACE grants the group ‘workgroup,’ which all users are a member of, read/write access to the share, and is set to inherit to all subfolders and files.

Subfolders will receive the following inherited permission:

0: group:workgroup inherited allow list,add_file,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity,file_inherit,directory_inherit

And files the following inherited permission:

0: group:workgroup inherited allow read,write,execute,append,readattr,writeattr,readextattr,writeextattr,readsecurity

Note in the above examples that the inherit bit is set on the ACE indicated by the ‘inherited’ keyword.

As further background, each file and folder has an owner (usually the user that first created the file) and a group assigned. Permissions are also set on the folder of file for the owner (user), group, and everyone else (other)—these are known as standard POSIX permissions. As an example:

-rw-r--r--@ 1 jsmith wheel 8015872 13 Oct 15:53 104345 HSC.indd
0: group:workgroup inherited allow read,write,execute,append,readattr,writeattr,readextattr,writeextattr,readsecurity

This output indicates that for the file ‘HSC.indd’ the user ‘jsmith’ is the owner and ‘wheel’ is the group assigned to the file. The owner has read/write access, the group has read only access, and everyone else has read only access. In addition to the standard permissions, we see that the inherited ACE is present granting the group ‘workgroup’ read/write access to the file.

When investigating a file that is unable to be opened by other users we see the following information:

-rwx------ 1 jjones wheel 7475200 11 Oct 09:11 104345 HSC.indd

Critically what we notice here, is the file is missing an ACE, the standard permissions indicate the file owner, in this case the user ‘jjones,’ has read/write access while the group and everyone else both have no access. As the ACE is missing which would normally grant all users (who are members of the group ‘workgroup’) read/write access to the file, only the owner of the file is able to open or modify it.

To resolve the issue for an affected file, an administrator accessing the file directly on the server adds the missing inherited ACE to the file, granting access to the group ‘workgroup’.

___________

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines