RE: Mad monitoring error 9099

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,


Thank you for posting back!

Currently, I suggest you perform following action plans:

1. Reinstall Monitoring features on your Small Business Server.
To do so:
a. Locate Server Management----Monitoring and Reporting.
b. In the right pane, click Setup Monitoring Reports and Alerts.
c. And follow the wizard to reinstall monitoring features.

2. I would suggest you t try the solution in the following article to
re-register the Exchange 2003 Server namespace with WMI to see if we can
fix the problem.

Error "0x8004100e" and event ID 9097 occur when you run the System Attendant
http://support.microsoft.com/default.aspx?scid=KB;EN-US;288590

Note: Although you may not get the 9097 error, the above KB article can
still be applied because re-registering the Exchange 2003 Server namespace
with WMI usually will fix such kind of errors due to WMI problem.

If the problem still persists after trying the above method, I still
suggest you try the steps in the KB article 326011:

XADM: System Attendant Generates Event ID 9098 And 9099 Messages Every Five
Minutes
http://support.microsoft.com/default.aspx?scid=KB;EN-US;326011

3, Please make sure that you installed the Exchange 2003 latest service
pack:

836993 How to obtain the latest service packs for Exchange Server 2003
http://support.microsoft.com/?id=836993

Best Regards,

Chace Zhang (MSFT)

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: Mad monitoring error 9099
| thread-index: Aca1FXbQ8fcgciqSRleuK7MhBSmBAw==
| X-WBNR-Posting-Host: 68.37.3.206
| From: =?Utf-8?B?Z3V5Zw==?= <guyg@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <05135DED-F6C0-4FC2-9165-EA143521D7FA@xxxxxxxxxxxxx>
<Hu$bB4znGHA.5892@xxxxxxxxxxxxxxxxxxxxx>
<E95D4D91-EC90-4524-B082-2B9E951BB6C9@xxxxxxxxxxxxx>
<f1tBRZ8rGHA.5976@xxxxxxxxxxxxxxxxxxxxx>
<ED8F5691-5AAE-4B36-A629-32EF354B7F20@xxxxxxxxxxxxx>
<AaQfcDJtGHA.2504@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: Mad monitoring error 9099
| Date: Mon, 31 Jul 2006 19:52:01 -0700
| Lines: 315
| Message-ID: <F7FEBE18-B596-4344-AEBE-86C32ADE63FF@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: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:285935
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| followed all instructions so far except 2. I do not have a good copy of
| system state and i did not do the Q326011 instructions yet. I have to go
to
| the server site.
| Also found that the dependencies for event log service has no "The
following
| system components depend on this service". I compared this with a good
| working server and found that this area has a list of services in it.
Also if
| i go to the WMI control properties-security tab I found that
Microsoftllsv2
| is missing ms_409 and also is perfmon and WMI. When I follow the
instructions
| for Q326011 it ask to run exchange setup at the end. Will this erase or
over
| write e-mails on the server?
| Thanks,
| Guy
|
| "chace zhang" wrote:
|
| > Hi,
| >
| > Thank you for your update.
| >
| > This issue occurs because the monitoring thread that is run by the
System
| > Attendant service (Mad.exe) cannot query Microsoft Windows Management
| > Instrumentation (WMI) for the state of any of the following items:
| >
| > - Cluster resources
| > - CPU usage information
| > - Instances of the ExchangeLink class or other classes provided by the
| > Exchange WMI provider (Exwmi.dll)
| >
| > In order to further research, please gather application log to me:
| > v-chacez@xxxxxxxxxxxxx
| >
| > Here, I would like to provide you following action plan:
| > Action 1
| > I suggest you restore your server,(if you had backup your system
state).
| >
| > Action 2
| > Also please apply Exchange Service Pack 2 again.
| >
| >
| > Action 3
| >
| > 1. Click Start, click Run, type "DCOMCNFG" and press ENTER. Expand
| > Component Services -> Computers, right-click My Computer and click
| > Properties. On the Default Properties tab, check "Enable Distributed
COM on
| > this computer" (By default this is usually checked.). Make sure
"Default
| > authentication level" is set to "Connect" and "Default Impersonation
Level"
| > is set to "Impersonate".
| >
| > 2. Ensure that Cdowfevt.dll is version 6.5.6944.0 or higher.
| >
| > 3. Run the following command:
| >
| > regsvr32 "D:\Program Files\Exchsrvr\bin\cdowfevt.dll".
| >
| > 4. Put the SBS installation CD #2 into the CD-ROM, recompile the 4 MOF
| > files for exchange using the following syntax, where <cd-rom> is the
drive
| > letter of the CD-ROM drive:
| >
| > mofcomp -N:root\cmiv2\applications\exchange
| > <cd-rom>:\EXCHSRVR65\setup\i386\exchange\exwmi.mof
| > mofcomp -N:root\cmiv2\applications\exchange
| > <cd-rom>:\EXCHSRVR65\setup\i386\exchange\exmgmt.mof
| > mofcomp -N:root\cmiv2\applications\exchange wbemcons.mof
| > mofcomp -N:root\cmiv2\applications\exchange smtpcons.mof
| >
| > If these fail, copy these from another working system and paste them
into
| > the %SystemRoot%\system32\wbem folder.
| >
| > 5. If you continue getting the error, view the folder structure with
the
| > management tool. To do so:
| >
| > A. Click Start, click Run, type "compmgmt.msc" and press ENTER.
| > B. Expand the "Services and Applications".
| > C. Click once on the "WMI Control" Icon and then right-click the WMI
| > Control and click "Properties".
| > D. On the "Security tab" expand the "Root".
| > E. compare the folder structure to that of your own system. Check for
| > missing folders. These are created by the .mof files.
| > F. If folders are missing check the mof files above by opening them
with
| > NotePad. If they are empty copy new mof files from a working system and
| > recompile them.
| >
| > 6. Perform the procedures outlined in Q326011:
| >
| > 326011 XADM: System Attendant Generates Event ID 9098 And 9099 Messages
| > Every Five Minutes
| > http://support.microsoft.com/?id=326011
| >
| >
| >
| > Hope this helps.
| >
| >
| > Please feel free to let me know the result. I look forward to your
update.
| >
| > Best Regards,
| >
| > Chace Zhang (MSFT)
| >
| > 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: Mad monitoring error 9099
| > | thread-index: AcazKiUsmP5jfKXkR9GjrN5WAZJg3Q==
| > | X-WBNR-Posting-Host: 68.37.3.206
| > | From: =?Utf-8?B?Z3V5Zw==?= <guyg@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | References: <05135DED-F6C0-4FC2-9165-EA143521D7FA@xxxxxxxxxxxxx>
| > <Hu$bB4znGHA.5892@xxxxxxxxxxxxxxxxxxxxx>
| > <E95D4D91-EC90-4524-B082-2B9E951BB6C9@xxxxxxxxxxxxx>
| > <f1tBRZ8rGHA.5976@xxxxxxxxxxxxxxxxxxxxx>
| > | Subject: RE: Mad monitoring error 9099
| > | Date: Sat, 29 Jul 2006 09:15:02 -0700
| > | Lines: 319
| > | Message-ID: <ED8F5691-5AAE-4B36-A629-32EF354B7F20@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: TK2MSFTNGXA01.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:285313
| > | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | I have found some logs and events.I will send them to you via the
e-mail
| > | address you sent me. Also when I open health monitor and tree down to
| > | Microsoft Exchange
| > | system attendant properties and click on details tab and then the
browse
| > | button it
| > | shows "\\severname\root\cimv2 and in the name window below it is
empty. I
| > | compared this to a good working SBS2003 server and found a lot of
stuff
| > in
| > | this area. Also when I click on servername under health monitor it
| > collects
| > | data and
| > | displays all alerts and status. Compared to good working server this
list
| > is
| > | small and
| > | incomplete. Maybe a reinstall of the monitoring tools from setup
disk
| > could
| > | fix this?
| > | How much of a problem is these errors doing to exchange?
| > | Thank you,
| > | Guy
| > |
| > | "chace zhang" wrote:
| > |
| > | > Hi,
| > | >
| > | > Thanks for your reply.
| > | >
| > | > According to your situation, you may also try to run the following
| > command
| > | > on the system in question to check the system files:
| > | >
| > | > SFC /Scannow
| > | >
| > | > Note: You may need the Windows installation CD-ROM if the Scan
utility
| > | > cannot find the system files that are required.
| > | >
| > | > For more information about SFC, you may refer to the following
| > Microsoft
| > | > Web site:
| > | >
| > | > Description of Windows XP and Windows Server 2003 System File
Checker
| > | > (Sfc.exe)
| > | > http://support.microsoft.com/kb/310747
| > | >
| > | > Hope this helps! Please try the suggestions above and let me know
the
| > | > results. I look forward to hearing from you soon.
| > | >
| > | > Have a nice day!
| > | >
| > | > Best Regards,
| > | >
| > | > Chace Zhang (MSFT)
| > | >
| > | > 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: Mad monitoring error 9099
| > | > | thread-index: AcavchmpMSWwnaM+QaKWh/Vjlgzm5Q==
| > | > | X-WBNR-Posting-Host: 68.37.3.206
| > | > | From: =?Utf-8?B?Z3V5Zw==?= <guyg@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | > | References: <05135DED-F6C0-4FC2-9165-EA143521D7FA@xxxxxxxxxxxxx>
| > | > <Hu$bB4znGHA.5892@xxxxxxxxxxxxxxxxxxxxx>
| > | > | Subject: RE: Mad monitoring error 9099
| > | > | Date: Mon, 24 Jul 2006 15:40:02 -0700
| > | > | Lines: 225
| > | > | Message-ID: <E95D4D91-EC90-4524-B082-2B9E951BB6C9@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: TK2MSFTNGXA01.phx.gbl
| > | > | Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.sbs:283847
| > | > | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > | > |
| > | > | followed the instrauctions. The error is still present and also
| > getting
| > | > an
| > | > | error for SBS backup failed. I do not have this configured to
run.
| > Not
| > | > sure
| > | > | what is happenig to the server. All started after it rebooted
three
| > times
| > | > | during a storm.I will try to give you more info about errors
latrer.
| > | > | Thanks
| > | > |
| > | > | "chace zhang" wrote:
| > | > |
| > | > | > Hi,
| > | > | >
| > | > | > Thank you for posting here.
| > | > | >
| > | > | > According to your description, I understand the error event
9099
| > occur
| > | > | > frequently (every five minutes). This issue may occur if the
| > Microsoft
| > | > | > Exchange System Attendant was unable to query Window Management
| > | > | > Instrumentation (WMI) for instances of Win32_Service class.
This
| > class
| > | > is
| > | > | > provided by the standard Win32 provider shipped with Windows
| > 2000/2003.
| > | > The
| > | > | > Monitoring thread will recover from these errors if they are
| > isolated.
| > | > | >
| > | > | > Based on my experience, the errors may be caused by one of the
| > | > following
| > | > | > underlying issues:
| > | > | >
|

.

Quantcast