Hey all. First posting here but other than the HP forums, this issue
isn't patch / resolved / fixed as of yet.
Like many others on Google, printing multiple copies on Excel 2003
does the 1st copy fine but subsequent copies kick back the "PCL XL
error" and, as of now, the known workaround is to go the printer's
advanced settings and un-check "print optimization" as has been
suggested in the HP forums. It's been suggested that .NET framework 3
hosed something and that it is the most likely culprit. Our machines
have been running Office 2003 SP3 since shortly after it was released
with zero problems. This spring we introduced .NET framework 3.0 + SP1
and not things are goofy. I am inclined to agree that it's the root
cause.
All applications can print multiple copies be they from Office or
otherwise so it is not the fault of the driver. Seems to be happening
on out Laserjet 8150s, 9040s, 4300s, and 4350s.
So does anyone know of a patch, hotfix, registry hack, permanent fix
for this issue? Any links to KB articles or other sites would be
great. I've dug through the KB but nothing so far yet. Thanks for any
tips.
If you suspect it's related to .NET 3.0 have you tried updating for testing to .NET 3.5?
You may want to also want to use the link below to post in the Excel Printing discussion group as well to see what others may have
encountered on this. It's not one I've had an issue with.
I'm assuming that since you posted in the HP forums you have already checked for any HP printer driver/beta driver updates?
==========
<<"Thee Chicago Wolf" <.@.> wrote in message news:mf9vo31dg3m3i81dtck4qlj2ihirb9auv0@4ax.com...
Hey all. First posting here but other than the HP forums, this issue
isn't patch / resolved / fixed as of yet.
Like many others on Google, printing multiple copies on Excel 2003
does the 1st copy fine but subsequent copies kick back the "PCL XL
error" and, as of now, the known workaround is to go the printer's
advanced settings and un-check "print optimization" as has been
suggested in the HP forums. It's been suggested that .NET framework 3
hosed something and that it is the most likely culprit. Our machines
have been running Office 2003 SP3 since shortly after it was released
with zero problems. This spring we introduced .NET framework 3.0 + SP1
and not things are goofy. I am inclined to agree that it's the root
cause.
All applications can print multiple copies be they from Office or
otherwise so it is not the fault of the driver. Seems to be happening
on out Laserjet 8150s, 9040s, 4300s, and 4350s.
So does anyone know of a patch, hotfix, registry hack, permanent fix
for this issue? Any links to KB articles or other sites would be
great. I've dug through the KB but nothing so far yet. Thanks for any
tips.
- Thee Chicago Wolf>>
--
Please let us know if this has helped,
Bob Buckland ?:-)
MS Office System Products MVP
>>*Courtesy is not expensive and can pay big dividends<<
>Hi Wolf,
>
>If you suspect it's related to .NET 3.0 have you tried updating for testing to .NET 3.5?
>
>You may want to also want to use the link below to post in the Excel Printing discussion group as well to see what others may have
>encountered on this. It's not one I've had an issue with.
>
>I'm assuming that since you posted in the HP forums you have already checked for any HP printer driver/beta driver updates?
Here's the bizarre thing, MS issued a patch for it here: http://support.microsoft.com/kb/944203 and I already have it applied
to all the machines experiencing the issue. Odd thing is in other
forums, people report it with other apps. Excel is the only one doing
it for us though.
..NET 3.0 is the culprit for sure as I have done a before / after
comparison and it is broken after .NET 3.0. There a guy in the HP
forums who put together some lines of code that totally fixes the
issue. Here's hoping Redmond acknowledges they broke it and stops
blaming HP. This was the forum: http://forums12.itrc.hp.com/service/...readId=1111678
Sadly, no newer drivers are out there yet but there is a workaround
for the issue. Simply disabling "Print Optimization" in the Advanced
Settings during the print dialogue box does the trick. Perhaps XP SP3
will have a fix (fingers crossed).