I am attempting to deploy a project to SQL 2012 and receive the security error below. I have tried the steps listed in this post (http://social.msdn.microsoft.com/Forums/en-US/vstsdb/thread/bd6a985c-0efc-4541-8771-5201ca47f9c8) but it did not resolve the issue. Any other ideas? I am server admin and sysadmin on SQL. -<SummaryReportItem><Message>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) .</Message><Property>Deploying project</Property><Status>Failure</Status><Value xmlns:a="http://www.w3.org/2001/XMLSchema" i:type="a:string">System.Data.SqlClient.SqlException (0x80131904): 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) . at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.SqlServer.IntegrationServices.Common.ObjectModel.SqlHelper.ExecuteSQLCommand(SqlStoreConnection storeConnection, CommandType cmdType, String cmdText, SqlParameter[] parameters, ExecuteType execType, Int32 commandTimeout) at Microsoft.SqlServer.Management.IntegrationServices.CatalogFolder.DeployProject(String projectName, Byte[] projectStream) at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeployExportProjectHelper.DeployProject(CatalogFolder folder, Project project) at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.Deploy(CatalogFolder folder, Project project) at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.DeployProject()</Value></SummaryReportItem>

It must be the DCOM issue, ispect other permissions. And if does not help please share here how you deploy. E.g. if it is x-server deploy using a deployment model or how?Arthur My Blog

In efforts to resolve this. I gave full permissions to each dcom security piece to "users" on the server. I am deploying locally to a test instance of SQL Server. Project level deploy to a new path in the SSIS catalog. I've tried through the VS 2010 wizard to deploy, using the ispac file and even the import method is management studio. All receive the same error.

Can you take an individual package and import it manually?Arthur My Blog

I think I will have to convert it to a package deployment model and I have using project level connection managers. When I try to import it swiches me to the conversion wizard and reports it cannot find the connection. The connection "...." is not found. This error is thrown by Connections collectionw hen the specific connection element is not found.

Is there something else I could try without having to rewrite my code?

I'm having the same problem - even with a new project with a single package and no connection managers. I've also updated DCOM permissions and verified permissions on the server and folder. The strange thing is that it was working previously and suddenly stopped. I'm starting to wonder if it's related to a patch.

Dayne, what patch did you install? Stacey, why are you referring to code? Are you deploying programmatically? Arthur My Blog

I have a script task in the package which references the connection manager. Sorry, just habit calling it code.

Can you try deploying somewhere else? We want to isolate this issue to a specific machine.Arthur My Blog

unfortunately, I don't have another 2012 environment.

I didn't install any specific patch. I just know that there was a batch of MS updates installed in the last couple of weeks on the server. It was working before then, so that's my only guess at this point. I am trying to deploy via the Visual Studio deploy wizard.

I tried deploying to a different server, and I get the same error.

Can you import a package manually to a catalog?Arthur My Blog

Yes, you need to use the package deployment model with project level connection managers. I don't think it's possible to use project connection managers and the package deployment model. You need to use the project deployment model to use these.MCTS, MCITP - Please mark posts as answered where appropriate.

I tried the "Import Packages..." wizard from the Projects node within SSMS. It took me through the steps of creating a deployment project and then ran the deployment wizard. It failed with the same error.

I would re-install SSIS along with all the shared components at this stage.Arthur My Blog

I have a support ticket open with Microsoft, I will report and progress made.

Even better, I was thinking of directing you to CSS but was unsure whether you will incur any costs, so I am glad you did and please post the outcome.Arthur My Blog

Hi All, We have seen this error in few cases where the Sql Server Service Account is running under the deafult built-in account "NT Service\MSSQLSERVER". We are still investigating why this happens on few scenarios and not consistent, we are inclined to believe that this could be because some permissions not granted to the "NT Service\MSSQLSERVER" account during installation due to some reasons but still not absolutely sure about it. For a work-around as of now, please change the Sql Server Service Account (NOT the SSIS Service Account) to a local admin user and you should be able to deploy the projects without any issues. Cheers, Debs

So I ran a SQL repair, and that fixed the problem. It worked for both servers. I think the only thing that's been done to both servers is a round of security patches. So I'm still wondering if that's what caused the problem. Hopefully they will keep working. I'll let you know if not.

Dayne, i think you are correct. I successfully used the deploy in VS2010 to install my project to this SQL2012 server previously. Currently it is broken with this error Adding my user and the sqlserver user to that local admins group on this server has had no effect I will run the SQL repair and repost. The SQL Repair fixed it for me as well.

See the answer from DebarchanS. That solved the problem permanently for me. (Changed the SQL Server service account.) Dayne

I also ran a SQL repair and it corrected the problem. However upon the next server restart the problem returned. Another repair again corrected the issue but I assume an additional restart will break it again. Scott Carnes

I am agreed with Scott. Having the same concern..Net