Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 281
  • Last Modified:

WMI Service Error??

Exchange 2003 SP2 on a WIN2k3 SP1 box.

Exchange_Server has reported a Error.  Reported status is:
Queues - Unknown
Drives - Unknown
Services - Error
Memory - Unknown
CPU - Unknown

I had an issue awhile back with disk space and database size, so I adjusted many diagnostic logging levels.  I am sure this is releated to this, but how do I know which service is experiencing the error?

Also, Is there a 'template' or guidlines I can follow to set my diag logging levels so that they will only log issues I need to be concerned with?

-Darren
0
darrennelson
Asked:
darrennelson
  • 3
  • 3
1 Solution
 
darrennelsonAuthor Commented:
also, the email notification came at 11:34PM.  I checked my logs and there wasn't anything obvious in the sys or app log at or around those times.
0
 
rstovallCommented:
Sounds like local machine access problem for WMI?

This could likely be resolved through using DCOMCNFG .. and verify that WMI has all necessary permissions

Also, if you added drives ot the system, (due to disk space issues)  .. verify that system has full control in NTFS perms...

appears to be more access/security related than a setting . .let me know what you find in DCOM (sometines I have removed and re-added perms in DCOMCNFG to resolve access issues)
0
 
darrennelsonAuthor Commented:
rst,

I'm not familiar with DCOMCNFG.  I'm in it now, and navigated to Component Services->Comuters->My Computer->DCOM Config->Windows Management and Instrumentation->Properties->Security.  Here I have 'Launch and Activation Permissions' set to customize - if I edit, the group 'Everyone' has full access - no other groups or users present.  Under "Access Permissions", its set to "Use Default".  Under "Configuration Permissions", once again "Customize" is selected and if I edit, local admins and SYSTEM have full access, various other users have different degrees of access.

Am I in the right place?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
rstovallCommented:
Perfect .. remove system and readd it to have full permissions ...

Also, verify that system has access to all newly added drives .. especially if you have moved a store or log files over there!!

I wouldn't worry about other users, unless you have something running as a service account, etc ..

Let me know if that resolves the problem .. kind of a long shot, with my knowledge of WMI .. but it sure sounds like this kind of access problem
0
 
darrennelsonAuthor Commented:
I have removed and readded SYSTEM and will continue to monitor.  No additional disks to worry about at this time, although were are getting close to that point.

On the subject of monitoring, is there a default Diagnostic Logging level in Exchange that I can set all my events to log at?  Or is it just tinkering with what you need logged?

-Darren
0
 
rstovallCommented:
there is no blanket solution for this monitoring ..

"tinkering" with what you need when you need it is usually the way to go ..

There are some ways to get even more verbose logging if you should ever need it .. you can add loglevel in the registry up to 7 I believe

this may be of some use to you
http://www.computerperformance.co.uk/exchange2003/exchange2003_logs_diagnostic.htm
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now