Perform the following to determine if either problem is being encountered in the environment:
Virtual Assurance cannot login or communicate to SQL:
Data::ODBC::HandleException<void *,2>: Exception
IWebServiceDependency::waitForDependency SQL isAvailable returned false.
or
Virtual Assurance cannot access EEM Server:
"Failed to connect to EEM using System account. Reason: <EE_AUTHFAILED Authentication Failed>"
If the errors point to SQL:
You can verify sql communication by running the osql command:
Windows Authentication
osql -S <sql-server-name\INSTANCE>,1433 -E -Q "SELECT * FROM sysdatabases"
SQL Server Authentication
osql -S <sql-server-name\INSTANCE>,1433 -U <user-name> -P <password> -Q "SELECT * FROM sysdatabases"
dmputil -set -mgmtdb and dpmutil -set -aom2
<Please see attached file for image>
dpmutil -get -mgmtdb or dpmutil -get -aom2
<Please see attached file for image>
If the errors point to EEM:
If the log does not update:
In some rare cases the log may not update or, if the log was deleted, it may not be recreated. In these instances the server should be rebooted and the CAAIPApache service will start normally on boot.
At this time there is no known root cause for this problem and why it is cleared via a reboot.