SSDT 2012 - ssis deployment error

10
votes

I am trying to deploy a SSDT 2012 SSIS project using Deploy option. But I am getting below error:

TITLE: SQL Server Integration Services

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) . (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 the screen shot of the error.

enter image description here

4
ssis

4 Answers

3
votes

That error often means the SQL Server Agent account is missing a permission somewhere. The "A required privilege is not held by the client" in this case means the SQL Agent account is called to do something but isn't permitted to.

One thing to try is to use the SQL Server Configuration Manager, as administrator, to reset the account for SQL Server Agent (and possibly SQL Server itself). This will reinstate the required permissions if you have sufficient rights.

I have seen cases where Group Policy prohibited the assignment of the service account to needed permissions at the OS level, which really creates a problem.

Example: 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

2
votes

I have faced this issue after installation of Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012. After installation I started repair option of SQL server management studio by running SQL Server Setup. After restarting SQL Server Management studio issue resolved Now I can deploy SSIS package in Integration Service Catalog. Repair Option Shown below

2
votes

Went through most of the other solutions but using the repair option worked.

The problem could have been due to the installation of Visual Studio and SSDT after SQL was installed.

Would be nice if MS provided better support for their products rather than leaving to the community to fix the problem.