Why can't we print from CS5 Photoshop on Konica Magicolor?

Question

Why can't we print from CS5 Photoshop on Konica Magicolor?

Ever since installing Adobe CS5 we have not been able to print flattened Photoshop files on our Konica Magicolor 7450. PSDs, yes. We've run Disk Utilities (Repair Permisions); OnyX; deleted and re-installed drivers; Installed the 10.6.8 Combo upgrade. Read every forum I could find. Learned more about "Cups" than I probably needed to know. I also spit 3 times and threw salt over my shoulder, and did a computer-spiritual-cleansing ritual....just in case! Ok. Not really, But I'm at the point where I'd seriously consider all of those things. Anybody got any ideas???

Mac Pro, Mac OS X (10.6.8)

Posted on Jul 15, 2011 3:13 PM

Reply

Answer 1

PAHU

Level 6

16,705 points

Jul 15, 2011 5:53 PM in response to sufromsanta barbara

What is happening when you try to print? Are you getting cups related error messages? Does the KM have a Fiery print server attached?

Reply

Answer 2

Jul 15, 2011 7:37 PM in response to PAHU

When we hit print, the files start processing and then just stop. Never makes it to the printer. The printer is on a network; no postscript, no fiery. The cups error log reads:

W [15/Jul/2011:12:13:30 -0700] No limit for Validate-Job defined in policy authenticated - using Print-Job's policy

W [15/Jul/2011:12:13:30 -0700] No limit for Validate-Job defined in policy kerberos - using Print-Job's policy

Reply

Answer 3

MooMuir

Level 1

50 points

Jul 15, 2011 7:42 PM in response to sufromsanta barbara

Not a solution, but a workaround...

This might sound a little silly, but if you save the printout to a PDF file, can you print the PDF? CUPS is not the most fun utility, and I found this was a workaround...

Reply

Answer 4

Jul 15, 2011 7:57 PM in response to MooMuir

Yes, we can...and have..done that. In most cases we need to send print outs of the files in the format that they're supplied. So in most cases workarounds won't cut it. This all started happening as soon as we upgraded to CS5. No problems before that. (And why will a layered PSD file print, but not a flattened TIFF? V-e-r-y frustrating.)

Reply

Answer 5

PAHU

Level 6

16,705 points

Jul 15, 2011 8:18 PM in response to sufromsanta barbara

Thanks for the cups error log but those entries are not related to the problem. Those messages started appearing after one of the previous point updates - I think it was 10.6.7.

If there is no entry showing a print job ID, usually shown inside square brackets, then PS CS5 could be failing before any of the driver modules are being used. This sort of fits in with what you mention. So if you were to look at the Console app you may find crash reports for PS.

As for why TIFFs fail but PSDs don't, one thought would be plugins. But generally it would be a plugin related to the printer, so in that case there would have to be some record of the plugin being called by the app. And if the device is not Postscript, then the PSD will still be flattened somewhere in the process before being submitted to the printer, as it wouldn't be able to handle the layering. So this observation is confusing. If you save as some other image format, does that print?

Reply

Answer 6

Jul 15, 2011 8:35 PM in response to PAHU

My mistake. It does postscript. It just doesn't hold the file for future reprinting. Sorry about that. As for saving it as a different format (e.g. jpeg or eps), sometimes they print and sometimes they don't. Haven't figured out what's different from file to file that makes the difference. Got any idea of how to find out if it is a plug in we need? Or any log or error code that would give me a hint?

Reply

Answer 7

PAHU

Level 6

16,705 points

Jul 15, 2011 8:39 PM in response to sufromsanta barbara

Open the Console app (Applications > Utilities), click Show Log Lists and browse through the logs. The system log will give some detail but it tracks everything so it would be handy to print the TIFF again and then check the log so the issue is most recent. The system log can then also show that the problem has been recorded in another log, such as an Adobe PS Crashlog.

Reply

Answer 8

Jul 15, 2011 8:50 PM in response to PAHU

I'll give that a try when I'm back in the office on Monday. Thanks again for your time and help! I'll keep you posted. Thanks!

Reply

Answer 9

Jul 18, 2011 9:49 AM in response to sufromsanta barbara

Here's the error code that showed up on the system log when I (unsuccesfully) tried to print a TIFF:

2 cupsd[267]: sandbox cache error: database is locked

Got an idiot-proof translation for me? 😉

Reply

Answer 10

Jul 18, 2011 11:20 AM in response to PAHU

Here's the error code that showed up on the system log when I (unsuccesfully) tried to print a TIFF:

2 cupsd[267]: sandbox cache error: database is locked

Got an idiot-proof translation for me?

Reply

Answer 11

PAHU

Level 6

16,705 points

Jul 19, 2011 12:58 AM in response to sufromsanta barbara

sufromsanta barbara wrote:

Got an idiot-proof translation for me?

Sorry but no. I can see that the cups daemon, process ID 267, has a problem but not exactly sure what database would be locked. There may be other references to process ID 267 in the log. If not then that message is too cryptic for me.

Reply

Answer 12

Jul 19, 2011 8:43 AM in response to PAHU

One last question. Re: your reference to plug-ins. Were you indicating a plug in might be causing the problem, or that I'm missing a plug-in that might help the problem? Thanks again so much for all your help. At the very least you've shown me where to start looking. I really appreciate your time and efforts!!

Reply

Answer 13

PAHU

Level 6

16,705 points

Jul 20, 2011 1:08 AM in response to sufromsanta barbara

sufromsanta barbara wrote:

One last question. Re: your reference to plug-ins. Were you indicating a plug in might be causing the problem, or that I'm missing a plug-in that might help the problem?

My thoughts, and experience with the Adobe suite, is that a plugin could have been causing the problem. This can occur after updating the application or updating a driver or both.

You mention installing CS5. If you had CS4 or earlier installed and installed CS5 'over the top' then I've had personal experience with this creating crashes and unwanted printing results. I've also seen orphaned plugins, often a left-over from a previous driver update, cause printing issues similar to your symptom. But for many of these issues there has always been a trail of cause shown in the logs and this does not appear to be happening in the same way for you.

One action that you can take to determine if the Konica driver is a cause is to use the Generic Postscript driver. If the Generic PS also causes an error with printing the TIFFs then it at least rules out the Konica driver as being a cause.

Another action would be to purchase an external USB drive, format it to OS X Journaled and then install 10.6.x and then use the 10.6.8 combo update. Then install CS5 and see if the TIFFs cause the same problem.

Reply