Is this a domain controller ? or a member/standalone server ?
Yes, it's a domain controller.
It means something got messed up w/ the domain level bladelogicRSCD account. did you change the passwd for this account recently w/o using chapw ?
No, i didn't change password.
I tried to upgrade RSCD agent from 8.0 to 8.5, before upgrade it was working fine with 8.0. but after upgrade getting issue. even i rolled back with 8.0 agent, but still facing same issue.
can you see if the domain bladelogicRSCD account is locked ?
Yes, I checked that's not locked.
you can try this:
- stop the rscd service on all DCs in the domain
- delete the BladeLogicRSCD account on the PDC emulator
- force replication of the delete from ad sites and services
- delete the HKLM\SECURITY\SAM\BladeLogic\Operations Manager\RSCD\E and S registry values on all DCs
- start the rscd service on the pdc emulator, confirm it works
- force replication (new bladelogicRSCD is created) again
- start the service on the other DCs.
Issue got resolved now after re-installing RSCD agent.
But now we are getting another below errors on different servers while trying to upgrade agent servers.
Error operable program or batch file
Error 'msiexec' is not recognized as an internal or external command,
ERROR: RSCD agent upgrade failed. MSI returned error code : 1601
ERROR: RSCD agent upgrade failed. MSI returned error code : 1603
Server1 and Server2 error seems to be related to Windows Installer service. Go to services.msc and check if this service is running and if it stopped then start it.
Another thing you can do is to unregister and register msiexec with below commands and restart system and check if installation works.
For Server3 - You can check event viewer and see if you are able to find some error there.
After change in export file issue got resolved for server-2.
For server-3, below log in event viewer:-
Product: BladeLogic Server Automation RSCD Agent -- Error 1606. Could not access network location \BMC Software\BladeLogic\8.0\RSCD.
did you copy the msi locally to the server before starting the install ?
Can you try doing that ?