Quicken 2014 Deluxe Printing Problem

Feb 21, 2015 6 Replies
K

I've had this problem for a while, but since I so seldom want to print anything in Quicken, I've ignored it. But it's starting to annoy me.



I'm running Windows 8.1. My printer is a Samsung CLP315.



I don't normally print checks, but I just tried printing one to verify that it works correctly. It does.



My problem is printing reports. It never works. When I try, it prints this error message:



SPL-C ERROR - IllegalResolution



POSITION : 0x0 (0)



SYSTEM : src/xl_tbl



LINE : 771



VERSION : SPL-C 5.35 11-20-2007



I've checked in Printer Setup, and I haven't seen anything that looks wrong. Anyone know what's wrong and how to fix it?



And by the way, printing from all other applications works fine.



Vote
Twitter Facebook LinkedIn
Z

try to print to a PDF as a test

Vote
Twitter Facebook LinkedIn
K

Sorry, I should have mentioned that I already done that, and it works fine.

So a workaround for the problem is printing to a pdf file, and then printing the pdf file. But I would still like to find out what's wrong and how to fix it.

Printing to the printer from Quicken, I can print checks but not reports. And looking at the two printer setup dialogs, I don't see any differences.

Vote
Twitter Facebook LinkedIn
J

Sorry, I should have mentioned that I already done that, and it works fine.

So a workaround for the problem is printing to a pdf file, and then printing the pdf file. But I would still like to find out what's wrong and how to fix it.

Printing to the printer from Quicken, I can print checks but not reports. And looking at the two printer setup dialogs, I don't see any differences.

--------------------------------------------------------

Have you tried resetting your Quicken printer settings?

File > File Operations > Validate and Repair. Put a check mark in "Reset all Quicken printer settings ...". Click OK.

Vote
Twitter Facebook LinkedIn
K

No, I hadn't. I had never even looked at that dialog box before and didn't even know it was an option. But at your suggestion, I just did it.

Thanks very much! That fixed it.

Vote
Twitter Facebook LinkedIn
M

Thanks, I was having that problem as well. Worked for me too. Mike

Vote
Twitter Facebook LinkedIn
K

Glad it worked for you too.

By the way, no big deal now that I know how to fix it if it happens again, but John, do you, or anyone else here know what causes this?

Vote
Twitter Facebook LinkedIn

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required