Few days ago I found an error in RDLC report after published. The client claims that sometimes the report shows fine but sometimes shows the error. Then I test this report in my development PC but no luck. I can not generate any error. After that in my testing i found an error like below:
“An error has occurred during report processing.
Exception has been thrown by the target of an invocation.
Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.”
Then I start googling what was the problem. I found few solutions but these does not work for me. Then I have started to test again to produce this error. Here i want to show you how i can generate this error in my development PC. To ease the example i will show you by a simple query which caueses this problem. To generate this error add a DataSet into your project. Then right click on it to configure. Select Use SQL statements radio button then next next finish. The SQL for DataAdapter which i have used to produce this error is given below:
SELECT Title,Amount,Sort FROM ( SELECT 'None' Title,100 Amount,1 Sort UNION SELECT 'Sale of subscriptions and connections',150,2 UNION SELECT 'Sale of airtime for prepaid',200,3 UNION SELECT 'Broadband/Internet',220,4 UNION SELECT 'Prepaid services',200,5 UNION SELECT 'Partner/3rd party - revenues/ Partner/3rd party - revenues',190,6 UNION SELECT 'Other',240,7 UNION SELECT 'Costs/revenue sharing',250,8 ) tbl Order BY Sort
Ok our data adapter now configured. Now add a RDLC report. Drag a Table object on it. And drag & drop Title & Amount column in the table details row.
Ok now our RDLC report also configured. Now open the default.aspx page or add another aspx page into your project which will contain the RDLC report within ReportViewer control. Now add a ReportViewer control in your page. Add an ObjectDataSource into your page. Align DataSet with your ObjectDataSource. Now assign the DataSourceObject in the ReportViewer Control.
Now run the project you will get the below screenshot:
After different of tests i found that the problem is the length constraints. In DataSet i found the backend code generated length of 37 for Title column. So when the resultset try to retrieve a record more than length of 37 then report generates the error: Failed to enable constraints. Look at the auto generated code behind of DataSet:
So just change the length for the column will resolve the problem: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.
This type of error may appeared for different type of scenarios here i just shared one of them which i did not get in GOOGLE.