Download lagu cakra khan ost sinetron bidadari bidadari surga sctv youtube. I've got an odd issue going on with one of our Dell servers that I can't quite wrap my head around. We've got a PowerEdge 2900 running Server 2003. This machine runs DNS, AD, and hosts a few files and small databases. Nothing fancy. I have 2 Ricoh Afc MP-3500 copiers on the network, and they are showing up in the printer directory without any issues. Over the weekend, I noticed that I could not RDC to the server from the house. I got to the office and could not open a shared folder from another workstation, nor access any databases, etc.
It was as if the network connection had just locked up. I rebooted and all was well for about 24 hours. Rebooted again, same results. I was able to dig around yesterday and was stumped. The first thing I noticed is that the networked printers just showed 'opening' when viewed from the printer folder of any XP workstation on the network. I tried deleting the printers and was able to get as far as 'copying drivers' when adding from the printer directory. The wizard just locked up. At the server's console, I noticed very slow performance and network issues galore. I rebooted a couple of times from the console, and everything would be fine for about 10 minutes but those printers would just keep showing 'opening' on the XP workstations. I went back to the server and opened the printer folder where the MP-3500s are shared from, and could not get a response. That is to say, I clicked on the Printers and Faxes link under the Start button and nothing happened at all. I then restarted the print spooler, and just as soon as I did, the printer/fax folder popped open (on it's own, from my attempt right beforehand) and everything instantly started working on the network. Printers, databases, everything. I rebooted the server and waiting for it to fail again, and was able to duplicate the same thing, several times. ![]() It seems that something is up with the spooler, but I'm not sure where to go with this. I've never seen a print spooler lock an entire network up like this, even with networked printers -- but then again, I haven't seen it all. =) Any ideas or suggestions on this one? When it locks up, check Task Manager to see if spoolsv.exe is taking 100% of the CPU. ![]() I've seen a million times where an errant print job will hang up the spool service. Restarting the spool service or even rebooting the server will alleviate this, but only temporarily, because the errant print data is still in the spool file and will try again, bringing the CPU to 100% and recreating the problem. Stop the spool service, the navigate to the spool folder (typically C: windows system32 spool) and delete anything in there. Then, restart the spool service.
0 Comments
Leave a Reply. |