Solved: Device Fault Manager 3.0.5 starts, but have issues with alerts portlet

aserov · ‎12-10-2009

Hello

We have windows 2003 server running LMS 1.0.1 and DFM 3.0.5, and have error messages on the "High Severity Alerts" DFM portlet says : "An exception occurred. Please check the AAD.log file for further details". AAD.log attached. Also "netstat -anob" attached.

Previously it works fine. dmgtd restart doesn't help. No problem with device management in DFM.

Any help will be really appreciated.

Regards,

Cedric.

Joe Clarke · ‎12-13-2009

Your EPM database is down. This could be due to a corrupt transaction log, or a corrupt database. First, shutdown Daemon Manager, then delete the NMSROOT/database/dfmEpm/dfmEpm.log if it exists. Then run the following command:

NMSROOT/objects/db/win32/dbsrv9 -f NMSROOT/databases/dfmEpm/dfmEpm.log

Then try restarting Daemon Manager. If the EPMDbEngine process is still down, you will need to restore LMS from a known good backup, or reinitialize this database with the command:

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=epm dmprefix=EPM

View solution in original post

Joe Clarke · ‎12-10-2009

Post the output of the pdshow command.

aserov · ‎12-10-2009

Here it is.

Joe Clarke · ‎12-13-2009

Your EPM database is down. This could be due to a corrupt transaction log, or a corrupt database. First, shutdown Daemon Manager, then delete the NMSROOT/database/dfmEpm/dfmEpm.log if it exists. Then run the following command:

NMSROOT/objects/db/win32/dbsrv9 -f NMSROOT/databases/dfmEpm/dfmEpm.log

Then try restarting Daemon Manager. If the EPMDbEngine process is still down, you will need to restore LMS from a known good backup, or reinitialize this database with the command:

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=epm dmprefix=EPM

aserov · ‎12-14-2009

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmEpm dmprefix=EPM

This command helps. Thank you.