Symptoms
Assume that you use Microsoft SQL Server 2012 Integration Services (SSIS 2012) or SQL Server 2014 Integration Services (SSIS 2014). When you have an SSIS XML task that has the OperationType property configured to Validate, the SSIS XML validator outputs only values of true or false. This behavior is by design in SQL Server Integration Services.
However, when the validation outputs a value of false, it can be difficult to determine where the error exists in the XML document that is being validated.
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL Server 2012 SP2 /en-us/help/2976982
Cumulative Update 2 for SQL Server 2014 /en-us/help/2967546
Cumulative Update 10 for SQL Server 2012 SP1 /en-us/help/2954099
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
After you apply this hotfix, a new task property ValidationDetails is introduced in this hotfix. Its data type is bool and the default value is false. When you use the default value, the validation output is still the same string of true or false. To obtain the detailed validation output in XML format, you have to change the property value to true. The output XML resembles the following:<?xml version="1.0" encoding="utf-8"?>
<root xmlns:ns="http://schemas.microsoft.com/xmltools/2002/xmlvalidation">
<metadata>
<result>false</result>
<errors>1</errors>
<warnings>0</warnings>
<startTime><DateTime></startTime>
<endTime><DateTime></endTime>
</metadata>
<messages>
<error line="1" position="6250">The key sequence 'HUNGC' in 'CustomerIDKey' Keyref fails to refer to some key.</error>
</messages>
</root> Note To take full advantage of the newly added ValidationDetails option and enhanced output, you can install the cumulative update on both the SSIS server on which the packages are run and the SSDT developer computer on which packages are developed.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
