Photoshop CC 2018 19.1: Bridge > Photoshop Image Processor Intermittently fails to save JPEG on server

  • 1
  • Problem
  • Updated 9 months ago
  • (Edited)
We are a team of four graphic designers all updated on the latest versions of Photoshop and Bridge CC 2018. Since we did the update, when using the Tools/image processor from Bridge to Photoshop, we keep randomly getting this Script alert:

I am unable to create a file in this folder. Please check your access right to this location.

We all save locally on our server, which is located in our building and not a cloud based service. It is the same server we've been using for the past 4 years. Some PSD get saved into JPEGs no problem, then one will fail with the script error and the other will be just fine. We regularly process 40+ PSDs in one go, and it used to be a problem free process. Now we do the files one by one and it takes forever and even then, it fails.

We use Windows 7 Professional on Dell computers, each of them equipped with Xeon CPUs, 16 to 32GB of RAM, SSDs as Scratch disks...
Photo of Janie Trudel

Janie Trudel

  • 6 Posts
  • 3 Reply Likes

Posted 9 months ago

  • 1
Photo of Hannah Nicollet

Hannah Nicollet, Official Rep

  • 689 Posts
  • 288 Reply Likes
Hi Janie,

Thanks for letting us know. How many of you in your office are seeing it? Next time it happens would you please:

1. recount all the steps you took before it happened
2. make a screenshot when you encounter the error

Thank you, 
Hannah
(Edited)
Photo of Janie Trudel

Janie Trudel

  • 6 Posts
  • 3 Reply Likes
The four of us have this issue.

What we do is we finish our work in Photoshop, close our current file, go to Bridge, select all the files in the project, then run an Image Processor on all of them at once. We've always been doing this in the past and it was working fine until now. All settings in the Image Processors are left at default.  It saves the newly created JPEG into a JPEG folder it creates.

Here's a screenshot of the error message.
Photo of Hannah Nicollet

Hannah Nicollet, Official Rep

  • 689 Posts
  • 288 Reply Likes
Okay thank you. Have you ever experienced the error saving to a local machine? Or is only when you're saving to the server? We were looking at the error and it appears that it might be happening because of a conflict with another user who is attempting to access the server at the same time. Does it sound like that could describe your situation?
Photo of Janie Trudel

Janie Trudel

  • 6 Posts
  • 3 Reply Likes
I tried saving locally to My documents without any trouble, though it's hard to tell as the problem doesn't always occur.
We are about 30 people in various departments in the office accessing the server at all times, so it could be it. However, it never happened before the update. Our entire work is done on the server, with very little saved locally on our own computers. PSD are opened from the server and saved to the server directly. But saving a PSD normally doesn't cause any trouble, it's only the Image Processor.
Trying to get everybody off the server when we try to save, that'll be impossible. 
Photo of Todd Shaner

Todd Shaner, Champion

  • 1111 Posts
  • 360 Reply Likes
This can occur if another process accesses the destination folder on the network drive when running Image Processor. Some possible causes:

1) Another other user is accessing the folder on the network drive.

2) A backup process has started and is accessing the folder.

3) Windows Indexing service has started and is accessing the folder.

Solution
1) Make sure no one else has access permissions to your folders.
Also make sure your server administrator isn't accessing the folders.

2)Make sure backup processes are scheduled to run when no one is working.

3) Go to Control Panel> 'Indexing Options,' click on 'Modify,' and uncheck the destination folder on the network drive.
Photo of David Converse

David Converse

  • 443 Posts
  • 128 Reply Likes
The general recommendation is to not work off a server (speaking as a long-time IT guy.) Work locally and copy back is much safer.
Photo of Janie Trudel

Janie Trudel

  • 6 Posts
  • 3 Reply Likes
Working off the server and copying back would be nearly impossible with the current structure of the company. Everybody, from our graphic department to our workshop, is connected to the server. Everybody works on it constantly. So basically everybody has access to all the folders at any time.

Backups are scheduled in the middle of the night, so not a problem on that side. And the server isn't indexed on my computer, don't know for the 30 other ones.

I just don't understand because it used to work, and we've been working off a server for the past 10 years or so, with our current server for the past 4 or so years.
Photo of David Converse

David Converse

  • 443 Posts
  • 128 Reply Likes
Typically it works until it doesn't. This may be an indication that you need to spend money on newer server hardware. Four years is about the lifespan. Everything now is virtualized and a good IT architect can look at your setup and make recommendations.

Personally, doing IT, I'd tell you not to do it that way.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1111 Posts
  • 360 Reply Likes
Janie, to rule out server issues you can have one or two people install the Previous PS and Bridge version you were using before upgrading to the latest versions (8.0.1 and PS 19.1). There's no need to uninstall the latest versions as you can have both installed at the same time. Go to the Creative Cloud app and click on the down arrow next to 'Open' for both PS and Bridge. Select 'Other Versions' and install the last version that was working with no issues. Just make sure you remember, which version you're using...it's easy to forget!

Photo of Janie Trudel

Janie Trudel

  • 6 Posts
  • 3 Reply Likes
I will install the 2017 Version, which was the latest one we were using before it started crashing, and we'll see.
Photo of Janie Trudel

Janie Trudel

  • 6 Posts
  • 3 Reply Likes
I installed the 2017 versions of Bridge and Photoshop, and ran an Image Processor and it failed twice trying to save 14 pictures. So it was just a coincidence that it started happening at the same time as we updated to the 2018 versions.

So what can we try now...?
Photo of Todd Shaner

Todd Shaner, Champion

  • 1074 Posts
  • 347 Reply Likes
We've eliminated PS as the source of this conflict. So something has changed on the network administration side (server software, user access rights, etc.).

David Converse provides the best solution and it appears Adobe agrees:

https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html

Recommended workflow
Technical Support strongly recommends working in Photoshop directly on the local hard disk. To prevent data loss, save files to your hard disk first. Then transfer them to the network or removable drive in the Finder or in Windows Explorer. To retrieve files, copy them in the Finder or in Windows Explorer from the network or removable drive to your hard disk. You can then open the files in Photoshop. This workflow avoids problems that occur when network system setups or removable media device drivers are incompatible with the operating system or Photoshop.

The only other option is to try and determine what has changed with the network system setup or user access. You may need to bring in an IT consultant as David Converse suggested and invest in new server HW and SW. Even then it's prone to fail again some time in the future.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14551 Posts
  • 1894 Reply Likes
If it used to work and now doesn't what's changed? Have there been any changes/updates to the server? Have any access privileges changed? Are there more users accessing the same folder?

See this document for troubleshooting steps and support boundaries with file servers:

https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html