Event ID 54 in ousb2hub: Print jobs not clearing

[Terry Preuit]

Hello,

Finished print jobs are getting stuck in the printer queue, causing
subsequent jobs to wait several minutes before they can be sent to the
printer.

This is a Windows XP SP3 machine, with a new Canon PIXMMA MX700
multifunction printer.

Last Friday I had to replace the original HP OfficeJet 7410 AIO because it
would no longer feed paper. Other than that, it worked great despite our
torture.

The owner wanted a different brand, however, so I recommended this Canon,
which I installed after removing the HP software and rebooting. However,
we're having two problems that seem to be related:

1) When sending a print job to the queue when it's empty, the job will print
and the last page of the job will eject, but the job remains in the queue.
The computer appears to think that it hasn't finished sending the job. For
instance, if I print a test page, it will send 72.1 KB of a 72.2 KB job and
then wait ten minutes or so before clearing the queue. This happens
printing other jobs/kinds of documents, as well.

2) The System Event Log shows many successive Event ID 54s from source
"ousb2hub":

Event Type: Warning
Event Source: ousb2hub
Event Category: None
Event ID: 54
Date: 99/99/9999
Time: 99:99:99 AA
User: N/A
Computer: AAAAAA
Description:
The description for Event ID ( 54 ) in Source ( ousb2hub ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
\Device\0000006c.
Data:
0000: 00 00 00 00 01 00 5a 00 ......Z.
0008: 00 00 00 00 36 00 04 80 ....6..€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

I've called Canon and they have no idea about this. I tried uninstalling
and reinstalling the USB hub and the printer, but that doesn't help either.

I'll be very grateful for any ideas.

 

[Bob I]

Does the HP still exist in the Print Server Properties? If so, remove it.

 

[Terry Preuit]

Hi, Bob,

Thanks for your reply.

It turns out that the old HP driver was still listed in Server Properties.
I removed it. All that's left are the fax and print drivers for the Canon,
and two Amyuni PDF converter drivers used by Quickbooks and another
application.

After I removed the HP driver, I tried printing a test page and got the same
result: it sent 77.4 KB of a 77.5 KB job, and did not clear the queue.

I rebooted the machine with that job still in the queue, and after Windows
started, it resent the test page to the printer with the same fershluginer
result. It took about five minutes for the queue to clear, at which time
the Event ID 54's from ousb2hub started appearing at a rate of 9 (yes, nine)
per second for about ten seconds every 4 to 6 minutes or so.

This seems pretty wierd to me. I'm going to uninstall the Canon and try
this again. I'll write back with the results.

David Dickinson
eveningstar at mvps dot org


Does the HP still exist in the Print Server Properties? If so, remove it.

 

[Terry Preuit]

I uninstalled all of the Canon software, including the driver that remained
in Server Properties. I restarted the machine and reinstalled the printer.
Same result.

I'm don't believe this is a problem with the printer. I'm using this same
model on several other Windows XP machines with no problems.

I'm stuck.

David

 

[Bob I]

Have you tried this particular printer on a different port, or PC.

 

[Alan Morris [MSFT]]

Who wrote the ousb2hub file? Why are they posting this error?

This file is not MS spooler file.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Chuck]

Given the name of the file, I'd suggest uninstalling the printer drivers,
then the USB port and controller drivers.
Reboot, and let windows reinstall the USB port and controller drivers. Then
properly install the required printer drivers.
Generally, this removes and properly reinstalls any links to the USB
drivers. Some motherboards have board specific USB drivers that can be
obtained from the OEM for the Mboard or the USB chipset on the board. Make
sure that you have copies of any USB driven device drivers that are/were not
included with windows.

 

[Terry Preuit]

Thanks for all of your suggestions, folks.

I have, indeed, tried uninstalling everything including the USB port and hub
drivers and then rebooting, and then reinstalling the printer software. But
I ended up with the same result.

Being that my client needed a printer that worked, I chucked the Canon and
went out and bought an HP Officejet Pro L7555 AIO.

Same problem: Event ID 54 Warning from ousb2hub, and print jobs stay in the
queue for several minutes after completion.

ousb2hub.sys is the USB 2.0 hub v2.0.5.0 from OrangeWare Corporation.

If I have to spend another sleepless night on this, I swear I'll give up
computers and become a pastry chef.

David Dickinson

 

[Patrick McTiernan]

I had an identical problem. The ousb2hub driver drives an NEC USB 2.0 PCI card in my PC, and Windows XP SP2 and above include a Microsoft driver for this card you can use instead.
When you switch over to the Microsoft driver, which is done just by asking Windows to update the driver for the NEC PCI USB2 controller, the new Microsoft drivers do NOT give the same print-job spooling problem.
I have had many intermittent problems with some USB2 devices, and not others, over the years, and I think this driver was the cause all along.
A fine example is that a Canon Pixma ip1500 printer DID NOT give problems attached to the USB port, but a Canon Pixma MP210 printer/scanner DID hang up after each job. One Fuji digital camera I have gave intermittent problems, another did not.
If it is relevant, I have a Gigabyte motherboard which uses VIA hardware for it's on-board USB 1.1 ports. Other posts I have seen on this problem seem to be from people who have similar hardware configurations.

 

[Terry Preuit]

Thanks, Patrick! You solved it!