asked on

@PJL Printer errors

Have a printer shared over a network taht has started giving errors when printing.

When trying to print anything, the follow happens:

1 page prints some errors, then another blank page, then the actual print job.

The page with errors has the following on it:

"@PJL SET JOBATTR="JobAcct8=cklosicki @PJL SET JOBATTR="JobAcct9= @PJL SET RET="

Everyone in the office that uses this printer is experiencing the same issue.

Believe the printer is an HP Laserjet 4000 using PCL5 drivers. Shared from a WIndows 2003 server. USers are on Windows 7.

This has only been happening for the past couple of days.

ZamZ0

Can you check Windows Update logs to see if Windows updated the drivers on its own recently? Windows has a habit of updating to the wrong drivers, especially with HP devices. Can you get the most recent drivers from HP and put them on the server? Also, you may want to check this link as it has some troubleshooting steps for @PJL errors.

http://ardamis.com/2012/02/15/troubleshooting-printing-problems-with-hp-upd-and-pjl/

Also, can you tell me are the clients running 32-bit or 64-bit Windows? And the server?

ASKER CERTIFIED SOLUTION

David_Ingledew

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SBSWIZARD

ASKER

I didnt see any updates for the drivers on the printer. I also have three other printers of the same model on the network and they are not experiencing any issues.

This is a new issue, but now the printer is going Offline and the only way I can ping it or get connection to it again is by power cycling the printer.

David_Ingledew

The printer is going offline on the workstation only? If so thats a simple one to fix - I can find you the reg change but effective you force synchronous rpc on the server, then all the workstations also use synchronous rpc and they never go offline on the site we had to fix it at.

If this is only affecting one printer, I would do the following:

Check that device has the same memory level as the working devices
Check the event log for that device, it may show repeated occurences
A) Swap devices to confirm if it is a device issue, or in fact how someone is using it in that location (Or)
B) Factory reset the affected device (and a cold reset if it a HP) to ensure it's "standard"