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

These are 10.6 clients saving to 10.6 AFP Servers.

The issues doesn't happen in PS5, except for that rare occassion when someone else in the folder where the file resides but in PS5 you can ALWAYS do a save as. In PS6, that doesn't work. There is no way to save it to the server when it happens in PS6. You have to save to the desktop.

Nothing else changed in the setups on either end, client or server, except CS6 was added.

Try turning off the saving of Image Previews in the File Handling preferences.  Not a Mac user myself, but it seems to me I read that can help work around the issue.

-Noel

It's very interesting that disabling Image Previews (icons) in Preferences > File Handling works around a problem which appeared with Ps CS6.

I discovered that the icons attached to Ps CS6 files are different to the icons attached to CS5.1 files (I don't have earlier versions of Ps). The CS6 icons are counter to Apple's software development guidelines. Compliant icons may somehow avoid some incorrect networking code from being run.

See http://forums.adobe.com/thread/1008694?start=67 from the point shown in this image

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.

 

 

We are having the same issue here, though some users can save fine and others can't. There is enough hardware and software differences between us to eliminate just one OS version or hardware setup as the cause (mac 10.7 and 10.8 being used on imacs and mac pros) and enough similarities (same os and same software on the same hardware systems and some can't save and others can) to be very confusing. We are saving the files on an older Mac server (OS 10.4 on powerPC xserve) and Photoshop CS5 saved them just fine. We are all running the same font software, so I don't think that is it. I did try to turn off the image previews for a user that can't save and it didn't seem to help. Hope it can be fixed soon by someone.

We are having this same issue and I have disussed this on other similar threads. Keeps coming back to the same things to try and no solution. One thing I did find is that the problem does not occur when saving to a file server with SMB. However, when saving through SMB, periodically I was getting a message that said something like, "The saved file was modified since the last time it was saved, all changes will be lost. Are you sure you want to save". It still let me save and I was able to go on with my business. I'd say that message appeared about as often as the AFP realated program error. So it makes me wonder if they are related. Anyone have any thoughts on this?

Hi Chris,

Sorry, I misread the original post. But can you clarify what you mean by the "primary problem"? Is that in response to my post or to the original post?

Hello Chris,

Me and a collegue are facing the same issue as topic starter JenniRLeder. We are both running Photoshop CS6 on Mac OS X 10.8.2.

However, you say that the issue is fixed in OS X 10.8.2, is this correct as we are still having this problem? I was not able to find a fix or workaround.

I hope you could help me with a solution for this issue!

We are also getting the error below when saving to our NAS. Saving to our local harddrive is no problem.

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.

Everything was fine when we used Photoshop CS4. We used it with a lower OS X version though and updated both at the same time. We did not encoutered the problem with any other program so far.

Hope to hear from you.

Thank you for the information.

Even if now my user can save Photoshop CS6 on my server after I change the permission of the root network folder ".TemporaryItems", I will give your advice a try, remove this temporary folder and see what's happen.

If somethings goes wrong I could just recreate the folder

Found this link while poking around for some information relating to the .TemporaryItems folder

http://prowiki.isc.upenn.edu/wiki/MS_Office_and_Network_Volumes

Some of the suggestions here sound like they could show some promise as the related error sounds all too familiar.

After the holiday, I'll be doing some testing and will post back what I find.

Happy Thanksgiving everyone.

As fas as I know this only affects AFP connections, I haven't seen errors with SMB.

I just tried this. Removed the .Temporaryitems folder. Started up one of my clients Photoshop CS6. Opened a job on the server, made some quick changes and did a save as to another location. The folder recreated itself and inside is a folders.502 which is showing r/w permissions only for the user I just used CS6 on. I propogated permission from the top down to give r/w to the group as well. Perhaps this will make some difference??

Or am I better off locking the .Temporaryitems folder so nobody can use it?

Client is 10.6.8

Server is 10.6.8 afp

So where does it create the temp file if the .TemporaryItems folder does not exist and it can not recreate it?

Does it just revert back to CS5 behavior of saving directly over the file?

This seems like a dangerous solution. I don't want to crosspost too much so take a look at my assessment of the situation so far over here. And I am well aware that these may be different issues, but they seem to have this directory problem in common...

http://feedback.photoshop.com/photoshop_family/topics/cs6_photoshop_sa ving_issues

I've taken the information I've learned from here and done some analysis through testing. I have not however tried preventing users from recreating the .TemporaryItems folder.

We have been working with full access to .TemporaryItems for all the share's users for about a week now. This works great, no more saving issues here.

Thanks for all your input!