Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails.
This error occurs at run time when an attempt is made to use a null value while inserting or updating a column that does not allow null values.
Note This message differs from the following message, which indicates that the attempt has been detected at compile time.
error 233: The column '%.*ls' in table '%.*ls' cannot be null.
This error can also occur if the table that is the target of an INSERT or UPDATE statement in a stored procedure or trigger is being dropped and re-created, and one or more of the table column definition(s) have changed from NULL to NOT NULL.
If this error occurs when you are running an UPDATE or INSERT statement, verify that the data inserted or updated matches the column definition for the affected table.
Inserting or updating a column does not allow null values.
Note In a direct UPDATE or INSERT by value, you will get compile error 233 instead of error 515. Usually 515 errors occur in an INSERT/SELECT or an UPDATE statement that uses data in another table.
If this error occurs when a stored procedure or trigger references a table that has been dropped and re-created with different nullability, drop and re-create the affected stored procedure or trigger.
If you are unable to resolve the problem, contact your primary support provider for assistance.