faulting applications and disconnections

[Guest]

I have 6 remote sights logging into TS, with about 40 users (palns are for
100). Just lately things were going okay until TS started getting the
following errors
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 1/20/2005
Time: 4:24:15 PM
User: N/A
Computer:
Description:
Faulting application spoolsv.exe, version 5.2.3790.0, faulting module
unknown, version 0.0.0.0, fault address 0x00000000.

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 1/20/2005
Time: 4:42:34 PM
User: N/A
Computer:
Description:
Faulting application mgrntw.exe, version 0.0.0.0, faulting module
mgrntw.exe, version 0.0.0.0, fault address 0x001ec10c.

When users get the spoolsv error they are disconnected, this is happening on
a regular basis. I must not forget that the users are accessing a SQL DB over
TS.
The other problem is that all users can see everyone elses printers and this
is problematic as a Large print job was redirected today to a printer at
another sight.
If anyone can help it would be very much appreciated.

Thanks

 

[Vera Noest [MVP]]

Seems that you have a couple of problems:

a) all users see all printers.
This most likely means that your users have Administrator rights,
since normal users can only see their own printers. If that's the
case, your are in for much worse problems than a crashing spooler.

b) your printer spooler is crashing.
A crashing printer spooler on a Terminal Server is nearly always a
sign that you are using a 3th party printer driver which is not TS-
compatible.
The remedy is to uninstall all 3th party printer drivers and map
all printers that don't autocreate to a native printer driver on
the server, by creating a custom ntprintsubs.inf file.
Details are explained here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

You can check the recommended native driver substitution for your
local printers here:

Client Printer Autocreation Matrix
http://www.printingsupport.com/matrix.htm

 

[Guest]

They are regular users and do not have administrative rights. As for the
print drivers I used the Microsoft Wizard to add them

 

[Vera Noest [MVP]]

OK, I've done some searching with Google for mgrntw.exe (the
faulting application), and that seems to be a part of
MagicSoftware.
There are numerous reports on their own forum that this software
causes crashes, so I would get rid of it asap.
http://www.magicsoftware.com/bin/en.jsp?
enPage=InnerPage&enDisplay=view&enDispWhat=Zone&enDispWho=forums_ge
neral&enZone=forums_general

About the printer driver: the important part is not *how* you
installed it, but if the driver was found on the native driver
list. If it was, OK, it's supported. If you had to click "Select
driver...Have disk" and then point to the manufacturers driver,
it's probably not. What printer model and driver is this?

About all users seeing all printers: this is in principle only
possible when the users are Administrators or Power Users.
The only exceptions that I know of are Excel 2000 and Excel 2002:

297883 - XL2000: You Can See Other Users' Printers in a Terminal
Server Session
http://support.microsoft.com/?kbid=297883

313683 - XL2002: Can See Other Users' Printers in Terminal Server
Session
http://support.microsoft.com/?kbid=313683

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---