Win2K Printing to TCP/IP Printers "Unable to create a print job."

[vodkaredbull]

Windows 2000 Server has been working for months. After adding a new networked printer and sharing from server, any attempts to print to other printers fails with following error:

Test page failed to print. Would you like to view the print trouble shooter for assistance? Unable to create a print job.

Deleted new printer and removed new tcp/ip port and still have same error. 6 printers shared via server all now have same error. Reinstalled WIN 2K SP4 and no different. Can ping printers from server and also access them via IE as they are web enabled. If i use a workstation to try and print direct to printer via tcp/ip printing then works fine.

Have seen many posts on google groups with same problem but can't seem to find any fixes. My last resort is to delete all printers and ports then recreate them all but don't want to if an easy fix is available.

HELP ME!!!


Thanks.

 

[Mekkins]

I don't fool with network printers too much but is it possible that the original printers are trying to use the driver for the new printer? Look at the advanced tab in printer properties and make sure the correct driver is displayed.

 

[vodkaredbull]

I have found the answer. It appears Windows 2000 SP4 has some bugs that cause this issue. If this occurs don’t panic. Microsoft have a printer migration tool that you can use to export all printers. Then delete the printers and use the tool to import them again. In my case I couldn't use this method as I had already deleted all printers to go back to a clean setup. I ended up stopping the print spooler service then going into the c:\winnt\system32\spool\printers folder and deleting all files within it. Then restarting the print spooler service. Microsoft have confirmed this to be a problem in SP4 for Windows 2000.

I hope this helps.

P.S. Don't worry as this is the 1st time I have seen this and I have plenty of sites running SP4 with no problems. It is possibly something to do with post SP4 Hotfixes not being totally compatible with SP4. I know this sounds strange but trust me it works.