D
Da Print Guy
We are using a W2K server as our print server running InfoPrint Manger
and EasySpooler as our delivery/manager software. Occasionally, the
server will hang. All connections to it fail except for very low
level pings. RDC fails as does direct connection. The only thing we
can do is reboot and in the middle of the night, this can be ugly
since batch print is happening at this time.
There is nothing in the event log. There is nothing in any of the
application logs and there are no hardware errors that I can see.
Is there some way to tweak the server so that it spits out even more
robust logging? I have our NT group looking at the issue, but they
are having as much (or as little)luck as I am trying to figure out
what happenened.
and EasySpooler as our delivery/manager software. Occasionally, the
server will hang. All connections to it fail except for very low
level pings. RDC fails as does direct connection. The only thing we
can do is reboot and in the middle of the night, this can be ugly
since batch print is happening at this time.
There is nothing in the event log. There is nothing in any of the
application logs and there are no hardware errors that I can see.
Is there some way to tweak the server so that it spits out even more
robust logging? I have our NT group looking at the issue, but they
are having as much (or as little)luck as I am trying to figure out
what happenened.