SQL server 2016 : Always Encrypted - Encrypted Column wizard failed- 'Task failed due to following error: Cannot save package to file. The model has build blocking errors: - by Pals_TR

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 3111925 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/17/2016 5:00:14 PM
Access Restriction Public

Description

SQL server Management Studio: Select Table-->Expand Column-->Right click Encrypt Column.

SQL Server Management Studio Encrypt column wizard throwing an error  " 'Task failed due to following error: Cannot save package to file. The model has build blocking errors:" when click finish now(after couple of minutes of execution). 

Nov 15 2016 14:43:03 [Informational] TaskUpdates: Message:Task: 'Performing encryption operations' -- Status: 'Failed' -- Details: 'Task failed due to following error: Cannot save package to file. The model has build blocking errors:
Error SQL71501: Error validating element [dbo].[INFORMATION_SCHEMA_INDEXES]: View: [dbo].[INFORMATION_SCHEMA_INDEXES] has an unresolved reference to object [sys].[indexes].
Error SQL71501: Error validating element [dbo].[INFORMATION_SCHEMA_INDEXES]: View: [dbo].[INFORMATION_SCHEMA_INDEXES] has an unresolved reference to object [sys].[objects].
Error SQL71501: Error validating element [dbo].[INFORMATION_SCHEMA_INDEXES]: View: [dbo].[INFORMATION_SCHEMA_INDEXES] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [sys].[indexes].[object_id], [sys].[indexes].[si] or [sys].[objects].[si].
Error SQL71501: Error validating element [dbo].[INFORMATION_SCHEMA_INDEXES]: View: [dbo].[INFORMATION_SCHEMA_INDEXES] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [sys].[indexes].[so], [sys].[objects].[object_id] or [sys].[objects].[so].
Sign in to post a comment.
Posted by Matteo [MSFT] on 1/23/2017 at 8:31 PM
This issue was fixed in the recently released SSMS 16.5.2 (https://msdn.microsoft.com/en-us/library/mt238290.aspx)

Thanks,
-Matteo
Posted by Jakub [MSFT] on 1/4/2017 at 5:29 PM
Thank you for reporting this bug. It has been fixed and the fix will ship in the upcoming version of SSMS.