Photoshop CC 2014: Cannot open NEF file using

  • 1
  • Problem
  • Updated 3 years ago
  • Solved
  • (Edited)
Cannot open NEF file using Photoshop CC 2014 on Mac OSX Yosemite. I get an error message "Could not complete your request because of a disk error."

I also cannot use the Camera Raw Filter (Filter > Camera Raw Filter) in the Photoshop CC 2014 menu.
Photo of Keane

Keane

  • 3 Posts
  • 1 Reply Like
  • frustrated

Posted 4 years ago

  • 1
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14049 Posts
  • 1735 Reply Likes
Did you have any problems prior to upgrading to Yosemite?

Try creating a new Admin user account and run Photoshop from the new user account to see if the problem goes away: http://blogs.adobe.com/crawlspace/201...
Photo of Keane

Keane

  • 3 Posts
  • 1 Reply Like
No, I didn't have any of these problems prior to Yosemite.

My previous system was:

Mac OSX Snow Leopard
Photoshop CS 5
LR 3

I'll try creating a new admin user account as you suggested. Thanks!
Photo of Keane

Keane

  • 3 Posts
  • 1 Reply Like
Thanks! When I created a new admin account and re-installed Photoshop CC for that account, it worked!
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13015 Posts
  • 1333 Reply Likes
Glad that worked. Thanks for closing the loop!
Photo of JIM RAFFERTY

JIM RAFFERTY

  • 3 Posts
  • 0 Reply Likes
I have an account with ADOBE. I recently installed Photoshop Elements. I saw there was a sign in area. I tried using my ADOBE ID and received the error message, "Photoshop.com services are currently unavailable. Please try again later or check your network connections. ERROR 400." I tried to create an account from the Photoshop Elements software page. I entered another e-mail address I use and new password. When I hit create, I received the same error. Adobe has been unable to assist me. Any help would be appreciated.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 812 Reply Likes
This is a great conversation that's completely unrelated to this topic, so I created a new conversation to continue the discussion.

Please reference the new conversation here: Error 400