Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

spoolsv.exe error

Status
Not open for further replies.

Spiff01

Technical User
Sep 14, 2005
24
CA
I am having an issue that i have not figured out yet.
I have a program called Broker CD - it is a program that users use to view and print Broker numbers off a network drive or CD.
It is a basic program, not much to the install - i dont think it is a 16 bit program...
The problem is that the program will not print. When you put in a broker number it pulls up the info in text format and you should be able to print.
On newer Dell GX620, GX280, it kills the spoolsv.exe when printing to a local printer, and it appears it prints on a network pritner but nothing comes out. Checked the print server to see if it is pushing a spoolsv.exe error in the event viewer, but not seeing anything there
Computers are running SP4 and I have tried everything i can think of. Using older print drivers, PS and PCL print drivers, cleaned out all the junk from the registry described in a microsoft article. tried regular fonts supplied in the program too.
Funny thing is that it will work on a GX1 with SP4 just fine.
NOw I am not sure how this program works when it prints. THe install is just a basic install file and the program files folder for it only has an exe file, the ini file a log file and another file.
THe error in event viewer when printed to a local pritner states the following...
he application, spoolsv.exe, generated an application error (close printprocessor)
cannot find anything on this...
any idea where to look next?
 
Check the parallel port mode settings between working and non-working machines.

If they are identical, the parallel port drivers had issues during the install of Windows. This article was written in an XP context, but the issue is identical under Win2k:
Last, consider modifying how the printer is defined even if locally attached. Create a printer share, then set the network sharename printer, rather than the physical printer, as the default printer. See MS-MVP Bruce Sanderson's discussion:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top