Showing results for 
Show  only  | Search instead for 
Did you mean: 


This article covers the scenario when migrating from 9.2.3 to the Web UI where you get a NULL error trying to insert the 'ImporterString' column into table 'dbo.InstallerEvidenceType'


You can identify this issue by seeing an error similar to the following in the ComplianceMigration log:

Preparing to run step 'Migration from 9.3.6 to 10.0'.
Required minimum database compatibility level: SQL Server 2008 (100)
Found database compatibility level: SQL Server 2008 (100)
Required version: 9.3.6
Found version: 9.3.6
Executing step
Checking that all database objects are owned by dbo...Validated
Running 'cm-migr1000-migprep.sql'.

There was an error while attempting to run 'cm-migr1000-migprep.sql'.
Cannot insert the value NULL into column 'ImporterString', table 'FNMP_FM.dbo.InstallerEvidenceType'; column does not allow nulls. UPDATE fails.
The statement has been terminated.

Stack Trace

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ManageSoft.Database.Update.FileStep.ExecuteNonBCP(SqlConnection p_SqlConnection)


This is caused by the script only taking into account the legacy InstallerEvidenceType values. If there are any new values (such as those added into 9.2.3) or any custom evidence types then this script fails as it adds an ImporterString column which has to be populated and the script doesn't know what value to set.

This is reported as known issue - FNMS-27492: Migration failure on InstallerEvidenceType when migrating from FNMP 9.2 to FNMS 2014 or later


This issue is permanently fixed in FNMS 2015 R2 SP1.


Attached is an updated version of "cm-migr1000-migprep.sql" which should resolve the issue. This is the updated version that is being added to SP1.
Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Jun 04, 2018 02:01 AM
Updated by: