Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with W2K3 Server

Status
Not open for further replies.

indyanguy

Programmer
Mar 8, 2004
7
US
Hello all,
The Win2k3 server we are using suddenly becomes so slow that it has to be restarted. When I check the Event Log, I find this entry:

Type Source Event User
Error TermServDevices 1111 N/A

The properties for this entry shows:

<<
Driver Acrobat PDFWriter required for printer Acrobat PDFWriter is unknown. Contact the administrator to install the driver before you log in again.

For more information, see Help and Support Center at >>

There seems to be no help at microsoft.com for this Event ID. It works fine after a restart until this error occurs again. We have a .NET application that is running that converts a document to a PDF document.

Any help is greatly appreciated.
 
Got the Event ID?
11111 isn't a valid ID.


What version of Adobe Acrobat are you using? Do you get the error if you disable the .net app?

Try to narrow it down a bit.

Good Luck,


Steve.
 
FYI, This probably should have been posted in the 2003 forum to get the best audience.

Anyway, I doubt this is the cause of your problem. What you are seeing is most likely due to someone accessing the server via Terminal Services from a Windows XP workstation.

When XP (or any other RDP5 client) connects to a 2K3 TS box, it attempts to redirect the printers locally. So what you are seeing is an attempt for the server to create a printer connection to the Adobe client. Since the server does nto have the drivers installed for this printer, it creates an error. Totally harmless unless you have something strange going on in your environment.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
Which I why I recommended looking into the version you have. The latest (6.01) support TS and works very well when properly configured.

Slowing down of the system probably isn't related to this issue though. Try looking at you CPU usage, and what processes are using the most CPU. Have much RAM have you got?

We need more info! :)

Good Luck,


Steve.
 
Thanks all for your answers. The reason I think that this error is slowing down the system is when I see this error in the Event Log and restart the system, everything works fine till the same error occurs again.

A quick google search suggested that I disable the Windows-Printer setting in the TermServ Config. I have done this and hoping that this error does not occur again. Is installing the drivers on the server going to solve the problem?

I know there is no problem with the .NET app since it was running on a W2K server before we moved it to W2K3 and we had no similar problem in the past.

TIA.
 
Printer redirection wasn't supported in Win2K, so that is one of the main new thigs in 2K3.

Adding the driver will stop it from generating that error. You should be adding the drivers for all the printers that your users will be connecting with. That way A)They will be able to print and B)Your log won't get filled with these messages

As I have seen this exact error on numerous Terminal Servers, I doubt seriously that it is the root cause, however as a troubleshooting process it is a good thing to eliminate from the equation. Please post back and let us know if this does in fact resolve the problem.

Another thing for you to check too would be to see if you have a bunch of users with disconnected sessions. They can really slow down a server if left running in memory for days or weeks.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
Disabling the Windows-Printer option does not seem to be working :( I hope that installing the driver will make it work. Mark, How do I check if I have users with disconnected sessions?

Thank you all for your time.
 
You need to go into Termianl Services Manager and there you will see sessions that are connected, connected & idle & disconnected. Right click the disconnected sessions and choose Logoff.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
We're seeing a similar message, as follows, on one of our servers:

"Driver HP LaserJet 1100 required for printer __PC123_HP LaserJet 1100 is unknown. Contact the administrator to install the driver before you log in again."

The printer the message is referring to is an actual printer on our LAN, but it's not defined at all on the server that is generating this message.

Very strange...
 
FunkMasterWeb, the printer would be configured on a workstation accessing the server via terminal services. (This is a 2003 Server right?)

TS is trying to map the local (client) printer back via terminal services. Adding a dummy lpt printer with that driver will get rid of the errors.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
Hello Mark,

We figured that the Error was not the reason for the Slow down on the W2K3 Server. We moved the application that was causing the error onto a different server but the problem still persists.

Earlier, we were running the same applications on 1.0 .NET Framework (Win 2k Server) and we had no problems. Currently our W2K3 server has the 1.1 .NET Framework installed.

As you suggested earlier, I checked and found no users with disconnected sessions.

Any help is appreciated.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top