Hi Yury, First have you upgrade the DW?

Alsocould you send me a exported copy on this registry key HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ Health Services \ Parameters \ Management Groups \ Intern \ SSDB \ References so I can check if there are any missing keys on the SRS server



Simon

Here's the thought, did this box have the Beta version of R2 Version 6.1.6407.0 as the reporting and agent cannot be upgraded. Have a look in the Registry for the version 6.1.6407.0 via a search or F3

Thanks for the update, I can across this problem last week where SRS reported an agent error the same as your, I had found that there were old components in the registry that created the problem. So here is a list of things to check

go to the MMC to Certs Local Computer in the OpsMgr folder how many certs are there? if more than 1 delete them all.

run "Net Stop HealthService" then go to >Program Files\system center operations manager 2007\health service state\health service store and delete ALL (edb, healthservicestore.edb, edb.chk, res1, res2) then Net Start HealthService.



So what we are doing here is stopping the HealthService deleting the store then starting it again, this may help for the Health Service to download the new rules, we are also checking that the cert is OK (there is always a cert) Had we been able to contact the agent via the console we could have used the 'Flush Cache' function which will dete those same files.

Can you send me a evt of the OpsMgr event log please?

I repared agent through console, but the same errors in opsmgr уме log.

Can you remove the Operations Manager Agent leave SRS alone then wait for an hour then resend the logs again. If you can do a remove agent from the console?

Solution;

 

Remove uninstall or remove agent from operation console.

Deploy agent from operation console or install manually,

re-import the mentinoned key from previous posts and start the service.

Stop RMS config service

Start RMS config service,

Stop RMS health service

Start RMS health Service.

Check event log; it should be communicating correctly.