Summary

Compliance import from ADDM fails with the error of "The staging state of the source ADDM staging database is currently set to "failed". 

Symptoms

2014-10-21 09:45:29.20: Importing from 'ADDM' [type: ADDM]
2014-10-21 09:45:29.25: FATAL: The import process has failed with the following error (use -verbose to see error details):
Error: ERROR: The staging state of the source ADDM staging database is currently set to "failed". This indicates one of the following: the staging state has not been set ("unknown"), the staging process has started and not completed ("running") or staging has failed ("failed"). The staging state value must be "success" if staging was successful. Please review the output of the ADDM staging tool.
There is a possible connection type mismatch: check that the database is of the correct connection type 
ERROR: The staging state of the source ADDM staging database is currently set to "failed". This indicates one of the following: the staging state has not been set ("unknown"), the staging process has started and not completed ("running") or staging has failed ("failed"). The staging state value must be "success" if staging was successful. Please review the output of the ADDM staging tool.
2014-10-21 09:45:29.25: Error Details:
ManageSoft.Compliance.Importer.Logic.ComplianceReaderFatalException
at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.CalculateVersion(ReaderConfig sourceDataType, SourceConnection sourceConn)
at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ExecuteReaders(ComplianceReader p_ComplianceReader, IExecutionContext context)
at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ExecuteComplianceReader(ComplianceReader p_ComplianceReader, Tenant tenant)
at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.RunImport()
2014-10-21 09:45:29.26: 
2014-10-21 09:45:29.26: Time: Tuesday, 21 October 2014 9:45:29 AM
2014-10-21 09:45:29.26: Total import time: 0 seconds
2014-10-21 09:45:29.26: 
2014-10-21 09:45:29.26: 0 source data warnings
2014-10-21 09:45:29.26: 
2014-10-21 09:45:29.26: 0 errors, 0 warnings
2014-10-21 09:45:29.26: 1 fatal errors. Imports may be incomplete or failed.

Cause

The settings were not pulling all of the columns in the table, and this was causing a mismatch where non-smallint data was trying to be written to the Processors, Cores, and LogicalProcessors columns in the database. updated settings file, FnmpADDMSettings_fixed.xml, with the method set to staged (this will create the XML files so that we can review the data and write the data to SQL).

Resolution

1) Replace "FnmpADDMSettings.xml" with the attached "FnmpADDMSettings_fixed.xml"
2) Add connection strings to be suitable for the customer's environment.