Print Spooler Problem With Terminal Services on Win2k Server

By mark.cardono ·
I have new client who, on a daily basis, has to restart his server or spooler because the print spooler hangs/stops. He is running a Win2k Server with Terminal Services(TS) in Application Mode. He has a Mortgage software program, called Point, that the users access through TS. Many of the users are at remote sites and print their work to their local printers. There are some errors and warnings that are recorded in the System event logs (eventid 1111 - print driver unknown, 1106 - printer not installed), that suggest the server cannot load all of the printers the remote user has on his/her computer. Then there are informational events logged, event id 26, "Application popup: pntsupp.exe - DLL Initialization Failed : The application failed to initialize because the window station is shutting down. " and "Application popup: winpoint.exe - Common Language Runtime Debugging Services : Application has generated an exception that could not be handled.

Process id=0x700 (1792), Thread id=0xbf8 (3064).
"The winpoint and pntsupp.exe are part of the Point software package. There are also System events "Document file://C:\WINPOINT\WORK\XXXXX.HTML was corrupted and has been deleted. The associated driver is: XXXXX"
Another System event that ocurrs frequently is event id 6161 - The document LH0612201.PRS owned by nigro failed to print on printer __XXXXXXXX_HP LaserJet 4200 PCL 6/XXXXXX/Session 44. Data type: NT EMF 1.008. Size of the spool file in bytes: 253564. Number of bytes printed: 0. Total number of pages in the document: 7. Number of pages printed: 0. Client machine: \\XXXX. Win32 error code returned by the print processor: 31." This event also records Win32 error codes 995 and 1444. There is also System event 7023 - "The Print Spooler service terminated with the following error:
The access code is invalid. "
In the application log are many event id 1000 - "Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.

DETAIL - Access is denied. , Build number ((2195)). "

The server also has DNS events 414 - "The DNS server machine currently has no DNS domain name. Its DNS name is a single label hostname with no domain (example: "host" rather than "")...... "
The server has Mcafee for anti virus, which throws Security events for each user when they connect and auditing is enabled.
Another program running is Hamachi, some sort of VPN freeware.
I don't know how any of the software was installed. I did install as many of the user's local printers as I could. That seemed to reduce some of the events of unknown printers. I also noticed that there are now TS events that the TS temporary license will expire in X days. I had not seen these events during the first few days I worked on the server. These are event 18 - "Terminal Services Licensing on server TS has not been activated. Terminal Services Licensing will only issue temporary licenses until the server is activated...." and event 26 - "Application popup: Terminal Services Warning : Your terminal services temporary client license will expire in 14 days." The following day, it read "... will expire in 5 days"

Any suggestions will be helpful.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Related Discussions

Related Forums