There are only Win2003-Driver (HP, Canon).
Maybe about 15 different printers in 6 locations.
All drivers are terminalserver-certified (all new installed).
I've logged every printjob. But there is no special driver in use before the
system hangs.
Here is the story:
First: popup error 1000 in systemlog
2...5 seconds
Second: application error 1000 in application log
-> no terminal-login possible
Thank you
Joerg
"Christoph Dommermuth" wrote:
> Can you see Windows NT Compatible drivers in the print server propertiesß
>
> Thanks,
>
> Christoph
>
>
> "Joerg Doeschner" schrieb im
> Newsbeitrag
> >2 times a week my printspooler hangs (application error 1000 and 1004).
> > After this a new logon for new users is impossible until i restart the
> > spooler-service.
> > Currently logged users are not affected.
> >
> > My System:
> > Server 2003 SP1 all Patches
> > Terminalservices
> >
> > I've changed all printer-drivers to original MS-Drivers and MS-Certified
> > drivers.
> > The event isn't bound to a special pritjob from a special driver.
> >
> > I'ts driving me nuts ....
> >
> > Joerg
>
>
> >> Stay informed about: Printspooler couses hang