Exchange restart kills mouse

[goal]

Hi,

We have several machines within the company that when MS Exchange is stopped and started, it kills the mouse totally. Everything works ok via keyboard, but still the mouse is dead. We can't find any way of restarting the mouse without rebooting the system, which obviously inconvenient. Does anyone else have experience of this - is there a fix? Any help appreciated...

INFO : NT4 SP6a Exchange 5.5

Thanks,
Andy.

 

[pbxman]

I haven't experienced it, but what services exactly are you stopping/starting to cause it?

 

[goal]

We are restarting all exchange services. As this is a live system I've been unable to test stopping/starting individual services.

 

[pbxman]

Are you using MS Intellimouse? Check the Event Log as well - sounds like your i8042 port may be stopping as well.

Also - try a serial mouse instead of PS/2 if you can, and see what that does.

 

[goal]

The machine I have experience of is PS/2, however other machines that this happens on have serial mice, so I don't think this has a lot to do with it (they are also different hardware, from Compaq to HP to others).

Sadly there's nothing in the EventLog to help - as this was my first port (no pun intended) of call when I first knew about the problem.

It's a standard PS/2 mouse, as supplied by the hardware vendor, in this case HP (other mice have been tried).

Thanks again,
Andy.

 

[goal]

anyone else have any experience of this, it's extremely frustrating.

Thanks,
Andy.

 

[Mubashir]

Is there anything worthwhile in system log?

Are you sure it's because of exchange services? Actually I've encountered a few problems where mouse, more appropriately cursor disappeared from screen. Investigation revealed incorrect screen resolution and colors. May be that kind of thing is happening there...

If there's nothing in logs, experiment with display settings of any idle server, since you've more than one server with this prob. Booting in VGA mode and start/stop services might also help here.

 

[goal]

Thanks for your suggestions, but unfortunatly we know its certainly exchange, it's been happening for some time and it only ever happens when exchange is stopped and started.

Like I said, all the machines already have different hardware and software setups (screen res etc) so we have ruled out anything like that really.

Can anyone help any further?

Thanks,
Andy.