Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 45 Source: Print
Document failed to print due to GDI/Driver error in rendering.
|English: Request a translation of the event description in plain English.|
After you apply the hotfix that ME324183 points to, the DEVMODE structure is checked before ICM data can be used. If a DEVMODE that is not valid is detected, the spooler may log this error. See ME324183 for more details on this issue.
According to Microsoft, a graphics device interface (GDI) or graphics driver error in rendering caused the document not to print. See MSW2KDB for additional information on this event.
This error is also logged when the tcp/ip port has been created with the wrong ip address for a jet direct. To resolve this, delete and recreate the port with the correct address.
Using W2K Terminal Services, client's print job reaches 72 bytes and hangs, does not print, and logs Events 10 and 45 on the server. Print job status is "Deleting." The queue never clears itself automatically. Solution: Gave "Everyone" full permissions to WINNT\TEMP and WINNT\SYSTEM32\SPOOL. Microsoft has a related article, but it doesn't solve the issue for users running Terminal Services (see the ME271901 link below).
I have a Print Server and started getting the above error message when I updated it with SP2 and none of my Terminal Servers would print. I obtained the hotfix described in the ME283795 article from MS and the problem went away immediately.
It seems that this error appears mainly on PrintServers. My experience is, beside the above things, to deactivate the Bidirectional communication under Connections for the printers. Some Printer Manufacturers explicitly indicate that!
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated