directing network printer errormessage

[John Smith]

I have added a network printer to my network, and all clients (w2k/XP) can
use them just fine. Only problem is that when I have a error-situation
(paperjam, out of paper etc), the error message displays on the physical
monitor of the print server. Now, this is a machine i dont wamt to have a
monitor conneted to, as it is a server. Is there a way to redirect the
messagebox with the "retry" button anywhere else? Can I get it perhaps to
the printer client or to a remote desktop session, instead of just misplaced
above the w2k-login window on the physical connected monitor? Does the
server os WXPpro/W2kpro/W2kserver make a difference?

john

 

[Brian Oakes [MSFT]]

Thanks for the question, and what a good question is it. I spoke to some
folks in support and the answer I got was unfortunately no. Most of those
messages are just popup's using the messenger service. So unfortunately they
will continue to log to the console. But... if they create an event log,
there are plenty of tools to monitor the events logs and then perform an
action based on what you specify. That would be the best direction to
look, but we are assuming that the print driver will log to the event log
which most won't from what I am told.
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.

 

[John Smith]

Thanks so much for the answer, even though this doesnt help me very much. in
the actual situation

The only follow up question I have, is whether, when this e.g. paperjam
situation raises, I have any sensible action to perform unless I am at
console, to make the printer work again (assume the monitor and server
physiacally is located in a locked up basement i Texas, and I am remotely
administering it from Hawaii) (okay, someone have to refill paper, but
assume they dont have privileges to touch the computer stuff).

Now I've already tried som stunts that wont work (after paper have been
added to printer:
* the client deletes the print job (job never goes away)
* remote desktop logged on admin deletes the job (job never goes away)
* restarting the print service after the each of the 2 above (still jam)
* powering off the printer and restarting is after each of the 2 top
bullets. (still jam)

The only solution (workaround) I have found is to
* (remotely of physically) reboot the machine, which has is consequences in
addition to require me to add a keyboard to the machine (or the BIOS will
hang). Now this all break my illusion of a monitor/keyboard less server, but
the keyboard would perhaps eventually emerge at the first powerout anyway...

Thanks nonetheless.

-John

 

[Brian Oakes [MSFT]]

Hopefully one of the apps guys (printer support folks) is watching the
groups and can add some value.
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.