Skip to main content
Participant
July 6, 2012
Question

Photoshop CS6 not saving to server

  • July 6, 2012
  • 11 replies
  • 49879 views

I cannot save my .psd files to the server from photoshop, neither save or save-as. Save for web works just fine. When I try to save I get this error message:

Could not save as “X.psd” because the file is locked, you do not have necessary access permissions, or another program is using the file. Use the ‘Get Info’ command in the Finder to ensure the file is unlocked and you have permission to access the file. If the problem persists, save the document to a different file or duplicate it in the Finder.

I know for sure that I have unlocked permissions and no one else is using the file.

I'm running Adobe Design Premium for CS6 on a retina mac book pro iOS 10.7.4

This topic has been closed for replies.

11 replies

Chris Cox
Legend
July 6, 2012

Note: Photoshop does not officially support saving to servers, because there are many problems with servers and networks outside our control.

The error means that you have a permissions problem on the server, another process accessing the file on the server, or a known MacOS bug with saving files to a server (Apple is still working on it, and in CS6 we tried really hard to work around it).

Save For Web does less error checking in the area that fails on the server (we know, we just haven't gotten it updated yet).

Check the permissions on the whole server (root level downward) to make sure you have correct permissions.

Make sure no other process is accessing that folder at the time you are trying to save.

And if that doesn't solve it -- then it's probably the MacOS bug and you'll need to save locally then copy to the server.

Participating Frequently
August 1, 2012

Then why when the error occurs can you save it fine to a server using PS5??

Also, I'm wondering if a font program is somehow interferring with saving to the server as I read all the font programs currently don't work in PS6 with auto activation.

Because doing the same test in another users account using Fast Switching allows it to save to the server. That account is not using a Font program.

However, just closing all your fonts in the PS6 test doesn't allow it to save until you restart.

In any case, PS5 works fine every time.... hmmmm

Chris Cox
Legend
August 16, 2012

Chris Cox wrote:

The CS6 icons are exactly as Apple requested them.

Apple are publicly advising developers to use application and document icons which contain a pyramid of images from 16 x 16  to 1024 x 1024 pixels, the largest size being intended for Retina displays.

You have stated in another thread that the Photoshop CS6 change from previously-compliant icons of CS5 to new less-useful and non-compliant icons is because Apple requested the change in preparation for Retina.

The request is clearly illogical, therefore there seems a high probability of a communication error between Apple and Adobe, or a mistake by someone at Apple or by someone at Adobe.

Will the icons in the next Ps update be compliant with Apple's public guidelines?

https://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/IconsImages/IconsImages.html#//apple_ref/doc/uid/20000967-TP6

Extract:

Provide a set of document icons in the same set of sizes you provide for your app icon. For the recommended standard- and high-resolution sizes, see Table 5-1.

As you do with your app icons, create an .icns file for your document icons. To learn more about how to create this type of file, see “Tips for Designing Icons.”

Table 5-1  App icon resource sizes

Filename

Size of canvas (in pixels)

icon_512x512@2x

1024x1024

icon_512x512

512x512

icon_256x256@2x

512x512

icon_256x256

256x256

icon_128x128@2x

256x256

icon_128x128

128x128

icon_32x32@2x

64x64

icon_32x32

32x32

icon_16x16@2x

32x32

icon_16x16

16x16

Note: PNG with an sRGB color profile is the recommended format for app icons.


That is not what Apple told us. Again, we are doing what they requested of us.

The bugs are in MacOS 10.6 and 10.7, but somehow 10.8 made things worse.

We are investigating the problem (not just waiting for Apple to fix it).