Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Event ID: 9098 MSExchangeSA

Network Sharing , TCP/IP, Internet, Wireless, Exchange, IIS, ISA and Print

Event ID: 9098 MSExchangeSA

Postby guest » Tue Mar 18, 2008 1:12 pm

Please understand that this issue is related to WMI. I suggest you perform
the following steps to troubleshoot the issue:

Step 1: Check the WMI service
===========================
a. Log on to the computer that is running Exchange 2003 by using an account
that has administrative permissions.
b. Click Start, click Run, type wmimgmt.msc in the Open box, and then click
OK.
c. In the WMI snap-in, right-click WMI Control (Local), and then click
Properties.
d. If the WMI service is configured correctly, the WMI Control (Local)
Properties dialog box is displayed. When you click the General tab, the
operating system version and the WMI version information are displayed.

If the WMI Control (Local) Properties dialog box is not displayed, you must
contact the Platforms Performance team.

Step 2: Check the WMI security settings
=================================
a. In the WMI snap-in, click the Security tab.
b. Expand Root, click MicrosoftExchangeV2, and then click Security.
c. Make sure that the inherited permissions resemble the following
permissions, and then click OK:

- Administrators
- Full permissions

- Everyone
- Execute method
- Provider Write
- Enable account

- Local Service
- Execute method
- Provider Write
- Enable account

- Network Service
- Execute method
- Provider Write
- Enable account


d. Expand CIMV2, expand Applications, click Exchange, and then click
Security.
e. Make sure that the inherited permissions resemble the following
permissions, and then click OK:

- Administrators
- Full permissions

- Everyone
- Execute method
- Provider Write
- Enable account

- Local Service
- Execute method
- Provider Write
- Enable account

- Network Service
- Execute method
- Provider Write
- Enable account

f. Use Windows Explorer to locate and to right-click the
WINNT\SYSTEM32\WBEM folder, and then click Properties.
g. In the wbem Properties dialog box, click the Security tab.
h. Make sure that the permissions resemble the following permissions, and
then click OK: o Administrators o Full Control

- Creator Owner
- Special Permissions

- Authenticated Users
- Read & Execute
- List Folder Contents
- Read

- System
- Full control


Step 3: Use Wbemtest.exe to check classes and namespaces
=================================================
a. Click Start, click Run, type wbemtest in the Open box, and then click
OK.
b. In the Windows Management Instrumentation Tester dialog box, click
Connect.
c. In the Namespace field, type root\cimv2\applications\exchange , and then
click Connect.

Note: To test a remote computer, type the following path in the Namespace
field:

\\ ServerName \cimv2\applications\exchange

In this path, ServerName is the name of the computer to which you want to
connect.

d. Click Enum Classes. Do not enter a superclass name. Select the Recursive
option, and then click OK.
e. In the Query Result page, there should be 59 objects for a computer that
is running Microsoft Exchange Server 2003 Service Pack 1 (SP1). There
should be 57 objects for a computer that is running Microsoft Exchange 2000
Server Service Pack 3 (SP3) with the latest service pack installed.

Compare these values with the values from another server that is correctly
running the same version of Exchange 2003 with the same service packs.
These values should be the same.

f. Click Close.
g. In the Windows Management Instrumentation Tester dialog box, click
Connect.
h. In the Namespace field, type root\microsoftExchangeV2 , and then click
Connect.
i. Click Enum Classes. Do not enter a superclass name. Select the Recursive
option, and then click OK.
j. In the Query Result page, there should be 74 objects for a computer that
is running Exchange 2003 SP1. There should be 52 objects for a computer
that is running Exchange 2000 SP3 that has the latest service pack
installed.

Compare these values with the values from another server that is correctly
running the same version of Exchange 2003 with the same service packs.
These values should be the same.

k. Click Close.
l. Click Enum Instances.
m. Enter the class name that you want to enumerate, such as Exchange_Server
or Exchange_DSAccessDC , and then click OK.

The class name depends on the issue that you want to troubleshoot or to
test. You can access the class names in steps 3i and 3j.

Step 4: Register the Exchange 2003 WMI .dll files, the WMI namespaces, and
the WMI classes
==========================================================================
You might use an invalid WMI namespace or an invalid WMI class error
message when you check the WMI security settings in step 2. Alternatively,
you might use an invalid WMI namespace or an invalid WMI class error
message when you use Wbemtest.exe to check the WMI classes and the WMI
namespaces in step 3.

If this occurs, you must register the required Exchange 2003 .dll files,
and then import the Exchange 2003 namespaces and classes to the WMI
repository. To do this, follow these steps:

a. Click Start, click Run, type cmd in the Open box, and then click OK.
b. Change to the Exchsrvr\Bin directory.
c. At the command prompt, type the following commands. Press ENTER after
each command.

exmgmt.exe /uninstall
exmgmt.exe /install
regsvr32 /s exwmi.dll
regsvr32 /s cdowf.dll
regsvr32 /s cdowfevt.dll

d. Change to the Windows\System32\Wbem directory.
e. At the command prompt, type the following commands. Press ENTER after
each command.

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:
\winnt\system32\wbem\msgtrk.mof

Note: The Msgtrk.mof file is included only in Exchange 2003 and in later
versions of Exchange Server. This file is not included in Microsoft
Exchange 2000 Server.

f. Click Start, click Run, type services.msc in the Open box, and then
click OK.
g. In the Services snap-in, right-click Windows Management Instrumentation,
and then click Restart.

After that, please verify whether the issue still occurs.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Return to Networking

Your Ad Here

Who is online

Users browsing this forum: No registered users and 4 guests