Alfred,

Points / Questions -

I am assuming that this cluster has been working. What has happened recently to change the environment ?

In the log directory (normally c:\program files\emc autostart\ \log) what does the domain-name_node-name.log file say ?

If you stop the backbone and agent on both nodes from Windows Service Manager, can you start the agent and backbone on only one node ?

Unable to open taf or dbl files suggests that there are errors accessing the shared Raima database. Has any one changed the systems recently where either anti-virus or backup software could have accessed these files ?

Has anyone changed the file permissions on the AutoStart directory or parts of the tree.

If you are unable to open the taf and dbl files on any of the nodes, it sounds as if you have a corrupted internal database and that you should be speaking with support as to a procedure to recover this database. This will normally require the re-import of the domain def information so you should ensure that you have a recent domain backup file available before starting the process.

Hope this helps

IKP

Currently the customer gets the error on both nodes when trying to start the agent.
They have no backups of the AAM config.


The tech that is onsite has just picked up the account, so he cannot answer the what changed question. It was working at one time.

Anti-virus is supposed to be excluded. There is no auto-backup software as far as he knows.

I have requested the AAM support logs to see if I can figure out what happened, but if I can't find anything I will open a support case. I had something similiar where the end user changed the AAM domain name, so I will look to see if they did that here.

He says that no one has been managing permissions because the servers are on a closed network segment. I will have him check though.

Thanks for the suggestions.