When we reboot our server every morning,,We get an error message"spoolss.exe-Entry point not found">>The procedure entry point GetJobA could not be located in the dynamic link library spoolss.dll<<< could someone help me ,this is becoming a problem,,We have loaded Serice Pack 6 for Terminal server,,this mahcine has Metaframe 1.8 also wiht the latest hot fix
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 Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NT 4 Termnal Server Spoolss.exe
- Thread starter vick53
- Start date
CitrixEngineer
Technical User
Try Forum48
I'd guess you have a missing or corrupt Localspl.dll (should be in %SystemRoot%\System32\). Other files to check are spoolss.dll and spoolss.exe, although I've heard of people fixing this by deleting the whole spool subfolder. I've never done this myself, so if you want to try this, simply rename the folder and it should have the same effect.
This could be caused by many things, but I've seen HP LaserJet 5si's cause similar things more often than any other printer driver. Did this start happening after you installed a printer? Are all your printers DEFINITELY compatible with Terminal Services?
Replace localspl.dll and/or either of the others with a copy from the latest Service pack or any Windows NT4 Terminal Server Edition CD-ROM - you may find that re-applying Service Pack 6 works (although you'd then need to re-apply any MetaFrame Service Packs you have).
Hope this helps
CitrixEngineer@yahoo.co.uk
I'd guess you have a missing or corrupt Localspl.dll (should be in %SystemRoot%\System32\). Other files to check are spoolss.dll and spoolss.exe, although I've heard of people fixing this by deleting the whole spool subfolder. I've never done this myself, so if you want to try this, simply rename the folder and it should have the same effect.
This could be caused by many things, but I've seen HP LaserJet 5si's cause similar things more often than any other printer driver. Did this start happening after you installed a printer? Are all your printers DEFINITELY compatible with Terminal Services?
Replace localspl.dll and/or either of the others with a copy from the latest Service pack or any Windows NT4 Terminal Server Edition CD-ROM - you may find that re-applying Service Pack 6 works (although you'd then need to re-apply any MetaFrame Service Packs you have).
Hope this helps
CitrixEngineer@yahoo.co.uk
- Status
Similar threads
- Locked
- Question
- Locked
- Question