Menu
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.
663
To deploy SSIS packages from SSDT to SSISDB, using Integration Services Deployment Wizard is one of the simplest and interactive ways. All you have to do is to right-click the package and click on Deploy, go through a few menus and you are done.
In SQL Server 2012, you can deploy SSIS packages using the command-line tool ISDeploymentWizard.exe. This tool works with the . ispac file, which is created in the project's BIN directory when you build the project in SQL Server Data Tools.
Reasons that the package may have failed are as follows: The user account that is used to run the package under SQL Server Agent differs from the original package author. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
Integration Services supports two deployment models, the project deployment model and the legacy package deployment model.
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
159
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
