Nam
Wed Jun 11 21:54:01 PDT 2008
They are all connected to the net.
"Alan Morris [MSFT]" wrote:
> That narrows this down.
>
>
> This is still a resource issue. I am sure the jobs would print by stopping
> the spooler service and starting the spooler service. The spooler does not
> have a security token for the user on spooler restart so the job is
> scheduled in the spooler security context.
>
> make sure that the Windows\temp directory is writable by administrator. GDI
> , this is the rendering component, will place spl.tmp files in this location
> during the printing process.
>
>
> It's unclear when you say you can't use printers. I assume you can use the
> print queue but nothing every departs the machine.
>
>
> How are the printers connected to the machine, USB, net?
>
>
>
>
> --
> 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.
>
> "Nam" <Nam@discussions.microsoft.com> wrote in message
> news:D2EAB50B-F2C5-4B68-8296-E03519E83B17@microsoft.com...
> > Yes, every sort of files, not just pdf, fails to print. And, when I
> > installed
> > SP2, I deleted all BUD files and let it be regenerated. And, in this time,
> > I
> > found an interesting fact. While using my computer, I can't use printers
> > and
> > all printing jobs remain uncompleted in the spool. But, when I restart my
> > computer, all the printing jobs in the spool are completed just at the
> > moment
> > that Windows starts! That is, printer works just at the moment Windows
> > starts.
> >
> > "Alan Morris [MSFT]" wrote:
> >
> >> And 0 is success!!
> >>
> >> Most likely some resource allocation failed, GDI resets the last error to
> >> 0
> >> and masked the real issue.
> >>
> >> This fails to print all the time, correct? I assume other files than
> >> just
> >> pdf.
> >>
> >>
> >> After SP2 install, are the BUD files regenerated? (file size of BUD file
> >> in
> >> C:\WINDOWS\system32\spool\drivers\x64\3 is not 0).
> >>
> >> --
> >> 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.
> >>
> >> "Nam" <Nam@discussions.microsoft.com> wrote in message
> >> news:B7335105-EF29-414C-A21B-4503EF9CF913@microsoft.com...
> >> > Here I attached the error event:
> >> > -----------------------------------
> >> > Event Type: Error
> >> > Event Source: Print
> >> > Event Category: None
> >> > Event ID: 6161
> >> > Date: 2008-06-08
> >> > Time: ?? 8:10:55
> >> > User: NT AUTHORITY\SYSTEM
> >> > Computer: CUOCUONM1
> >> > Description:
> >> > The document 01023411.pdf owned by Administrator failed to print on
> >> > printer
> >> > FX DC 286 PCL. Data type: NT EMF 1.008. Size of the spool file in
> >> > bytes:
> >> > 5701632. Number of bytes printed: 3949340. Total number of pages in the
> >> > document: 1. Number of pages printed: 2. Client machine: \\NEOCUONM1.
> >> > Win32
> >> > error code returned by the print processor: 0.
> >> >
> >> > For more information, see Help and Support Center at
> >> >
http://go.microsoft.com/fwlink/events.asp.
> >> > -------------------------------------------------
> >> >
> >> > And clicking the above link brought me the following message:
> >> > ---------------------------------------------
> >> > Details
> >> > ID: 6161
> >> > Source: Print
> >> >
> >> > We're sorry
> >> > There is no additional information about this issue in the Error and
> >> > Event
> >> > Log Messages or Knowledge Base databases at this time. You can use the
> >> > links
> >> > in the Support area to determine whether any additional information
> >> > might
> >> > be
> >> > available elsewhere.
> >> > -------------------------------------------------
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > "Alan Morris [MSFT]" wrote:
> >> >
> >> >> Well 6161 is the failure to print event. What is the error in the
> >> >> event?
> >> >>
> >> >> 2 is file not found
> >> >>
> >> >> 5 is access denied
> >> >>
> >> >> 6 is invalid handle
> >> >>
> >> >> 8 or 14 resource constraint.
> >> >>
> >> >> --
> >> >> 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.
> >> >>
> >> >> "Nam" <Nam@discussions.microsoft.com> wrote in message
> >> >> news:5AC5B181-7800-4710-BDF4-398D28B383D7@microsoft.com...
> >> >> > Thanks for your interest.
> >> >> >
> >> >> > Well, there is no special event log but an ordinary print error with
> >> >> > the event ID 6161.
> >> >> >
> >> >> > And, in the path "C:\WINDOWS\system32\spool\drivers\x64\3",
> >> >> > I could find unidrv.dll, unidrvui.dll, and unires.dll. They were all
> >> >> > in
> >> >> > the
> >> >> > same version, 0.3.3790.3959.
> >> >> >
> >> >> > "Alan Morris [MSFT]" wrote:
> >> >> >
> >> >> >> I'll let the other posters go. Back to the printing issue.
> >> >> >>
> >> >> >> Are there any events in the system event log?
> >> >> >>
> >> >> >> Most HP and Epson printers use unidrv components
> >> >> >>
> >> >> >> What are the versions of unidrvui.dll unidrv.dll and unires.dll?
> >> >> >> Ideally
> >> >> >> they should all be the same.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> 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.
> >> >> >>
> >> >> >> "Nam" <Nam@discussions.microsoft.com> wrote in message
> >> >> >> news:59108900-82A4-4599-A665-B42B6075DFBA@microsoft.com...
> >> >> >> > Hi All,
> >> >> >> >
> >> >> >> > I am running Windows XP x64. I have two printers,
> >> >> >> > one is HP and the other is Epson. But, I have not be able
> >> >> >> > to use my printers after installing sp2. I've tried many things
> >> >> >> > to fix this problem. I have reinstalled the lastest
> >> >> >> > drivers, and I've also reinstalled Windows several times. But
> >> >> >> > the only way that works was to delete SP2.
> >> >> >> >
> >> >> >> > Actually, I've found a related topic:
> >> >> >> >
http://support.microsoft.com/kb/832219/en-us
> >> >> >> >
> >> >> >> > I did according to the instruction, but it didn't help at all.
> >> >> >> > Is there any other things I can try?
> >> >> >> >
> >> >> >> > Please help me!
> >> >> >> >
> >> >> >> > - Nam
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>