Powerhousecomputing
asked on
Cannot print in Windows Vista
Using Vista Business SP 1 on my 2003 SBS domain. I cannot print because the Printer Spooler service keeps closing down. This is the error recorded in the application log:
EventID:1000
Faulting application spoolsv.exe, version 6.0.6001.18000, time stamp 0x4791956c, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000005, fault offset 0x00065a20, process id 0xdcc, application start time 0x01c9b8f4cb1a6a0c.
I have checked the Service Log on which is set to local system account and is allowed to interact with the desktop.
EventID:1000
Faulting application spoolsv.exe, version 6.0.6001.18000, time stamp 0x4791956c, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000005, fault offset 0x00065a20, process id 0xdcc, application start time 0x01c9b8f4cb1a6a0c.
I have checked the Service Log on which is set to local system account and is allowed to interact with the desktop.
Check that the dll is not damaged. Reported size should be 1.14 MB (1,203,792 bytes). Find it in Windows system32.
Chris B
Chris B
ASKER
The size is correct.
I am using a windows server to share the printer. i have also added an additional vista driver in to the printer managment console. Unfortunately it has not worked. I attempted to install the printer locally on the machine but on reboot the computer added the printers that it found shared on the server. (See other open question i have posted.)
I am using a windows server to share the printer. i have also added an additional vista driver in to the printer managment console. Unfortunately it has not worked. I attempted to install the printer locally on the machine but on reboot the computer added the printers that it found shared on the server. (See other open question i have posted.)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is this print queue connected via a print server? If so, I would advise uninstalling/reinstalling the driver for the printer in question on the print server. Or potentially using a different version of the driver.
Also removing any excess drivers from the print server (old print drivers no longer used etc) is always a good idea when you start having problems. :)