Avaya ACCS services cannot boot up

[hcmbmt]

Hi all,
Please advise if you have same experience or where should I check for below issue:
The ACCS for IP Office has two servers: Primary and Secondary. However, after reboot, the active server—whether it's the Secondary or the Primary—fails to start all services. Both servers hang at the same step during the startup process:
CCMS can start only 13/37 and get stuck here. I tried to do manual enable services but unsuccessful.

 

[hcmbmt]

These two servers have been joined to the domain. I suspect there may have been a policy change—what should I check?
Which policies might be causing this issue?

 

[Mo. Abdullah]

check if the 2 servers in active state or standby state.
from business continuity configuration select one server as active and the other as standby. then reboot the 2 servers.
the services will start on the active and won't start on the standby.
reenable the shadowing and switchover between them again.

 

[hcmbmt]

I had to restore the two servers, and the services are now able to boot up. Restore the database to get up to date configuration and data.
However, after a few hours of operation, all agents lost connection to ACCS. A reboot temporarily resolves the issue, but the connection is lost again after a few hours.
When login to agent desktop from Agent PC with their domain account, it shows this error:


After rebooting ACCS, they can log in normally. So, could the issue be related to the server itself rather than the network or policies

 

[Mo. Abdullah]

It is from the server itself. I had this issue before for one of our customers, and the solution was to stop the DB shadowing between the two servers and disable the automatic switchover, working with only one active server, without the standby server. I don't know exactly the cause of the issue or if it is related to network issue but this resolved the issue permenantily. It seems to me that the servers need to be redeployed or at least the standby server needs to be reconfigured.
The customer has no support with Avaya, so I couldn't determine the cause. Sorry for that. i just sharing my past experience.