I have found, that on the 2000 Server, goto Printers and set each printer under the Advanced Tab, to 'Print Directly to Printer' - this resolves all issues. Okay its not ideal, especially if you use Print Monitoring Software, but proves that the issue MUST be with Windows 2000, or the transfering of the Job from the Workstation to the Server. Maybe everyone should use a decent Network O/S with proper Print Queues! (E.g Netware/Unix!)

0

I am also having similar problems. I am wondering if it is not related to Service Pack 3 for Windows 2000. There has been one post on this board stating the use of SP3 and I have taken note from other forums/sites reporting this problem that they too had SP3 installed. I too am experiencing this problem, but my server RAM usage jumps to more than 1.5GB, where the server only has 512MB. There are no print jobs in any queues and CPU usage is between 1 and 10% as usual. Does everyone here who is experiencing this problem have SP3 installed? Zakie

0

I too am getting the same error and I'm running windows 2000 server with sp3, hp Laserjet 4050TN, and a jetdirect card. I'm beginning to think that it could be sp3 because I have only encounter this error after installing sp3 a week ago. Late, Keo

0

The servers i'm seeing the problem on, are running SP3 and ALL the latest Windows Updates, with all the latest HP Printer drivers. I don't see any excessive usage of Ram (could be cause it all happens so quickly). Maybe check event viewer and see if you get the same 3 string of errors each time a job is printed.

0

same with me, happened after i loaded sp3 on print servers. i only get errors on my hp printers, all types, and only when printing from office 2000 apps.

0

I'm getting the same error message on Win2k Server w/ SP3 when I even print a test page but only when printing from the latest Laserjet 4Si and Laserjet 3D printers.

0

I'm experiencing the same thing with the hpdeskjet 5550. Also W2K Server/SP3. There are a couple of users who can print, and a few others who can't (from the SAME W2K Pro, no less!).

0

I found someone in a newsgroup who said you have to give Full Priviliges to "Authenticated Users" for C:\WINNT\TEMP on the printing server. Tis didn't work for me, but might help someone here (I hope). It annoys me that neither HP nor MS have documented this.

0

Righteo EVERYTHING was working fine on 2000 srv environment with 15 2000 pro users, upgrade to server to SP3 and now people can print for a few minutes after a full shutdown! After that I get event 61 and NOONE can print to any of 5 HP printers (4050n, 5100tn, d155xi, 750c+, 1220c). Totally bitchin! MS is NO help on this one so far!

0

I think you are right about SP3. We started getting this error the day SP3 was installed on our Windows 2000 cluster server.

0

I Have the same problem as you on SOME of my printers (after a recovery and SP3). The printer handling has just gone nuts. Found a solution to some printer models. Might help you guys. Laserjet 4Si and Laserjet 3D: http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xfa595c7609e9d61190050090279cd0f9,00.html

0

That post on HP.com was mine and it wasn't any help, unfortunately. I also tried the PS and PCL5 drivers and the same effect. What's wierd is that the other printers on my network aren't experiencing the same problem. Especially since I had a HP4050, 4100, and Laserjet 5SI and people have mainly reported the problem on the 40XX models. (shrug)

0

I do not have SP3 and I am getting this error. I am getting it across many printers in a print cluster. I have tried the print directly to the printer and that did not work for me. If anyone has any other ideas I would love to here them.

0

We have seen event ID 61 on both Lexmark and HP printers. Since upgraging to SP3, I have twice fixed problems with printers not printing by updating the drivers. On the print server, go to Server Properties and select the Drivers tab. Find the driver you are having problems with and select Update. This will reload or update the driver for all of the printers that use it. So far I have only used this method on printers using Windows drivers, not the manufacturs drivers.

0

I have had the same issue today. I installed sp3 on my cluster servers(where printspool is running) last night and today I have all sorts of printing issues. I narrowed it down to a few things and contacted microsoft. The pointed me to q329405. It is a dns issue. Go figure. If you think about it, it does make sense. They haven't officially released the fix yet so you can't get it off of the knowledge base but if you call them (it will be free because it is an issue with a service pack) they can give you the ftp link to get the hotfix. It worked for me. Good luck.

0

After installing a SMC-Barricade cable router that has an integrated printserver I experience similar problems. On my W98-PC printing via this printerserver works flawless. On my W2K-PC however it doesn't seem to work. I have SP3 installed. Dropping the printer, installing new drivers etc. doesn't solve my problem. On the HP-forum I see numerous people complaining about not being able to print anymore after SP3 is installed. They all get the same error 0x3F (63) event id 61 in their loggings. The error doesn't mean much. It only says that the document you wanted to print has been deleted. I suggest asking Microsoft what's going wrong.

0

I finally found the answer to my problems and solved my error message. What I forgot is that under Windows NT 4.0 I was printing to these printers using LPR and it's installed by default when you install Simple TCP/IP Services. Not so with Windows 2000. Once I did the upgrade and installed Simple TCP/IP Services, these particular printers (using Dlink and Jetlan print servers) stopped working and gave me the Event ID 61 error message when I set them up using Simple TCP/IP Port. Once I realized that LPR needed to be individually installed, I went into Add/Remove Programs, Windows Components, Other Network File and Print Services, and installed Unix Print Services, I could then set these printers up to work specifically on LPR ports and they worked again. Hope this helps! I'm back up and running with no changes to the workstations.

0

Well, I am having the same issue with a Sharp AR-507 PCL6 on a Windows 2K server with SP3...I dont want to point fingers but I blame Microsoft. :)

0

I am also having these issues accross various HP printers (4050, 2500, etc etc), and I had them prior to SP3, but also have them post (obviously)SP3 install. I have tried the "print direct" option suggested earlier, and I am considering the LPR install. Has anyone else tried this?

0

Getting the same on hp4000, 4050 w2k w/sp3.... FIX IT MICROSOFT

0

I am also having these problems! I have two network JetDirect printers: HP LaserJet 2200 and HP LaserJet 2100. I have an error 61 with LJ 2100 only. But I use SP3 too! The operating system is Windows 2000 Server. Note: After this error job exists for a while, both printers are shutdown because of Print Spooler is going down! After restarting him and turning on/off printers - it's ok! Sometimes helps to turn off/on the printer with manually deleting all print jobs in queue. Microsoft: When you fix this dull problem?

0

Having the same problem with our printers on hp8100, 4050, hpdeskjets, all printers assigned to the printer server w2k w/sp3.... The only thing I have found in common when this happens on our network, a single user that is printing large qty of printouts, same user everytime. Ex. 50 copies of a 35 page document We actually ran out of virt memory today, increased it and hope that helps for awhile but who knows. When the users complain about printouts not coming out, we just restart the print spooler and that clears it up for awhile. But please Microsoft, we need a fix.

0

I have spoken with Microsoft about this error and was told that if the end of the error code in the Event ID 61 is (63), as it is in the example the first user posted, then it is a result of a user canceling a print job. It is really informational and should not be considered an error. Hope this helps those of you with that exact error.

0