Note This issue occurs when the following registry subkey is set to 1:
Service pack information
SQL Server 2016To fix this issue in SQL Server 2016, get Service Pack 1 for SQL Server 2016.
SQL Server 2014To fix this issue in SQL Server 2014, get Service Pack 2 for SQL Server 2014.
SQL Server 2012To fix this issue in SQL Server 2012, get Service Pack 3 for SQL Server 2012.
- Turn off the FIPS policy on the server. To do this, see the "To configure FIPS policy settings" section on the following TechNet website:Notes
- You must restart the application for the new setting to take effect.
- This setting affects the following registry value in Windows Server:HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\EnabledThis registry value reflects the current FIPS setting. If this setting is enabled, the value is 1. If this setting is disabled, the value is 0.
- Use other Microsoft .NET solutions instead of the Script component.
Note The MD5 algorithm is hard-coded within the data flow Script component. Therefore, you cannot change this Script component.
Article ID: 2925865 - Last Review: Dec 2, 2016 - Revision: 1