Just an update - reinstalling the agent cleared up this problem.
But anyone have ideas why this could happen and / or how to avoid it next time a windows patch is installed on the server?
what windows patches were applied? and what were they affecting?
It looks like a sizable update - approx 14 Security Updates for Windows 2003, including a culmulative KillBit and IE security update. I can publish a list if it helps.
Belmont Software Services
it appears that the passwd to the bladelogicrscd account was changed or affected in some way. it’s possible that could be related to the path, or it could be something else.
David, did you solved the problem we have the same issue on 2003 x32 systems, or dou you hav information how this problem is solved?
You may want to stop the agent service, delete the BladelogicRSCD account and restart the agent service. Please let me know if that helps.
Already I used this workaround so when we deploy jobs we are able to finish.
But everytime the server reboots the user account gets wrong logon.
If the user is re-created we can stop and start the service several times and we do not get wrong logons but after reboot the problem is there again.
In our case it is not on the BBSA app server. But it is on multiple BBSA clients w2003 x32 as well as x64.
Ferry van Kessel
CIBER Nederland B.V.
PO Box 843
5600 AV Eindhoven
There should be a fix for this in the 8.1 SP1 Patch3 agent.
Yes Bill, you were totally right the problem is solved in this patch. I got the same solution from BMC suppport. I also issue a critical ticket for support of this problem. Tested the new agent and the problem does not occur anymore. thanks for the solution.
I'm also facing the same issue during Patching the target servers. The BladeLogicRSCD account is getting locked out post reboot during Patch installation. Applied the workaround as suggested earlier of deleting the BladeLogicRSCD account and restarting the service but still no luck. The issue doesn't happen on all the servers as well but on half of the inventory.
What version of the agent are you using?
I think this is fixed in 8.1 SP2. Whats the agent version?
It’s fixed in 8.1 SP2 Patch4 and 8.1 SP1 Patch3 and 8.0 SP10 or SP11.
The inventory has two versions of agents
i have seen the servers were accounts are getting locked are mostly 8.1.147 agents.
My application server version is 8.1.02.233 an rscd agent 126.96.36.199. so u suggest me to upgrade both the agent versions