I am getting an error when trying to deploy an SSIS package to a SQL Server 2017 machine.
Environment:
Windows Server 2012 R2
.NET 4.7
SQL Server 2017
solution files local
visual studio 2017 w/SSDT
ssms 17.3
Action: Hit deploy on Visual Studio 2017 or execute the following code:
DECLARE @ProjectBinary AS VARBINARY(MAX) DECLARE @Operation_id AS BIGINT SET @ProjectBinary = (SELECT * FROM OPENROWSET(BULK 'C:\Source\MyPackage.ispac', SINGLE_BLOB) AS BinaryData) EXEC [catalog].[deploy_project] @folder_name = 'MyFolder', @project_name = 'MyProject', @project_stream = @ProjectBinary, @operation_id = @Operation_id out
The following error message is returned from the server:
Msg 6522, Level 16, State 1, Procedure internal.deploy_project_internal, Line 0 [Batch Start Line 0]
A .NET Framework error occurred during execution of user-defined routine or aggregate "deploy_project_internal":
System.ComponentModel.Win32Exception: A required privilege is not held by the client
System.ComponentModel.Win32Exception:
at Microsoft.SqlServer.IntegrationServices.Server.ISServerProcess.StartProcess(Boolean bSuspendThread)
at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.DeployProjectInternal(SqlInt64 deployId, SqlInt64 versionId, SqlInt64 projectId, SqlString projectName)
.
I have found several articles talking about this issue and most refer to permissions, like this one https://blogs.msdn.microsoft.com/dataaccesstechnologies/2013/08/20/system-componentmodel-win32exception-a-required-privilege-is-not-held-by-the-client-while-deploying-ssis-project/
I have verified that all permissions referenced are available to the service accounts that run SQL Server and the SQL Agent. SSIS is running with the NT Service\MsDtsServer140 account.
I have not seen anything in process monitor or event viewer that stand out as an issue, making me think this is some kind of SQL 2017/.NET 4.7/Visual Studio 2017 issue. I know we are still in preview...hoping that a patch will soon fix this and wanted to report my issue and hope that someone may know of a fix...my upgrade is currently on hold until I can resolve this one.