Hi All, Not able to Reset Health in Health Explorer, Showing Calculating the Health State of the following monitor and gets hang and it wont respond also.MNYash

Can you provide the version of OpsMgr? Service Pack 1? R2?http://OpsMgr.ru/

Hi, SCOM 2007 R2 MNYash

Do you see an errors or warnings in Operations Manager eventlog on your root management server?http://OpsMgr.ru/

If it hangs I would suggest you might have some kind of issue on the management server. If it just doesnt reset the health state right you could place the agent machine (not the management server) into maintenance mode for 15 minutes and see what happens after it comes out of maintenance mode. Sometimes this will clear up.Bob Cornelissen - BICTT (My BICTT Blog)

If it hangs I would suggest you might have some kind of issue on the management server. If it just doesnt reset the health state right you could place the agent machine (not the management server) into maintenance mode for 15 minutes and see what happens after it comes out of maintenance mode. Sometimes this will clear up.Bob Cornelissen - BICTT (My BICTT Blog)

Hi, Its a Management Server, In Event Logs it showing Event ID : 31552 Failed to store data in the Data Warehouse. Exception 'SqlException': Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance Instance name: State data set Instance ID: Management group: MNYash

The 31552 event isn't related to the problem of health state not changing. The 31552 event indicates some process not able to complete in time in the DW. Recalculate health only works on monitors that have probe action defined to recalculate health - most monitors do not. If reset health isn't working, try Bob's solution and let us know. Don't forget not to sweat the small stuff: http://blogs.technet.com/b/jonathanalmquist/archive/2011/01/29/lessons-in-scom-don-t-sweat-the-small-stuff-and-learn-to-choose-your-battles.aspx You can also try Green Machine: http://blogs.technet.com/b/timhe/archive/2009/01/15/announcing-the-greenmachine-utility-for-operationsmanager-rtm-sp1-and-r2.aspx HTH, Jonathan Almquist - MSFT

Hi All, My Problem is Not able to Reset Health in Health Explorer, Showing Calculating the Health State of the following monitor and gets hang and it wont respond also. Please help me to fix this issue.MNYash

Hi, to re-itterate.. Have you done the maintenance mode thing on the agent? Do you see any other errors in the operationsmanager log (not related to datawarehouse)? Do you see any errors in the scom monitoring when going to Monitoring - Operations manager - management server and look at the health state views.Bob Cornelissen - BICTT (My BICTT Blog)

Have you tried Bob's suggestion about the maintenance mode?Regards, Marc Klaver http://jama00.wordpress.com/

Hi, It is having problem with Management Server, Not in Agent System. In Operation Manager Log it is showing the Below Event IDs : HealthService 4512 None Converting data batch to XML failed with error "Not enough storage is available to complete this operation." (0x8007000E) in rule "Microsoft.SystemCenter.ACS.Collector.EventCollection" running for instance "Microsoft.SystemCenter.ACS.Collector" with id:"{}" in management group " ". The rule will be unloaded. AdtServer 4618 None Error occured on database connection: Status: 0x0021C001 ODBC Error: 0 ODBC State: 08S01 Message: [Microsoft][ODBC SQL Server Driver]Communication link failure Database: SqlWriter Connection: Maintenance Statement: spCheckPoint OpsMgr SDK Service 26319 None An exception was thrown while processing Connect for session id uuid:f2a0032b-25c6-4252-8a32-fdc237eeb538;id=5. Exception Message: The creator of this fault did not specify a Reason. Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException: The user DARF\Administrator does not have sufficient permission to perform the operation.). MNYash

Well for us it was important to know if that one agent would reset its state after you place it in maintenance mode. That was your first problem. Thats why we would like you to test that with the one box. In the error output you give us now we see two things (at least I see two things at first glance..). - Not enough storage is available to complete this operation - The user DARF\Administrator does not have sufficient permission to perform the operation So the first might have to do with a memory problem on your RMS. Check for that. Or reboot the whole box and try right after the reboot. ;-) The second the account permissions. Is the account member of the SCOM Admins group? Are any of the System Center services on the RMS running this account or was it you that is using this account to logon to SCOM? Also check this one for rights of accounts: http://blogs.technet.com/b/kevinholman/archive/2008/04/15/opsmgr-security-account-rights-mapping-what-accounts-need-what-privileges.aspx Bob Cornelissen - BICTT (My BICTT Blog)

Hi, How can i change the User Account Permission, Or Shall i add new user ( Which is having Domain Admin Right) I need to tell another Update. Recently we have upgraded the SQL 2008 Service Pack From 1 to 2. Will it give any problem. MNYash

I think the first is related to the database not the memory on the management server. MNYash should check it's ACS database for sufficient storage and free space in the ACS database. It looks like the database can not write it's checkpoint due to insufficient disk space (resulting in a roll back on the operation).Regards, Marc Klaver http://jama00.wordpress.com/

Hi Marc, I will check and i will revert you. MNYash

Hi All, I did all the settings, Its not working, So I had Reinstall the SCOM Server and Its OK Now. Thanks for the Support.MNYash

Hi All, I did all the settings, Its not working, So I had Reinstall the SCOM Server and Its OK Now. Thanks for the Support.MNYash