From: Ingmar Van Glabbeek on
it started with the following entry in eventlog:

Faulting application wmiprvse.exe, version 5.2.3790.4455, faulting
module ntdll.dll, version 5.2.3790.4455, fault address 0x0001a379.
(every 10 seconds, sometimes making exchange management crash as well)

I followed the instructions on reinstalling wmi, rebuilding the
repository and restoring the repository from the installation disk

as per this link http://windowsxp.mvps.org/repairwmi.htm

Nothing changed and I was still getting the errors in my eventlog every
10 seconds.

Then I ran wmidiag.vbs and changed the permissions of the objects that
were reported to have incorrect permissions.

Now the same crash keep showing in the eventlog (not every 10 seconds
but still frequently) as well as warnings that wmi is run with incorrect
security settings.

Any advice on how to proceed would be appreciated.
From: Russ SBITS.Biz [SBS-MVP] on
Since this could take some time to troubleshoot
and this is not a quick fix.
If you are a partner I'd post to the Microsoft Partner newsgroup.
They can spend the time to help troubleshoot and fix your issue.

Thanks
Russ

--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Small Business Server/Computer Support - www.SBITS.Biz
BPOS - Microsoft Online Services - www.Microsoft-Online-Services.com


"Ingmar Van Glabbeek" <ingmar.vg(a)gmail.com> wrote in message
news:ORpsSa##KHA.3840(a)TK2MSFTNGP02.phx.gbl...
> it started with the following entry in eventlog:
>
> Faulting application wmiprvse.exe, version 5.2.3790.4455, faulting module
> ntdll.dll, version 5.2.3790.4455, fault address 0x0001a379.
> (every 10 seconds, sometimes making exchange management crash as well)
>
> I followed the instructions on reinstalling wmi, rebuilding the repository
> and restoring the repository from the installation disk
>
> as per this link http://windowsxp.mvps.org/repairwmi.htm
>
> Nothing changed and I was still getting the errors in my eventlog every 10
> seconds.
>
> Then I ran wmidiag.vbs and changed the permissions of the objects that
> were reported to have incorrect permissions.
>
> Now the same crash keep showing in the eventlog (not every 10 seconds but
> still frequently) as well as warnings that wmi is run with incorrect
> security settings.
>
> Any advice on how to proceed would be appreciated.

From: Ingmar Van Glabbeek on
Unfortunatly I have no acces to this newsgroup, could you point me in
any other direction for support regarding this issue?

Op 25/05/2010 21:49, Russ SBITS.Biz [SBS-MVP] schreef:
> Microsoft Partner newsgroup

From: Russ SBITS.Biz [SBS-MVP] on
Ingmar,
The only reason I suggest getting some help
is because in my experience WMI issues are like chasing ghosts

You can get lucky in finding it right off the bat
or you can spend hours looking for the fix.

A hit and miss.

You can find a list of Microsoft Independent SBSC Specialists here.
Which Many of them are here on this forum.

(Location won't matter because as long as they have remote access to your
server they can help.)
http://www.microsoft.com/smallbusiness/hub.mspx

Contact Microsoft For Support
http://support.microsoft.com/common/international.aspx?RDPATH=dm;en-us;select&target=assistance

Russ

--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Small Business Server/Computer Support - www.SBITS.Biz
BPOS - Microsoft Online Services - www.Microsoft-Online-Services.com


"Ingmar Van Glabbeek" <ingmar.vg(a)gmail.com> wrote in message
news:#ZnYqNN$KHA.980(a)TK2MSFTNGP04.phx.gbl...
> Unfortunatly I have no acces to this newsgroup, could you point me in any
> other direction for support regarding this issue?
>
> Op 25/05/2010 21:49, Russ SBITS.Biz [SBS-MVP] schreef:
>> Microsoft Partner newsgroup
>
From: Ingmar Van Glabbeek on
Unfortunatly we are not a microsoft certified partner, just a registered
partner and have no acces to that newsgroup.

Any other suggestions?

Op 25/05/2010 21:49, Russ SBITS.Biz [SBS-MVP] schreef:
> Since this could take some time to troubleshoot
> and this is not a quick fix.
> If you are a partner I'd post to the Microsoft Partner newsgroup.
> They can spend the time to help troubleshoot and fix your issue.
>
> Thanks
> Russ
>