After Lion to Mountain Lion upgrade.
Cannot save or save as to Windows server. Due to "program error." Adobe Photoshop CS5. Can save as fine to local drive. Can also drag and drop in the Finder to this server.
This is Photoshop CS5 12.0.4 (current).
Once the error "could not save filename due to a program error" occurs, the file disappears from the Windows server.
I think it has something to due with the SMB connection.
All other CS5 apps (InDesign, Illustrator, etc.) "save" and "save as" fine. It is also fine performing the same procedure using Preview.
Same exact problem.
Issue happens in CS5 after Mountain Lion Upgrade 10.8
when using CS5 to save files via a SMB connection to a Windows Server the following error is displayed "could not save filename due to a program error"
however file save functionality in other programs / finder succeeds as expected with no issue.
Also have exact problem. Had it before 10.8 but now it gets worse - file deletes after this error. Other apps works fine. Local saving also works fine. Suitcase Fusion plugin for Photoshop is disabled (read somewhere here about it causing problems but not in my case). We have huge windows server disks (3 Tb).
More info to the above situation.
Windows Server 2008 r2 and 2003 r2. No changes made to any server. No changes to any permissions. All SOP until I installed OS X 10.8.
I'm aware of Adobe's official policy on saving to a networked server. Don't belive in it, but I know of it. Have never experienced any issues concerning that since about 1990. None.
Installed Photoshop CS6 on another machine to see how that went. Results were the same with one exception...with CS6, after receiving the error, the file on the server does not disappear.
Also, saving to a shared Mac continues to work great. Both CS5 and CS6. No problems.
Not much help still.
Derek Holiman wrote:
…I'm aware of Adobe's official policy on saving to a networked server. Don't belive in it, but I know of it. Have never experienced any issues concerning that since about 1990. None…
Adobe's "policy" or position is that saving across a network should work, and it does for most users.
What they're telling us is that if it's not working in our case, we're on our own, because they can't support or troubleshoot our network. In other words, if you are experiencing problems working across a network, you have two choices:
!.— Make sure your network administrator is a competent professional who can fix it; or
2.— Save locally.
Seems like I found solution for myself -
I created (it didn't exist) the /etc/nsmb.conf file, with the contents:
It's an Apple problem, not Adobe
Now we're talking! Thanks badly+.
nsmb.conf file worked for me too. Will run for a day or two to see how the performance is, but it looks good so far.
Just sayin', always figured it was on Apple, ultimately, with all their chnages with SMB. It was their OS upgrade that changed. I get it. Also don't see it as a problem, it's just progress. Was figuring it would get sorted out in the 10.8.1 release.
Thank you for reporting here the workaround, badly+.
I wish some part of the documentation at the link you provided would actually describe what that setting does, and whether there are any downsides.
Do you (or anyone) know of documentation that describes just what that setting does?
Also found this.
There's a post from Kimmo about setting Photoshops File Handling option to never save image previews. I removed the nsmb.conf file and changed this Photoshop setting. I still have Column Preview availble in Column view of OS X.
It works too. For me anyway. Photoshop CS5 will now save and save as normally to SMB server (File Server 2008 r2).
Seems better to go this route instead of dealing with it at the OS level. Just me.
Agreed - especially when the underlying OS and other Apps work as expected without OS modification, it points to a Photoshop application issue not an OS issue.
Sr. Information Systems Analyst
OS modification? It's a setting, not a modification.
And maybe that setting choice makes perfect sense for use with a Windows server - which is why I'm seeking more information on what it really means.
Noel - the SMB setting changes the way the MAC OS writes to SMB file stores - it's not optimal.
a few quick googlz for this setting and appledouble files should convince anyone this isn't a good choice.
for every file you save you will now have two forked files.
soooo if I save a file called "myfile.jpg" - then normally you have a file on the smb vol named "myfile.jpg"
once you set the smb setting discussed here you will now have instead
"._myfile.jpg" and "myfile.jpg"
Ultimately one would hope Adobe would fix it's method of saving data verses the SMB mod that throws you into the dark ages -that's just my opinion however - perhaps some may like having double files all over the server
Jonathan Hughes MCT, MCSE, MCITP, ScrumMaster
Sr. Information Systems Analyst
Adobe can't easily change it's code to avoid an OS filesystem bug (that appears to be SMB specific).
Apparently the double file version avoids the OS bug.
Apple is aware of the problem, and we are working with them on solutions to this OS bug.
I could understand that Chris if the underlying save failed but it doesn't. If there is a SMB bug why does it only effect your product? I would think if it were a SMB bug then I would see this happen in other save functions from other programs - or the OS itself, that uses the same buggy SMB - but they all work fine on my systems and only Adobe products exhibit the behavior.
The underlying save does fail, which is what causes the program error message.
If other products do error checking on the same APIs, they would see the same error.
We've already been through this with Apple, BTW. They know it's their bug.