You have a permissions issue on your Library folder. Find the folder mentioned in the warning, use right-click Get Info on it and adjust permissions.
Having a similar problem as I try to use After Effects CC for the first time. "After Effects warning: Could not rename the file '/Users/timmyd/Library/Preferences/Adobe/After Effects/12.1/Workspaces.583.1407351854988961.xml' to 'Workspaces.xml'.
When I navigate to the 12.1 folder, I see ModifiedWorkspaces and OriginalUserWorkspaces folders but no "/Workspaces.583.1407351854988961.xml".
Then I attempted to open a project in AE CS6 (haven't use AE at all in months), I get a simliar message as the project is loading. "After Effect error: Can't overwrite file"/Users/timmyd/Library/Preferences/Adobe After Effects 11.0-x63 Prefs". ( 3 :: 3 )
When I click okay the project closes.
What Mylenium is talking about is not "your" problem, in the sense that you caused it, but a problem with the way Adobe's latest update now interacts with permissions. I never changed my preferences folder's permissions, but with the 12.0 update—and if you get this error—you have to go in and change them. I have run into this same error on the latest CS6 update as well as with a new install of CC, and only with After Effects, other creative suite/cloud apps were not affected this way.
The fix, which I discovered independently, during several hours on the phone being passed between both native and non-native English speakers, was to simply:
- Find the folder as per Mylenium's response,
- then File > Get Info (or Cmd+i)
- Scroll to the bottom of the folder info window, where it says "Sharing & Permissions"
- change the "12.0" folder's permission for everyone from "read only" to "read & write."
You may have to enter your Admin password to change your folder preferences.
Am I right that you recently upgraded Mac OS to a newer version, such as 10.9? It is the Mac OS upgrade process that is almost always responsible for this problem.
You are correct In my case, the issue occured after my upgrade to 10.9.
Yes and no.
My first encounter with the problem was with the 12.0 update for CS6 - but I had not upgraded to Mavericks yet.
Since upgrading to Mavericks.... wait... maybe I'm that's not right... yes, you might be right. Mavericks broke a lot of other stuff too. I don't know the dates, but if the CS6 12.0 update came out before Mavericks, then I experienced it pre-Mavericks. If it came out afterwards, then you're spot on. I upgraded to Mavericks on its release date.
Let me put the blame back on Apple!
Regardless, it's not a user-error issue—that was my main point. Which makes it hard to deduce, because it is all about user permissions. Easy to solve, difficult to daignose after installing an update that never explicitly addresses permission stuff that presumably no one ever messes with on their working system.