Anyway not a problem ask away. & Yes I do realize that the Print Server is running Debiam but because the Error Messages are all Windows Reports they are all I can point you to for a possible solution. They also seen to indicate that the Windows Box's are not communicating with the Debian Box and that the problem is at the Windows end. Maybe
Anyway the Event ID 61XX message relates to a failed Print Job as shown here
http://tinyurl.com/2l82bv
However what is interesting is this bit of that Article
[i][b]CAUSE[/b]
This problem occurs because the error that the underlying component reported was overwritten. Therefore, only the last error was reported. For example, the following Win32 error codes may have been reported: ? ERROR_SPL_NO_STARTDOC (3003)
This error code means that a StartDocPrinter call was not issued. You receive this error code when the print spooler cannot send data to the port. The print job is marked as "error printing." In this scenario, the print spooler repeatedly tries to send the data until the user cancels the job. The error that the port monitor component returns is overwritten when the user cancels the print job.
? ERROR_SUCCESS (0)
This error code means that the operation completed successfully. You receive this error code when an underlying component such as graphics device interface (GDI) returns a failure but does not set the last error.[/i]
This cane up in a Search for the CODE WIN 32 which may be useful maybe
http://tinyurl.com/3d95qv
The interesting bit here is
[i]CAUSE
This problem occurs when you do not specify the full path of the file you are printing to. If a file is specified as filename.prn, the file will be created in the %Systemroot%\System32 folder. Various users will have different rights to this folder. If you print to a file that is located in this folder, you may receive an "ACCESS_DENIED" error message. In this case, if you continue to write jobs to this same file, the spooler continues to try to print the job. This scenario can exhaust page-pooled memory and cause your computer to stop responding. [/i] seems pretty straight forward and may or may not be applicable in this case.
The Event ID 45 error seems to apply to Windows Servers rebooting unexpectally as there are 44 Listings on the M$ knowledge Base with this Event ID after a search. Not sure if this applies here or not but maybe it is useful
http://tinyurl.com/2pz2qe
OK so all of this means that the Windows 2003 Server isn't communicating with the Debian Print Server/Printer so something along the line is breaking down with the obvious thing being the Interface between the Windows Side of the LAN and the Print Server. The thing here is Samba being the most likely problem child if the 2003 Server is actually sending the Print Job onto the Print Server. So do you have any way to verify that the Windows Server/s are actually passing the Print Job on?
There could be a communication failure here or another possibility is a Driver Issue at the Debian Server which is preventing the Printer from working correctly.
Anyway HP lists the following Web Site for their latest Imaging & Printing Driver for Open Source Products
http://tinyurl.com/2pz2qe
That may be helpful though I'm not overly sure any more with this one.
Lets know if any of that was helpful
Col