| Author |
Messages |
|
SuperUser
 
Posts:26
 |
| 04/20/2005 5:51 PM |
|
| I am using UAM 4.0 SP1, and had a server lock up today. The task manager showed multiple instances of dialog_u.exe running. We ended up having to do a hard reboot of the server, and when coming back up the Ca unicenter, mssql, world view agent, and DTS services weren't starting. The logs were full of DCOM errors. Only problem we still can't get figured out is a DCOM error involving the SeverityPropagation account. The account acts like it's locked out for failed password, but we're not sure how to change it. Any ideas on what could have caused all the accounts to lose their ability to validate the services seemingly out of the blue, what service uses the SeverityPropagation account and how to make it recognize a password change on this account? |
|
|
|
SuperUser
Posts:26
|
| 04/21/2005 8:20 AM |
|
Posted by Lisa Schroer (Unregistered Guest) on Wednesday, April 20, 2005 - 5:51 pm:
I am using UAM 4.0 SP1, and had a server lock up today. The task manager showed multiple instances of dialog_u.exe running. We ended up having to do a hard reboot of the server, and when coming back up the Ca unicenter, mssql, world view agent, and DTS services weren't starting. The logs were full of DCOM errors. Only problem we still can't get figured out is a DCOM error involving the SeverityPropagation account. The account acts like it's locked out for failed password, but we're not sure how to change it. Any ideas on what could have caused all the accounts to lose their ability to validate the services seemingly out of the blue, what service uses the SeverityPropagation account and how to make it recognize a password change on this account?
The CA-Unicenter TNG Severity Propagation services uses the SeverityPropagation account. This account monitors the tng_managedobjects table in TNGDB for severity changes. When a change takes place, it propagates the change (propagated_sev) up to the parent object. This services runs as a default and is a required service for a CORe/repository server. This services does NOT play well with Active Directory. The application of domain group policy disconnects this service from the database and there is no logic to check or reconnect it. I've fought with CA to get this fixed and/or to identify the specific security permissions required and they're clueless. As a temporary solution, I had to reconfigure the Log On properties in Services for the Severity Propagation service to use a domain level admin account (in Services; CA-Unicenter TNG Severity Propagation Properties; Log On tab) and I reconfigured the Identity in dcomcnfg (dcomcnfg; component services, computers, DCOM Config, CA Unicenter severity propagation Properties, Identity tab) to use this same account so that it will run properly. I do not know why you would be receiving DCOM errors nor do I know the default password but at least you now will know where you can change it. |
|
|
|
|