RE: Exchange System Manager and WMI

Hi Jenny, thank you that fixed the tracking problem.

Cheers

""Jenny wu [MSFT]"" wrote:

Hi Ciel,

Thanks for using the SBS newsgroup.

From your description, I understand the issue to be: you received this
error message "ID no: 8004100e, Exchange System Manager", when you are
using the Message Tracking Center. If I am off base, please don't hesitate
to let me know.

The error code 8004100e translates to WBEM_E_INVALID_NAMESPACE, which means
the failure is due to an invalid namespace.

To resolve this issue, we will need to attempt registration of the
necessary DLLs and to import the Exchange Namespaces and Classes. Running
the below commands will harm nothing if the DLLs are already registered or
if the Namespaces and/or Classes are already present in the WMI Repository.

1. Run the following command from a command prompt in the Program
Files\Exchsrvr\Bin directory:

regsvr32 /s exwmi.dll
regsvr32 /s cdowf.dll
regsvr32 /s cdowfevt.dll

2. Run the following commands from a command prompt in the
Windows\System32\Wbem directory:

mofcomp.exe -class:forceupdate C:\WINDOWS\system32\WBEM\exmgmt.mof
mofcomp.exe C:\WINDOWS\system32\WBEM\exwmi.mof
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\wbemcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\smtpcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\msgtrk.mof"

3. Restart the Windows Management Instrumentation service and all related
services.

If the issue still persists, that files in the
%SystemRoot%\System32\Wbem\Repository folder may get corrupted. Let's
perform these steps:

1. Click Start, and then right-click My Computer.

2. On the shortcut menu, click Manage.

3. In the left pane of the Computer Management console, double-click
"Services and Applications".

4. Under "Services and Applications", click Services.

5. In the right pane of the Computer Management console, locate and then
right-click Windows Management Instrumentation.

6. On the shortcut menu, click Stop.

7. Start Windows Explorer, and then locate the
%SystemRoot%\System32\Wbem\Repository folder.

8. Copy %SystemRoot%\System32\wbem\Repository to a different folder and
then delete all of the files in the %SystemRoot%\System32\Wbem\Repository
folder.

9. Register all DLLS in %SystemRoot%\System32\wbem. To do so, run the
following commands:

cd C:\WINDOWS\system32\wbem
for /f %s in ('dir /b *.dll') do regsvr32 /s %s

10. Restart the computer. The files that were deleted are re-created when
the computer restarts as the Windows Management Instrumentation service
starts automatically when you restart the computer.

Hope above information helps! I am happy to be of assistance to you and
look forward to your reply.

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
Thread-Topic: Exchange System Manager and WMI
thread-index: AcZCPo8M9Mp7pLdISt2pQfGIyOVA1Q==
X-WBNR-Posting-Host: 207.37.89.65
From: =?Utf-8?B?Q2llbA==?= <Ciel@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Exchange System Manager and WMI
Date: Tue, 7 Mar 2006 15:26:28 -0800
Lines: 20
Message-ID: <EB8E4A55-70AF-4DDA-92A7-B5EB0579C5BB@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.windows.server.sbs:250397
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs

I have a problem on a SBS 2003 SP1 system related to the WMI. The initial
symptom was the following error message when attemting to use the Track
Mail
tool in Exchange System Manager "Exchange System Manager - An error
occurred
during a call to Windows Management Instumentation ID No:80041004"

The logs showed that there was a corruption in the \wbem\Respository. To
resolve this I disabled WMI and deleted the fiiles in the Repository
directory then restarted WMI.

Now the error message reads "Exchange System Manager - An error occurred
during a call to Windows Management Instumentation ID No:8004100e"

I have followed the instructions in Microsoft Artile ID 288590 and the
mofcomp.exe commands complete successfully. However the 8004100e error
reamins and I cannot track the email messages.

The wbemprox.log has the following entries:
(Wed Mar 08 08:51:56 2006.339775515) : NTLMLogin resulted in hr =
0x8004100e

Any suggestions on how to resolve this?



.

Relevant Pages

  • Re: Unable to download files from the Internet. Please advice.
    ... This will establish an HTTP connection to the ... server is now waiting for further commands, ... then I'm expecting to see an error message and/or code instead. ... Jim ...
    (microsoft.public.windowsxp.security_admin)
  • Re: [opensuse] kdm + resmgr problem in login
    ... As I was clean of one error message and without new ones, ... how could It work, if I overwrite all files with ... To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx ... For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx ...
    (SuSE)
  • Re: Boot failure after update
    ... >> error message. ... Type in the following commands. ... assumption that you are booting into either Gnome or KDE. ... or install CD #1 by booting into rescue mode. ...
    (Fedora)
  • Re: Error!
    ... time as I received the error message I was able to send e-mails without any ... This is a known issue with Entourage where it, by default, attempts to send ... set of commands to the mail server simultaneously, ...
    (microsoft.public.mac.office.entourage)
  • Re: Startup error in gkrellm
    ... > commands seemed to work on the date or timestamp of some files or links. ... > error message about times has gone. ... > doing incremental backups with backerupper, ... You definitely want an USB 2/firewire hd. ...
    (comp.os.linux.setup)
Loading