Exchange Server

jj · Guest

pardon my repost, but we still haven't been able to fix this ... and no one
replied before:

On Exchange 2003, we are having problems with the logs and with Directory
Access.
On the General Tab of the server properties we see this error in the Log
file directory field:

An error occurred during a call to Windows Management Instrumentation
ID no: 80041013
Exchange System Manager

Under the Directory Access tab we get a pop up that says "Information about
Directory Sevices could not be entirely obtained. Check to see that the
Microsoft Exchange Management service is running on the Exchange 2000 or
Exchange Server 2003 server"

It is running. Also, we are getting logging errors (no logs!)

your assistance is appreciated!

jj

It is running

Kirill Palagin · Guest

Does that apply
http://support.microsoft.com/default.aspx?scid=kb;en-us;841481

Ben Winzenz [Exchange MVP · Guest

I'd try restarting the Windows Management Instrumentation service along with
the Exchange Management service. This clearly sounds like a WMI issue.
http://support.microsoft.com/default.aspx?scid=kb;en-us;295821 indicates
that the error you get is
WBEM_E_PROVIDER_LOAD_FAILURE 0x80041013

Has this always been an issue or did it just start happening? Any 3rd party
software installed (specifically Doubletake?)
http://support.microsoft.com/default.aspx?scid=kb;en-us;841481

You might check some of the things from this KB article (may or may not
apply)
http://support.microsoft.com/default.aspx?scid=kb;en-us;288590

I'd also check the Group Policy and/or Local Security Policy that is applied
to your Exchange server for the following:
http://www.webservertalk.com/message167362.html

You could also try enabling debug logging on WMI (wmimgmt.msc), but I'm not
sure how easy it will be to interpret the information, plus you have to make
sure that you turn logging off, otherwise the debug logs will eat up disk
space.

--
Ben Winzenz
Exchange MVP
MessageOne

jj · Guest

There are no third party apps other than a backup utility (Veritas)
connector. We also use IMF, from MS.

We also do not use clustering and this is a single server.

I verified that the persmissions on the .log files were set for read access,
they are.

This just started happening in the last two weeks or so, but we haven't made
any changes to the system as far as I can tell ...

ack!

Kirill Palagin · Guest

Well I am stumped. See if reboot will help. Also try
Link

ryanxie · Joined: 09 Nov 2006 Posts: 1

JJ (or anybody else),

Did you manage to get a solution for your problem? I have a distributed exchange environment, with 2 Front-end-servers (at 2 separate locations) and up to 15 back-end-servers.

The problem ("An error occurred during a call to Windows Management Instrumentation ID no: 80041013 Exchange System Manager" on the general tab of both my front-end-servers ONLY; back-end servers have no such problem) started occuring after Exchange SP2 installation (and activation of RPC-over-HTTP feature, if that matters). before that, no such error was found.

Even witht this error, my mail delivery doesn't seem to get affected. What's affected are:
1. i can't track message because the message tracking on front-end is malfunctioning due to the above error.
2. i can't push any patches/updates to my front-end-servers because the $IPC shares on my front-end-servers appear to be lost.

I've ensured "Local Service" and "Service" accounts are among the accounts enabled for "Impersonate after logon" user-rights on my front-end-servers. The restrictanonymous (HKLM\System\CurrenctControlSet\Control\LSA) is set to 0 or disabled on my DCs and front-ends.

Everytime, however, when the front-end is rebooted, the problem will go away, BUT it will return after some period of time (approximately an hour or so).

Please help!!

	Exchange Server Forum Index -> Administration	All times are GMT
Page 1 of 1