RE: WMI Hell
- From: "David Davis" <DavidDavis@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 16 Jun 2005 07:55:06 -0700
If this box is going to be a production Exchange box then I highly recomend
that you roll back the driver and contact the hardware vendor for a new
driver. You do not want these types of issues on your exchange box. If there
is no new driver, then you will seriously want to consider upgrading the
hardware. Once you remove the problem driver, go ahead and re-install
exchange. This should fix any other problems that may be lurking.
Hope this helps
--
David Davis, MCSE, CCNA, Security +
Network Engineer
"the friendly display name" wrote:
> Hello, I run a windows 2003 SBS Server (sp1). Recently I have installed a
> driver that was for win2000, not 2003, (2003 driver wasn't available) and
> well...
>
> The driver and the hardware for that the driver was written are working, but
> the OS has problems now. After the reboot, I got a message, that a driver or
> a service didn't start. After I have inspected the eventlog, it seemed that a
> Exchange service didn't start propery. If I try to inspect that service in
> the Admin Tools program, I am getting the message, that the service isn't
> registered. The same thing with a IIS service. After I have re-installed IIS,
> it works now, but the Exchange is still broken. Note, that exchange isn't
> used the in the network yet but it will soon, so the problem must be resolved.
>
> Further investigations in the eventlog about the exchange service showed me,
> that it got blocked by wmiprvse, and that I need to change the access
> restriction of wmiprvse in the component service program. I played with those
> setting, but the problem is still there.
>
>
> Any advices?
.
- References:
- WMI Hell
- From: the friendly display name
- WMI Hell
- Prev by Date: RE: Partition Magic-Moved Post
- Next by Date: Re: Secure File Sharing
- Previous by thread: WMI Hell
- Next by thread: Partition Magic-Moved Post
- Index(es):
Relevant Pages
|
