Failed To Print Due To Gdi Driver Error In Rendering
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. -General printer discussion Forum at Tek-Tips HomeForumsServer RackPrinters-General printer discussion Forum Document failed to print due to GDI/Driver error in rendering. thread929-558936 Forum Search FAQs Links MVPs Document failed to print due to GDI/Driver error in rendering. Document failed to print due to GDI/Driver error in rendering. dietcokebottle (MIS) (OP) 26 May 03 10:33 Does anybody know the resolution to this error...It is happening on a Windows 2000 ServerDocument failed to print due to GDI/Driver error in rendering. Thanks RE: Document failed to print due to GDI/Driver error in rendering. Jomama46 (TechnicalUser) 26 May 03 16:18 I believe it is because your OS doesnt have a GDI. Nor NT/XP. Jomama Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Click Here to join Tek-Tips and talk with other members! Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. Registration on or use of this site constitutes acceptance of our Privacy Policy. Close Box Join Tek-Tips Today! Join your peers on the In
with a Deskjet 1220. It prints fine from 95/98 clients, but we've a couple of new XP clients that can't print. They get the error Event ID 45 Document Failed to print due to GDI/Driver error in rendering I've looked this up on the MS knowledge base and whilst its a bit vague the general gist is that the print job isn't working because its coming from a program with http://www.tek-tips.com/viewthread.cfm?qid=558936 an older printer driver. I've tried installing the latest driver from the HP web site (it claims the same driver works for 2000 and XP) but still the same problem. Any ideas on a fix? Top 1. Document failed to print due to GDI/Driver error in rendering Has anyone come across this http://www.verycomputer.com/1_c61d1930cee3e587_1.htm error before? We are running Win2K Pro desktops on a network. Also running a print server on 2000 server. This happens on more than one document but not all. Thank you 2. Phone Dinging Around 2 AM 3. document failed to print due to GDI/Driver error in rendering 4. PCW 8256 Serial Port ? 5. Event 45 Document failed to print due to GDI/Driver error in rendering. 6. WPI Benchmark Suite (1.1) (19/28) c.be.FAQ 7. Document failed to print due to GDI/Driver error in rendering. 8. HTML mode - configuring startup 9. HP JetDirect w/ Win2000 SP1 - Document failed to print due to GDI/Driver error in rendering. 10. Document failed to print due to GDI/Driver error in rendering 11. Event ID: 45 "Document Failed to print diue to GDI/Driver error in rendering. 12. Document failed to print due to GDI/Driver error in rendering. Printing garbage after hibernation 1 post • Page:1 of 1 All times are UTC Board index Spam Report
or graphics driver error in rendering caused the document http://kb.eventtracker.com/evtpass/evtPages/EventId_45_Print_47476.asp not to print.Resolution:Resubmit the print job. If http://www.eventid.net/display-eventid-45-source-Print-eventno-607-phase-1.htm the print job fails and you get the same message, obtain an updated printer driver from the printer vendor, install it, and then try printing the job againSYMPTOMS: When failed to you try to print to a network printer while you are using a guest or local user account, the print job may be placed in the queue but it may not be printed to the port failed to print (SPM or LPR). However, if an administrator logs on to the server and prints a test page, the subsequent print jobs may succeed from all clients until the print server is restarted. When you experience this problem, Event ID 45 may be reported in System Event log. RESOLUTION: A supported fix is now available from MicrosoftReference Linksevent id:45 and event source:PrintPrinter Server Problem When You Try to Print with a Guest or Local User Account
Did this information help you to resolve the problem? Yes: My problem was resolved. No: The information was not helpful / Partially helpful. Comments: Captcha RefreshAdd-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. read more... Event ID: 45 Source: Print Source: Print Type: Error Description:Document failed to print due to GDI/Driver error in rendering. English: Request a translation of the event description in plain English. Comments: EventID.Net 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. x 5 David Newton 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. x 5 Victor Oddy 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). x 7 Simon Curtiss 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. x 5 Elmar Sievers It seems that this error appears mainly on PrintServers. My experience is, beside the above things, to deactiva