1.1 A .NET Framework error occurred during execution of user-defined routine or aggregate "msp_GenerateKeys":
Msg 6522, Level 16, State 1, Procedure msp_GenerateKeys, Line 0
A .NET Framework error occurred during execution of user-defined routine or aggregate "msp_GenerateKeys":
System.Data.DBConcurrencyException: Concurrency violation: the UpdateCommand affected 0 of the expected 1 records.
1.1.1 Possible Cause:
The keys table exists and is not empty, and msp_GenerateKeys previously failed.
Subsequently running msp_GenerateKeys means that, because the table isn’t empty, SQL Update commands are used to write data to the key fields rather than an Insert command (if the table was empty). But the exception is thrown when trying to update a row that doesn’t exist.
To get around this, delete the keys table then re-run the key generation. Also, please consider using msp_BulkGenerateKeys, as that stored procedure is much less likely to leave the table in an incomplete state
1.1 Column ‘<column>’ has invalid type: <type>
Msg 6522, Level 16, State 1, Procedure msp_OutputDuplicates, Line 0
A .NET Framework error occurred during execution of user-defined routine or aggregate "msp_OutputDuplicates":
core.DataException: Column '<column>' has invalid type: <type>
matchIT SQL currently provides support for the following column data types: bit, tinyint, smallint, int, bigint, char, varchar, nchar, nvarchar, datetime, xml, uniqueidentifier, float, real, decimal, numeric.
Other data types (such as money, text, and date) can still be mapped in XML configuration files, but they will cause this exception in stored procedures such as msp_OutputDuplicates and msp_OutputDedupedTable. Please contact 360Science if you encounter such an exception.