LaserJet P3015 - GE Issued Warning: 76 & Two PCL XL Errors

[ElliotHarrison]

Hello everyone,

Got a strange issue affecting a user.  The users laptop is connected to a network via wireless and is connected to a shared network printer.

When the user goes to print a file, it will normally print a couple of pages and then print out the following errors:

GE Issued Warning: 76

 &

PCL XL error

Subsystem: KERNEL

Error: Illegal Operator Sequence

Operator: 0x1b

Position: 1633

&

PCL XL error

Subsytem: IMAGE

Error: ExtraData

Operator: ReadImage

Position: 2914

I have tried removing the printer and then re-installing it but the issue still exists.

Anyone got any suggestions?  Thank you!

[Rainbow7000]

To get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial product. You can do this at Commercial Forums.

I hope this helps! 🙂

[ElliotHarrison]

Thanks for your help!

Thankfully, I found a solution to this problem, it eventually lead to re-adding the printer on to the users PC, but also installing the PCL 5 driver instead of PCL 6.  This worked like a charm.

[Kevin_Herr]

I know this is a bit late as far as a response but maybe this will help someone else in the future. 

HP LaserJet P3015 - My Solution to  GE Issued Warning: 76 was to configure the Port Settings to LPR.

1. Click the Ports tab on the Printer's Properties.
2. Click the desired port you plan to use.
3. Click Configure Port...
4. Select the LPR radio button.
5. Set Queue Name to any name you want.

This also has solved an issue with an HP printer spewing copies of a one page print job.

[Richard1960]

My CP3525dn printer had stopped printing and was printing an error message -

PCL XL error

Subsystem: USERSTREAM

Error: MissingData

Operator: ReadFontHeader

Position: 29

I tried updating the firmware, but that didn't help.

Also tried the Print and Scan Doctor, which was no help either, but did get another error message -

GE Issued Warning: 75

After searching the GE Issued Warning I found your 'late' post and it worked just fine. 

Thanks.