I've just installed SC2007 but I get an error each time I attempt computer discovery. Health service 'computername' in which the location monitoring object is contained is not available. Make sure that the computer hosting the health service is available and verify the health service is running. The computer that is running the health service is localhost, and it is running. I can start and stop it from the services mmc without any complaints. It's running using the local system account. This text is from the additional information box: "Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run. Microsoft.EnterpriseManagement.Common.LocationMonitoringObjectNotAvailableException: Health Service 'computername' in which the location monitoring object is contained is not available. Make sure that the computer hosting the Health Service is available and verify that the Health Service is running. at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleSubmitTaskIndigoExceptions(Exception ex) at Microsoft.EnterpriseManagement.DataAbstractionLayer.AdministrationOperations.LaunchDiscovery(Guid batchId, List`1 jobDefinitions) at Microsoft.EnterpriseManagement.Administration.ManagementServer.BeginExecuteWindowsDiscovery(IList`1 discoveryConfigurations, AsyncCallback callback, Object state) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Administration.DiscoveryProgress.<>c__DisplayClass7.<SubmitTask>b__3(Object , ConsoleJobEventArgs ) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent jobOwner, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)" I've tried specifying accounts other than the management server action account, even DA accounts which I know have full access to my servers but I always get this error. In administration - security - run as accounts, I have tried changing the credentials here for the action account but this also makes no difference. My operaions manager event log is full of1102 events. Where have I gone wrong?

If you go to the monitoring view of the UI does the SCE server show as healthy? If not what exactly is being reported as unhealthy?

It shows as healthy. If I drill down further into Health Explorer then it has all green ticks apart from MOM2005 Monitoring Rollup and Security which are all blank. There are a bunch of other servers in there which seem to have been discovered automatically with a status of "Not Monitored". I've also got event 7015 in the event log: The Health Service cannot verify the future validity of the RunAs account CORP\momadmin for management group MOM2007. The error is Logon failure: unknown user name or bad password. (1326L). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. But this account is a DA and the password has definitely been typed in correctly.

You should try re-entering the username and password into the RunAs accounts section of the UI to make sure that the account is correct. I would recommend taking a look at all the RunAs accounts to make sure you didn't miss one using the CORP\momadmin account. If the account still has issues you should check the security audit log to see what exactly caused the logon failure. If the account is a domain account sometimes the security audit log on the domain controller will have more information about why it failed the logon.

Did this solve your problem? I'm having the same issue. If I watch the service, it's running (and stays running). Once I get the error, if I leave the screen up and restart the service, then return to the screen and retry it, it "usually" works....very strange.

My healthservice does not even start. I've uninstalled and reinstalled - same thing. I've changed the logon account from local system to a DA - no good. The other services (OpsMgr SDK and OpsMgr Config) are running. At one time, SEC 2007 was working on this server and MOM 2005 before that. SCE just stopped working - would not discover, stopped reporting errors, etc. That's why I uninstalled and reinstalled. This is on a domain controller - I know it's not recommended, but it's the only server available. What am I overlooking?

The health service should only run under the local system account. To change the account context tasks run under, use the administration space user role for the action account. This is also the location to change passwordsafter a password change. Note that this account requires to be a local administrator on the machine. If the machine is a DC, the requirement is still a local administrator - it does not have to be a member of the domain admins group. If the health service cannot start, can you see what errors appear regarding starting the service in the event log?

Trying to start the server manually give the following error: "Count not start the OpsMgr Health Service service on Local Computer. Error 0x80004005: Unspecified error" The following is in the Application log: Event Type:InformationEvent Source:MSSQL$SCEEvent Category:(2)Event ID:17137Date:7/2/2007Time:1:47:22 PMUser:NT AUTHORITY\SYSTEMComputer:NETMONDescription:Starting up database 'ReportServer$SCETempDB'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: f1 42 00 00 0a 00 00 00 B......0008: 0b 00 00 00 4e 00 45 00 ....N.E.0010: 54 00 4d 00 4f 00 4e 00 T.M.O.N.0018: 5c 00 53 00 43 00 45 00 \.S.C.E.0020: 00 00 11 00 00 00 52 00 ......R.0028: 65 00 70 00 6f 00 72 00 e.p.o.r.0030: 74 00 53 00 65 00 72 00 t.S.e.r.0038: 76 00 65 00 72 00 24 00 v.e.r.$.0040: 53 00 43 00 45 00 00 00 S.C.E... I don't know if this helps or not, but this is in the "Operations Manager" event log every 10 minutes. Obviously it's because the service is not running, but didn't know if it had any information that may be helpful: Event Type:WarningEvent Source:OpsMgr Config ServiceEvent Category:NoneEvent ID:29104Date:7/2/2007Time:1:49:31 PMUser:N/AComputer:NETMONDescription:OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Hi I am having exactly the same problem. Was a solution ever found?? Thank you