SSDT 2012 - SIS Deployment Error

Question

I am trying to deploy an SSIS SSDT 2012 project using the Deploy option. But I get the error below:

TITLE: SQL Server Integration Services

A .NET Framework error occurred during the execution of the user routine or aggregate "deploy_project_internal": System.ComponentModel.Win32Exception: The requested privilege is not held by the client System.ComponentModel.Win32Exception: in Microsoft.SqlServer.IntegrationServices.Server.ISServerProcess.Startpread () Microsoft.SqlServer.IntegrationServices.Server.ServerApi.DeployProjectInternal (SqlInt64 deployId, SqlInt64 versionId, SqlInt64 projectId, SqlString projectName). (Microsoft SQL Server, Error: 6522)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.5058&EvtSrc=MSSQLServer&EvtID=6522&LinkId=20476

Any idea why this error? Below is a screenshot of the error.

Answer 1

This error often means that the SQL Server Agent account does not have permission. “Mandatory privilege is not held by the client” in this case means that the SQL agent account is called to execute something, but is not allowed.

SQL Server reset SQL Server (, , SQL Server). , .

, , .

: http://blogs.msdn.com/b/dataaccesstechnologies/archive/2012/08/20/error-while-deploying-ssis-2012-project-from-ssdt-to-ssis-catalog-system-componentmodel-win32exception-a-required-privilege-is-not-held-by-the-client.aspx

Answer 2

Microsoft SQL Server Data Tools - Business Intelligence Visual Studio 2012. SQL-, SQL Server. SQL Server Management . SSIS .

Answer 3

: https://msdn.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Windows

Answer 4

According to this blog, the required user right may be

Replace Process Level Token

https://www.oraylis.de/blog/fixing-sql-2012-ssis-deployment-error-6522-a-required-privilege-is-not-held-by-the-client

Answer 5

I went through most of the other solutions, but it worked with the help of the repair option.

The problem could be related to installing Visual Studio and SSDT after installing SQL.

It would be nice if MS would provide better support for its products rather than provide the community with a solution to this problem.