Skip navigation

could not save because write access was not granted (Mac OS)

Jan 3, 2012 12:49 PM

  Latest reply: thysonsacclaim, Mar 24, 2014 6:25 AM
Replies 1 2 3 4 5 6 ... 10 Previous Next
  • Currently Being Moderated
    Aug 9, 2011 5:46 PM   in reply to brunerd

    Although why would you call a temp file .afpDeleted is beyond me...

    You'll have to ask Apple about that. That's an OS and file server thing, not related to Photoshop.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2011 5:47 PM   in reply to mccolo

    So I dont understand where Photoshop is getting the error message and why it thinks it is a write issue if all the settings are open.

    Because the OS is returning an error during the save operation.

    We don't know the specifics (but Xinet seems to be the only AFP client with problems, and SMB problems appear to have a different cause).

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2011 8:21 AM   in reply to Chris Cox

    Chris Cox wrote:

     

    So I dont understand where Photoshop is getting the error message and why it thinks it is a write issue if all the settings are open.

    Because the OS is returning an error during the save operation.

    We don't know the specifics (but Xinet seems to be the only AFP client with problems, and SMB problems appear to have a different cause).

    Can you please clarfiy by what you mean that Xinet seems to be the only AFP client? I thought earlier we were reading about posts of regular OSX running afp, and also that extremeZ IP was also another one having issues.  Xinet is a server not a client, the client is the mac connecting regular ol afp. Xinet is lik Extreme Z IP but with more than file sharing, hence the reason for having it, otherwise I would just use a different sharing method.

     

    I just want to understand your thought on why you think Xinet is the only one with problems.

     

    Thnx!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2011 9:42 AM   in reply to Chris Cox

    Yeah, I'm really hoping it's the fact the Xinet AFP server is attempting to mark the file hidden and locking it at the same time the save operationattempting to complete. Our Xinet admin is changing our setting to "No special treatment" but it requires the AFP daemon to be restarted so we'll have to schedule it. I'll let you folks know what I find out.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2011 9:49 AM   in reply to brunerd

    brunerd,

     

    That would be WAY COOL! I noticed the restart prompt as well, so I waited and havent scheduled it yet since I am going on vacation. I will be anxiously awaiting your results.

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2011 11:32 AM   in reply to mccolo

    Dang -- we changed it... then we waited... first day OK, next day same old .afpDeleted nonsense...

     

    I can only hope by some miracle Photoshop CS5.5 behaves better, we've been waiting for Extensis to get their UTS/UTC 3 out with CS 5.5 plugins, so next is to upgrade the font server, then all the clients to CS 5.5

     

    Will keep you posted...

     

    And so help me Holger, I hope your Out of Office message is turned off!

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 10, 2011 7:57 AM   in reply to brunerd

    I have been having this and another issue with Photoshop regarding Lucida Grande not updating and not allowing me to edit files. When I contacted Apple to clear up my font issue, this problem went away for me. I'm not sure if it's related, and it's not something that makes a lot of sense to me, but I wanted to put it out there, to see if it helps. I understand how this issue can cause major problems.

     

    My font issue was with how Lucida Grande's preview is generated. Somehow in my updating process to CS5.5 and Lion OS, the resources Lucida uses were damaged. When I opened a file, it first asked me to update the file. When that failed, I would be forced to open the file and not udate the fonts. When I did that, ade any change to the file and attempted to save, the file would vanish from my server and I would have to save it again. The fix below is what I used to solve my font issue, and now I have no saving issues on my server at all. Again, I really can't explain why.

     

    First thing... quit all open applications.

     

    1. Open Font Book and navigate to Stone Sans. (You may have to or three versions)

    2. Right-Click and "Show in Finder" - This will take you to your System/Library/Fonts folder.

    3. Copy all Stone Sans font files to your desktop as a backup.

    4. In Font Book, right-click on all Stone Sans fonts and 'Remove Fonts'.

    5. Open Photoshop and check to see if Lucida Grande is available for use. This re-builds some font cache or font resource that is used by Photoshop. (No one could tell me this for sure, so I'm guessing here.)

    6. Close Photoshop and copy Stone Sans back into the System/Library/Fonts folder and relaunch Photoshop.

     

    Now try to open a file from the server and make a small change like turning on or off a layer. Then try to save and see if you can save the file as normal, or if you get the same error.

     

    The guy I spoke with at Apple said that he believes Stone Sans is a resource for Lucida Grande, and if the connection to that resource was corrupt, it could cause my font problem, but that he has never heard of it before. I wonder if the saving issue is related because all the files I have issues saving has Lucida Grande in them.

     

    Anyway, if any of you are still baffled and frustrated, try this fix. It doesn't take long and doesn't hurt anything, so it may be worth it to try.

     

    This worked for me.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2011 8:08 AM   in reply to sean-gloss

    Just to add my voice to those of others. I am an apple ACN in the UK and I support just over 40 companies. This error has cropped up in two separate sites. One with a user running CS5 on a 10.6.x machine working off SMB (I say 10.6.x as this problem persisted for this user from 10.6.4 up through 10.6.8 and persists now as an intermittent fault in CS5). I now also have a second user afflicted running CS5.5 on a 10.7 client accessing a 10.6.8 based AFP share. Although I didn't see it in person, the CS5.5 user has also reported this as an issue with local files as well as network based files. Both users have so far nullified the issue by reverting to CS3 or 4 where there's no problem.

     

    I have to agree with others, the common thread is Photoshop CS5. This happens with nothing else. No other CS5 app. No other version of CS, no other app outside of CS. this only happens in Photoshop CS5. As much as Chris tries to bat this away - theres an old saying, that "if it looks like a horse, smells like a horse and sounds like a horse.... chances are, its a horse". I expect to see this issue more often as companies buy new machines and end up buying CS5 for those new machines. It would be nice to see this resolved before CS 6.

     

    Chris you have been doing a great job batting this away and defending the company line. I'd expect nothing else. but at the end of the day this feels like ford making a car with dreadful handling that shakes all over the place and blaming the road.  if CS5 is meant to play nice on OS X 10.x, y or z then it's adobe's job to make it roadworthy, and right now it feels distinctly rickety.

     

    ATB to all

    John

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 15, 2011 12:58 PM   in reply to jrtbloke-2011

    Just wanted to add, in case nobody has mentioned it, that one way I've been able to easily reproduce the issue is by trying to save a large file and cancelling it mid-save by hitting the Escape key. The file on the server disappears at that point and a "save as" must be done to save the file you still have open in memory back to it's original location again.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 17, 2011 12:55 PM   in reply to Chris Cox

    We have a newer iMac running Lion working off a smb share and have been getting the "could not save because write access was not granted" and i can repeat the error every time by turning on or off the "preview" in the finder window (or coverflow view also), with preview on we get the error and can only save as a new name or to the local drive, when we turn preview off it saves fine back in the original directory. On this machine CS3 behaves the same, only the error is "file is in use or open...." again turning off the preview fixes that also. The other macs at work are all using admitmac smb, and are all running leopard or even tiger (cs3) and even with preview on do not have this issue. Newer OS with new finder seem to be our issue so the operator has been told to not use preview but they can use bridge. Maybe this info will help someone else.

    Gordon

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 29, 2011 2:21 PM   in reply to Chris Cox

    The issue is saving a file while the OS, Finder or something ELSE may have the file locked.

    It has nothing to do with Photoshop opening the file.

    Photoshop already does warn you if the file is in use by another application when saving -- but the OS bug appears to have issues (maybe timing related) with locks on the file.

     

    We have done our part, and determined that the responsibility in this case is with Apple.

    We cannot fix their OS bugs.

     

    Chris, I agree that this is not directly a Photoshop issue. I've always seen this as a Lightroom bug. Here's are the only circumstances where I have encountered this error:

         Select file (located on server) in Lightroom

         Cmd-E to Open existing PSD from Lightroom, choosing to edit original

         Make changes in Photoshop

         Try to save, get error, use Save As to save file

     

    However, I do NOT get the error in any of the following situations:

         Open a RAW file from Lightroom

         Open a PSD and choose to edit a copy

         Open existing PSD, then quit Lightroom before saving the file in Photoshop

         Batch export RAW files, choosing to run a post-export Photoshop action

              This creates a PSD for every RAW file, imports it into Lightroom, then opens it in Photoshop

         Cmd-R in Lightroom to reveal the PSD and open it in the Finder (without quitting LIghtroom)

               *** This is my current workaround ***

         Open the PSD in any method OTHER THAN from Lightoom, whether or not Lightroom is running.

     

    I'm running Lightroom 3, Photoshop CS5, and Mac OS Lion. Files are on a server running Lion server. I do not use the zip utility mentioned earlier in this thread. Having another user browsing the same directory the file is in does not seem to have any effect. I had this same issue when all machines were running Snow Leopard, Lightroom 2, and Photoshop CS4, with the exact same results as above.

     

    I'm not sure I understand why Photoshop pukes on the file if it's saving to a temp file and then swapping out the old file with the newer temp. The error happens far too quickly for Photoshop to have even attempted to save to a temp file before deleting the original.

     

    Nate

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 1, 2011 1:05 PM   in reply to sean-gloss

    I have one user with this issue as well.  Only  happens in Photoshop and not all the time.  Seems to only happen with PSD files.  My other 12 users, to this point, don't receive the error. CS 5, Lion, saving to a Windows 2008 R2 Server running the latest version of ExtremeZ-IP.  This user was having the problem with a previous Mac, which had 10.6 on it, so as a test I moved him to the newer machine he currently uses and same problem pops up.  It isn't all the time but does happen every day at least once when trying to save his work. 

     

    Going through this forum I don't hold out much hope this will get fixed because it seems Chris has taken on the typical, in my experience at least, Adobe stance of it is never our products that are causing the problem.  In all reality it is probably Photoshop and something to do with OS X but god forbid two companies work together to solve an issue.   Meanwhile we the users deal with the pain. 

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 1, 2011 8:01 PM   in reply to Tim-Dube

    >>  the typical, in my experience at least, Adobe stance of it is never our products that are causing the problem.

    That is a common answer because that is most often the case after we fix the major bugs in our products.  (ie: after fixing our bugs, what's left are other people's bugs that we can't work around)  Whenever a problem is ours, we admit it and try to get it fixed as soon as possible.  And as noted above, we've been working with Apple on this, and other companies.

     

    Anyway, we are continuing to work with Apple to figure this out, and adding more safety code on our side to prevent file loss when unexpected file system errors occur.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 1, 2011 8:27 PM   in reply to Chris Cox

    Chris Cox wrote:

     

    Anyway, we are continuing to work with Apple to figure this out, and adding more safety code on our side to prevent file loss when unexpected file system errors occur.

     

    Let me ammend my comment to say that if this is an Apple bug that can't be worked around, Photoshop/Lightroom is the only software combination in my experience that has hit it. Is there a bug report with Apple that I could follow?

     

    Nate

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 1, 2011 9:45 PM   in reply to Nate Berggren

    No, customers don't have visibility into Apple's bug system.

     

    Photoshop hits it because we check for all kinds of errors, most other applications just ignore the errors.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2011 5:47 PM   in reply to sean-gloss

    After a lot of frustration here today, we were able to resolve this issue by turning off "Show Icon Preview" in the Finder, using OSX 10.7.2.

     

    It looks like, for our situation, this error was the result of a conflict between Photoshop and the Finder. We "fixed" this conflict by turning off the Finder "Show View Options":

     

      Show Icon Preview = OFF

     

    If that is turned off, the problem goes away. Optionally, you can turn off Photoshop's preference to save icon previews. That also "fixed" it. But since Show Icon Preview is a network hog, and our server software (Xinet) already makes icon previews, we chose to turn that off.

     

    Hope that helps a few folks,

    James

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2011 5:54 PM   in reply to jpword

    jpword wrote:

     

    …since Show Icon Preview is a network hog, and our server software (Xinet)…

     

     

    You're working across a network? 

     

     

     

    This is the boilerplate text often used in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):

    If you are opening files over a network or saving them to a network server, please cease and desist immediately in the event you are currently experiencing problems with one or more files. Working across a network is not supported.


    See: 

    http://kb2.adobe.com/cps/406/kb406793.html

      Copy the CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.
     
         Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work.   It should.

        Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.

      If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.

    When problems arise, a lot of valuable work can be lost.

     

    ____________

    Wo Tai Lao Le

    我太老了        No connection to Adobe, just another end user.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2011 6:16 PM   in reply to Tai Lao

    Hi,

     

    Yep, over a network.

     

    Works fine with "Show Icon Preview" turned off, which is part of Adobe's "normally, it does work" message... but I completly agree with you, if you have sensitive image files, and no backup, you should certainly not work over the network... but many people do and I wanted to share why Photoshop was denying the write with the, "write access was not granted" message. It's because our server respects locks and the Finder had the resource fork locked trying to make its Icon Preview.

     

    Photoshop should detect when that's the case, and avoid the original file from being deleted. The error is fine, and justified. The delete is not.

     

    Thanks,

    James

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2011 9:46 PM   in reply to jpword

    Thanks James!

     

    I will give this a try tomorrow. We ate also on Xinet with a 10gig backbone

    working off the network with 2 gig aggregated to the desktops.

     

    Sent from my iPhone

     

    Mark Campbell

    Production Technology Director

    The Integer Group

    303.619.1166

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2011 11:59 PM   in reply to jpword

    >>> Photoshop should detect when that's the case, and avoid the original file from being deleted. The error is fine, and justified. The delete is not.

     

    We're still working with Apple to determine how that happens, and make sure it gets fixed or we find a way to avoid the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 14, 2011 9:30 AM   in reply to Chris Cox

    Hi Chris et al,

     

    I am very glad to hear that Adobe are now working on this with Apple. I have to go to a meeting with our users on Friday to discuss with them what progress has been made on fixing this, could you answer a few questions so I am able to give them an update?

     

    - How long have Adobe been working with Apple on this?

     

    - What progress has been made so far?

     

    - Are there any recommended workarounds in the short-term?

     

    - Is there an estimated time to resolve?

     

    - What priority is being given to the issue at both companies?

     

    Also if it helps towards a resolution at all, we have observed that this problem only occurs on certain sharepoints. We have a number of shares that are all hosted on the same Xsan volume, but the error only occurs with files stored on a few of these shares; users who are accessing the other shares never see the problem. I am more than happy to provide any diags that we can to Adobe/Apple regarding these shares.

     

    Many thanks

    Dan

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 14, 2011 2:42 PM   in reply to The Penguin of Doom

    We've beenn working with Apple on related issues for years.

    We recently identified a particular defect in the Apple SMB implementation that can cause a problem like this.  We are attempting to create workarounds in our code (and better error detection), but the core problem is in the MacOS code.

    And we never know Apple's priorities.

     

    The only known user workaround is to save on the local disk, then copy to the server.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 24, 2012 2:13 PM   in reply to sean-gloss

    So this issues of 'afpDeletedxxxxxxxxxxx' and 'Write access was not granted' in Photoshop are now happening in my environment.  The users (about 20) have worked off of a Mac Server for 10+ years using Quark, InDesgin, Photoshop, you name it and have never had any issues until the past month or so.  While I understand Adobe's stance on not working off of a server, I have been put in a tough as the system that worked for 10 years suddenly is not longer working consistently.  Try telling someone they have to change the way they have been working for 10 years with no problems until now?  No one is going to like that. 

     

    Here is a little info about the setup and troublehsooting I have tried

     

    • 2 Mac Pro Servers running 10.6.8 - 1 is an OD master, the other is a OD replica which exists only in case of a disaster.  The OD Master replicates its data 4 times a day to the OD replica using Carbon Copy Cloner.  (The replication process has been in place and untouched for 3 years now)  (I know when CCC runs and users have reported the saving issue at times that match up with CCC and times that do not.  I even disabled the replication for a day and it still happened)

    • The deisgners are all on Mac Pros purchased within the last three years and all are running 10.6.8 and CS5.5.  As I said the connect via the built in AFP using their Open Directory Credentials using the Open Directory Authentication Attribute.  All the designers have an internal drive dedicated to Time Machine.  I have disabled Time Machine and the issue still happens. 

    • The designers are very careful about accessing each others files.  Are the designer's project folders are color coded to alert other designers to stay out.  Other designer's browsing the directory is not the cause.

    • There has been no major change in software or hardware in the last 6 months so I cannot attribute that to the file saving issue.

     

    When stuff was changed

    CS5.5 and 10.6.8 Deployed in June 2011

    OD Master Replaced (Xserve -> Mac Pro) in March 2011

    3 New Mac Pros deployed in September 2011

     

    If anyone could shed any light on this issue I cannot tell you how much I would appreciate it.  I can upload logs if requested.  The next step I am likely to take is to bind all the machines to the OD master and implement Kerberos, futile?  Or a good idea?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 24, 2012 2:35 PM   in reply to Dovahkiin27

    There's only one workaround that I have found, and it's a pain. You have to go into Show View Options (Command J) and turn off the preview column.

     

    It's a workaround that I found here with a full explaination of the issue: http://support.grouplogic.com/?p=1664

     

    It works for me, but it's a pain because I have to hit the space bar to view previews, rather than having the finder present one to me. Slower, but safer.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 4:36 AM   in reply to garymason

    Hi Gary,

     

    As an addendum to your mail, we have run some reasonably extensive testing turning off the Finder preview options, but always seem to start seeing the problem again eventually. I would also add that these previews are written to the resource fork (._MyFile.jpg in the same directory for a file named MyFile.jpg) rather than the actual file and should not therefore hold any write lock over the original file.

     

    However, in the last week or so, we seem to be seeing some success (fingers and toes crossed) with turning off the three preview options in Photoshop's own preferences as per the attached image. We've only been running with these off for a short time so no guarantees, but we can only hope.

     

    Adobe Take Note: This would seem to indicate that your software may be holding a write lock on the file in order to write the preview. Please could you examine this section of your code to see if a resolution can be found here?

     

    Dan

     

    Picture 2-10.png

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 4:38 AM   in reply to The Penguin of Doom

    Just as a follow on to my previous post and Chris Cox's previous post, I have to say that I am horrified by the lack of helpfulness from Adobe on these issues. The people posting here are not single box copy end users, they are TLP and CLP licensees. My company spend in the region of £20,000 per year with Adobe. I would expect a somewhat less trite response.

     

    I've heard the responses before. I know Adobe don't support working directly off a server. However, that is how large organisations work, it's time you did support it, even if only on a basic level. I'm not asking for support on working over GPRS from a Fuse mounted LTO file system, I'm asking for support on a Mac desktop working from an AFP share hosted by an Xserve on the same LAN and subnet. It's very easy.

     

    I've heard the 'we do more checks' response. It doesn't wash. If that's the case, why don't we see files disappearing with any of the other applications we use, warning or no?

     

    There are some very smart people in this forum, all of whom are willing to help with resolving this. Why do you refuse to engage with us?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 6:10 AM   in reply to The Penguin of Doom

    He probably doesn't want to engage with a penguin of doom....

     

    Anyways, I share your concerns, about Mr. Cox's responses however I would like to add that very few of the posts are actually bad mouthing the Adobe software and that (guessing here) 90% of the posters in this forum are coming here to start conversations with others in the same field to work together to find a solution.  I don't think anyone comes here to get a response from an 'Adobe Employee'.

     

    With that being said, I have also implemented your idea about disabling Photoshop's desire to save a preview so we will see how this goes.  Ther user I disabled this for informed me he received the error 15-20 times yesterday.  He went from never to 15/day.  Needless to say this has not been a fun week.  I did also notice that spotlight searching was enabled on my share in Server Admin so I disabled it, did not help at all.

     

    If The Penguin of Dooms idea fails here are my next attempts

    Implement NFS for the problem user

    Bind his computer to the server and implement Kerberos (long over due anyhow)

     

    Would anyone have any other suggestions?  Thanks for all the help thus far

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 7:53 AM   in reply to Dovahkiin27

    He probably doesn't want to engage with a penguin of doom....

    Mwah haw haw

     

    ,o)

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 8:36 AM   in reply to Dovahkiin27

    Dovahkiin27 wrote:

     

    If The Penguin of Dooms idea fails here are my next attempts

    Implement NFS for the problem user

    Bind his computer to the server and implement Kerberos (long over due anyhow)

     

    We are bound to AD with Kerberos, running Xinet on a RedHat Linux server with a 10gig backbone and 2 gig aggreagated from the clients and while we dont have the issue frequent, we still get it on occasion.  We work on very large files (Bus wraps, Baseball Banners, etc.)  We have turned off the preview for columns, icons, and will give the Photoshop preference of preview generation a try as well next time it happens. Luckily we have told our users about the workaround of duplicating the file in Photoshop and saving it.

     

    The ridiculous part of all of this is afp has been around how long???? And ironically a new version of Photoshop just uncovered an error that has been there supposedly "forever" and previously we just didnt know about it because we didnt have the super special error reporting from Adobe??? I dont think so....Why did our files save before without crashing when we didnt get notified of an error (even if whatever error Adobe is reporting on was happening)???  Isnt that the real issue here? Adobe claims it is reporting on an "error" that is happening on Apple, but perhaps the act of reporting on it is what is causing the issue?  Maybe it is not an error at all, just a change of properties of the file and the reporting of that is what is causing the crash?  Has Adobe thought of this???  This is the kind of feedback I am sure a lot of us would like to hear from Adobe what their answers are and what they have investigated, or are investigating to ensure it is not an Adobe issue, but all we hear from them is "Its complicated.....we report on a lot of our vendors errors"  While that is all good, what are we supposed to do once we have the report?

     

    At any rate, I sure hope they dont change the way files get saved for their other products in the CS suite to "protect us" with error reporting.

     

    BTW we too are a super user of Adobe products and spend hundreds of thousands of dollars with them annually within our Agency Network. So I understand the frustration.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 9:50 AM   in reply to The Penguin of Doom

    Just as a follow on to my previous post and Chris Cox's previous post, I have to say that I am horrified by the lack of helpfulness from Adobe on these issues.

     

    The annoying thing was the time it took to get the point across that this wasn't an issue with 3rd party server software but with vanilla Mac to Mac OS connections.

     

    This issue is still causing us a lot of problems and due to the large number of images that we handle for ad campaigns it would be a nightmate to deal with the data duplication and the risk that the server version is not the latest version of the images.

     

    I don't know if this is related but we also get a lot of file reading errors in Photoshop if the file metadata is edited.

     

    If you save a PSD and then close it on one Mac and then edit the metadata (using exiftool) from another Mac, the original Mac is then unable to open the file at all -- or can open the file but it's unusable because the image data is disrupted. We have to open and re-save the data from a different Mac before the original machine can re-open the file. [Note that the image was closed before the metadata edit was carried out and sufficient time was left to ensure that that exiftool had completed the edit].

     

    Wonder if this is also the result of Photoshop's super special file handling routines? Certainly never seen this happen with any other software.

     

    --

    Martin

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 10:04 AM   in reply to The Penguin of Doom

    >> Adobe Take Note: This would seem to indicate that your software may be holding a write lock on the file in order to write the preview. Please could you examine this section of your code to see if a resolution can be found here?

     

    That's one of the areas we looked at, and that is one of the areas where we found a problem with MacOS file handling on some network protocols.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 10:09 AM   in reply to The Penguin of Doom

    >>> I've heard the 'we do more checks' response. It doesn't wash. If that's the case, why don't we see files disappearing with any of the other applications we use, warning or no?

     

    I don't know why you don't see it.  We can reproduce such problems fairly often in other apps (and it's annoying as @$%^@#%).

     

     

    We've been engaging with customers and OS vendors to solve the issue.

    But the problem isn't simple, and the majority of what we've found it outside of our control -- but we're still investigating workarounds and improved error checking to detect OS failures.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 10:11 AM   in reply to mccolo

    >> Why did our files save before without crashing

     

    We're not discussing crashes at all here, just files that fail to save correctly.

     

     

    >> but perhaps the act of reporting on it is what is causing the issue?

     

    Nope.  The error reporting happens after the OS has returned an error.

     

     

    >> At any rate, I sure hope they dont change the way files get saved for their other products in the CS suite to "protect us" with error reporting.

     

    So you prefer to quietly lose files on the server to actually being informed of the error coming from the OS?  Kind of a "head in the sand" approach to file management?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 10:15 AM   in reply to Martin Orpen

    >> The annoying thing was the time it took to get the point across that this wasn't an issue with 3rd party server software but with vanilla Mac to Mac OS connections.

     

    We've been working on the problem for a long time.  But the most common problem used to be with third party servers.

    MacOS changes have made it occur more often on any server using AFP or SMB.

     

     

    >> I don't know if this is related but we also get a lot of file reading errors in Photoshop if the file metadata is edited.

     

    Not related.  But if you're seeing image corruption like that, then you're looking at a bug in EXIFTool or your network server.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 10:29 AM   in reply to Chris Cox

    >>> I don't know if this is related but we also get a lot of file reading errors in Photoshop if the file metadata is edited.

     

    >> Not related.  But if you're seeing image corruption like that, then you're looking at a bug in EXIFTool or your network server.

     

    If that were the case then why is it *only* the Mac that saved the original file that is unable to re-open the image?

     

    If exiftool were hosing the data then none of the server clients would be able to open the file.

     

    --

    Martin

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 11:04 AM   in reply to Chris Cox

    Losing a file because of a .afpdeleted file error to me is a crash. As far as a head in the sand approach, my point was whatever Adobe did to change the way files get saved, seemed to complicate and make the issue worse. Besides, what the &%$#@#$ am I going to do with a report? Re-write my OS or application? Come on, put yourself in our shoes, If you give me a report of an error, give me some resources what to do with that and some workarounds at least. If your going to be proactive and provide reports of other peoples errors, then you must think it is important enough to give some options of what to do with them even if it means making work arounds in your own application to get around the error.  If your taking the side that it is "their" problem, the minute you report on it, you are taking responsibility for it from a users perspective. Just think of all the people that dont read this forum that see Photoshop giving them an error when they save.  Have you heard anyone say they got an Apple error that Photoshop told me about? No..........Bottom line is we are the clients here, and the more we hear how Adobe changed something and now it doesnt work, the more we (the purchasers of your software) will continue to give Adobe the bad press that they broke it.  Especially when we post on a forum to ask these questions and they get so defensive.

     

    Chris Cox wrote:

     

    >> Why did our files save before without crashing

     

    We're not discussing crashes at all here, just files that fail to save correctly.

     

     

    >> but perhaps the act of reporting on it is what is causing the issue?

     

    Nope.  The error reporting happens after the OS has returned an error.

     

     

    >> At any rate, I sure hope they dont change the way files get saved for their other products in the CS suite to "protect us" with error reporting.

     

    So you prefer to quietly lose files on the server to actually being informed of the error coming from the OS?  Kind of a "head in the sand" approach to file management?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 3:29 PM   in reply to Martin Orpen

    >> If that were the case then why is it *only* the Mac that saved the original file that is unable to re-open the image?

     

    I don't know -- I don't have your systems to debug.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 3:33 PM   in reply to mccolo

    >> Losing a file because of a .afpdeleted file error to me is a crash.

     

    No, a crash is a very specific thing.  Losing a file because of a file system error is not even remotely a crash.

     

     

    >> whatever Adobe did to change the way files get saved,


    All we did was check for more errors.

    The OS may change behavior (because it changes from Carbon to Cocoa, and sometimes from OS version to version), but Photoshop really didn't.

    We try to tell you about the errors so you know that something went wrong.  If you don't know about the error, you don't know that your file was lost. If you know about the error, you have a chance to resave the file.

     

    I'm sorry we don't have a magic wand to wave and solve your problems -- but it is still far better that you know about the OS bug than just losing files at random.

    And we are continuing to work with Apple, and working on our code (working around OS bugs) to prevent lost files.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 27, 2012 3:41 PM   in reply to Chris Cox

    And we are continuing to work with Apple, and working on our code (working around OS bugs) to prevent lost files.

    Thats good to hear. Is there any kind of ETA on this? What kind of progress can we expect to see in CS6 or CS5.75?

     
    |
    Mark as:
1 2 3 4 5 6 ... 10 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (4)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points