asked on

PCL XL Error printing from Word 2007

I have a Toshiba e-Studio280 printer. It worked fine until last week. I now have a problem when printing from Word 2007. I have an error message "PCL XL error Subsystem: xlgs Error: PS Engine Failure Operator: SetFont Position:20." The position will vary. This is only on documents created new in Word 2007. Older documents print fine. I performed a Copy/Paste into Word 2003 and had the same problem. I did a Copy/Paste Text only and it printed fine. I can print existing documents from Word 2007 with no problem. The Test page prints fine. I have not tried to print from Outlook or Excel. This is a network printer on our print server and is described as TOSHIBA eSTUDIO280Series PCL6, so that means Toshiba is using the PCL6 driver. There must be some type of code in the Word document that Word 2007 is entering. Does anyone have an idea how to remove this so we can use our printer?

ASKER CERTIFIED SOLUTION

souseran

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

RHWeston

ASKER

My original question was submitted as I was going home for the night. On my network my DC also doubles as a print server, and I have the Toshiba setup there for sharing. All users access this printer as a network printer. I have 7 users who have Office 2007, and 20 users with Office 2003. When a user looks in the directory for a printer, the Toshiba shows as described, using a PCL6 driver. There is something about a document created in Word 2007 which will not let it print to that printer. I have found and have downloaded, but not yet installed, a PS driver from Toshiba. As a new element this morning all users have had difficulty printing to the Toshiba. I am in the process of powering it down. That may have been the cause of the entire problem because it had only started yesterday. I will let you know the final solution. Or if you have any other suggestions, please post them

RHWeston

ASKER

The printer reboot seems to have taken care of the problem. Apparently something had become corrupted in the printer.

RHWeston

ASKER

It was not the final answer, but it helped me look in the right place. Thank you.