General discussion

Locked

Print Spooler crashes

By Mattius ·
This problem happens on a daily basis. In the system event viewer I get the following messages:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event I 7031
Date: 2/5/2002
Time: 9:35:38 AM
User: N/A
Computer: SULLEY
Description:
The Print Spooler service terminated unexpectedly. It has done this 21 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.


Event Type: Error
Event Source: Server
Event Category: None
Event I 2510
Date: 2/5/2002
Time: 9:35:49 AM
User: N/A
Computer: SULLEY
Description:
The server service was unable to map error code 1727.

This server is a secondary DNS and DC. HP webjetadmin and powerchute (for UPS) are installed.

This computer handles the printing for 30 printers and approximately 150 users and we want to add more. The computer is compaq proliant 530ML, dual 1GHz and lots of disk space. It also has a tape library for backup and arcserve 2000.The printers are HP and Aficio(also copiers).

Articles I found in the knowledge base say that installing SP2 will fix the problem, it didn't. I have the print spooler set to automatically restart after failure, but as you can see it fails quiteoften and is a problem.

Anyone have any ideas? Thanks in advance.

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Print Spooler crashes

by curlergirl In reply to Print Spooler crashes

I've not run HP's web JetAdmin program on a Win2K server, so I'm not sure if that would cause any problems - but I doubt it. I would take a look at the printer drivers that you're using and make sure they are all the most up-to-date drivers available for Win2K, and any workstations that have other versions of OS. The second error you described above (the one about being unable to map the error code) is a typical print driver error - the server can't map the error code because it is being generated by an incompatible print driver. Hope this helps!

Collapse -

Print Spooler crashes

by Mattius In reply to Print Spooler crashes

Most of the drivers are downloaded from the internet, all the Aficio come from their website and the HP drivers (4100 and 8100 series) come from HP website. The only native windows drivers I use are old ones like the HP4M. Our clients are using mainly windows 95 and 98.

Collapse -

Print Spooler crashes

by rguess In reply to Print Spooler crashes

Matt,

In my experience with Windows 2000, don't use the HP Jetadmin software. W2K already has provisions for you to print to a standard TCP/IP port or an HP Standard TCP/IP port. You might try to map your ptinters this way. I have also seen poorly written or not complient with W2K printer drivers cause this. They have done everything from crashing the spooler to blue screening the server.
I hope I was of some help.

Thanks,

Ron

Collapse -

Print Spooler crashes

by Mattius In reply to Print Spooler crashes

The webjetadmin software is not used to configure the queues, but rather to change settings on the printers. Some of the older printers do not have the embedded website so I use webjetadmin to configure settings remotely and update firmware. I couldmove it to another computer if you think it could be the problem.

Collapse -

Print Spooler crashes

by Joseph Moore In reply to Print Spooler crashes

I looked around and found that this was a problem with NT 3.51. On print servers that had many printers (and 30 printers counts), the RPC service would lose track of what is what.
Win2K shouldn't have a similar vulnerability, but maybe it does.
So, I would make sure the Remote Procedure Call (RPC) service is running.
I would also turn on Remote Procedure Call (RPC) Locator service.
With NT3.51, the print server would get confused with all of these print request going to all of these printers. It would get the printer names mixed up. RPC handles stuff like this. So make sure that both RPC services are running on your print server.
Also, is it possible for you to migrate some of the printers off this server onto another? That might really fix this.

Hope this suggestion helps.

Collapse -

Print Spooler crashes

by Mattius In reply to Print Spooler crashes

The RPC Service and Locator are both running. I don't know if they quit the same as the spooler, since they are set to automatically restart and if they do they are not loggin a seperate event. Has anyone been able to find out what is too many printers for Win2K? I hope it can handle more than 30...

Collapse -

Print Spooler crashes

by QuocH In reply to Print Spooler crashes

I think you should use jetdirect print servers for windows 2000 (I found this CD when I bought the hp jecdirect). It will configure windows2000 to support natively to the print server. Don't also forget to update your printer driver. Hope this help.
Quoc.

Collapse -

Print Spooler crashes

by Mattius In reply to Print Spooler crashes

I create the ports as HP Standard TCP/IP port already, what will installing that software help?

Collapse -

Print Spooler crashes

by ChrisSaw In reply to Print Spooler crashes

Hi,
First, I would like to know if your setup as it is right now has worked before. I'm sure the answer is yes. I recently had a similar problem on one of my customer and I passed 8 days to find the reason. May be it can resolve your problem or give you another way to search.
As you know, a print server can handle 18000 queue files in his directory. For my customer, the problem was the software Inoculate. When they was performing a network scanning, the application were creating temporary READONLY file in the print queue directory. When the maximum number of file is attained, the print server crashed. I know that there is also the same bug with McAfee network release.

Hope it help.
Christian.

Collapse -

Print Spooler crashes

by Mattius In reply to Print Spooler crashes

Thanks for all the responses. Due the nature of the problem we went directly to MS and they solved the problem. We had installed some Ricoh copier/printers on the server and their software created a print monitor and that was causing the crashes. MStold me to delete some registry settings and it has been fine since then.

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums