HPmon printer problems

Recently I built up an NT 4 serv with SP4,  I installed Jet admin and set up 40-45 printer shares on it and the same number of ports. All worked fine and printed test pages to all the printers. I set up HP 8000 driver for a printer that was connected, reboot and whammo......Spoolss failed to start, when I try and start Jetadmin I get exception error. The same with trying to set up port or anything else. I have removed Jet admin, been through registry and cleaned all files related to it and still when I set up Jet Admin it happens again. Has anyone had this before or know what is going on?
Thanks
Mike
mlbrookeAsked:
Who is Participating?
Advertise Here
 
kjmeierConnect With a Mentor Commented:
I had the exact same problem on my NT 4 box after I've installed SP4 and the latest JetAdmin Version. MS and HP don't know why this problem occurs. I had to reinstall the Jetadmin version (and of course the HP printer port) that is shipped with the SP3 CD. After that everything worked fine again. This was a suggestion from HP !
0
 
sweatbeastCommented:
There seems to be something funny going on with HP. We installed 3 HP 4000T's the other day and we get spoolss.exe errors all the time! As yet no resolution - microsoft don't have an answer, HP don't have an answer. All either could suggest was applying SP4 which we have done (cautiously!) to no avail.
We get the error at the workstation end - after the error occurs everything is fine except for printing - all the printers disapear! Re-booting solves the problem but it eventualy re-occurs.

Is this similar to your experience?
0
 
mlbrookeAuthor Commented:
Yes, my problem is similar to that. But once i reboot the printers are gone already. Unless I remove the JetAdmin software. If I do that then the printers are there, but no ports are avaliable (obvisously, b'cos no JetDirect ports anymore!). What I have done is to restore from backup so the ports are all avaliable again, with SP4. This is with JetAdmin 2.5 b'cos I think 3.0 caused the problem, will keep you posted as tomorrow I will reinstall the 8000 drivers (they are probably the cause)
0
 
mlbrookeAuthor Commented:
So am I able to use SP 4, with Jet admin?, as this is the required upgrade. We are upgrading an NT 3.51 to NT 4 server -by building another server putting all the print queues on it and then renaming it as the original 3.51 server. Apparently NT 4/SP 3 does not rename print queues when you rename the server so they still have the old UNC path.
0
 
kjmeierCommented:
There's no problem with applying SP4 to the server. The only thing you need from the SP3 CD is the JetAdmin version on there - you should find that in its own directory on the CD. That version of JetAdmin (even though it's pretty old of course) is the only one that ever worked correctly on my servers.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.