Error 6522
Contents |
Marketing Produkte ORAYLIS Tools ORAYLIS Vorgehensmodell ORAYLIS Guide Unternehmen Über uns Kunden Partner Kontakt Karriere Blog Twittern Fixing SQL 2012 SSIS Deployment Error 6522 „A required privilege is not held by the client" 30.Sep/13 by Stefan Grigat under Technical a required privilege is not held by the client ssis proxy Value Last week at customer side we faced the issue that project deployment replace a process level token greyed out of a SQL 2012 SSIS Project was not possible any more. On Wednesday we deployed the Project with Project-Deployment-Modell and ssis replace a process level token all went fine. Doing the same thing on Friday with the new build the deployment failed. The following error message appeared: Error 6522, A required privilege is not held by the client Msg
Replace A Process-level Token (seassignprimarytokenprivilege)
6522, Level 16, State 1, Procedure deploy_project_internal, 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) At first I thought it's a Visual Studio 2010 / Data Tools issue. So I tried to deploy the project using a required privilege is not held by the client sql server agent the stored procedure „catalog.deploy_project" but it failed with the same issue. On another server the deployment worked. So the project itself was still fine. While searching the web for error code and the error message I found hints pointing in the direction of CLR- or DCom-Permissions. Others reported that the error reappeared after a reboot. I checked the SQL-Server and Windows errorlog. The server was rebooted in the meantime and admins told the some group policies might have been applied to the server. So I tried the solutions presented in the web but none really worked, neihter giving the SQL-Server-Engine-Account and the SSIS-Service-Account the full permission in DCom-configuration nor adding the Service-Accounts to the local administrator group. Using Local-System-Account was no option as it was set to use Active-Directory-Service-Accounts. Another search in the internet brought up the hint to do a SQL-Server-Repair-Installation. But it was also said that this „fix" only works to the next reboot. So this couldn't be the correct answer. But then it came to my mind: „If a Repair-Installation helps and we know it has something to do with permissions and Group-Policies, let's check which permissions are granted during the (Repair-)Installation." Microsoft say
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and a required privilege is not held by the client). the step failed policies of this site About Us Learn more about Stack Overflow the
This Setting Is Not Compatible With Computers Running Windows 2000 Service Pack 1 Or Earlier
company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only https://blog.oraylis.de/2013/09/fixing-sql-2012-ssis-deployment-error-6522-a-required-privilege-is-not-held-by-the-client/ takes a minute: Sign up SSDT 2012 - ssis deployment error up vote 1 down vote favorite 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 http://stackoverflow.com/questions/34190385/ssdt-2012-ssis-deployment-error 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. ssis share|improve this question edited Dec 9 '15 at 22:58 billinkc 38.4k56291 asked Dec 9 '15 at 22:42 user5661489 162 add a comment| 3 Answers 3 active oldest votes up vote 0 down vote 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/
in callers, SQLCLR error 6522, and T-SQL TRY-CATCHBy: Bob Beauchemin Posted on: November 15, 2005 10:16 am I've been going over how errors are raised in SQLCLR against the SQL Server 2005 RTM version. http://www.sqlskills.com/blogs/bobb/seeing-errors-in-callers-sqlclr-error-6522-and-t-sql-try-catch/ If you remember (search the blog on "6522" if you don't) how errors made their way from the managed to the unmanaged stack evolved throughout the beta. My goal in investigating this was to determine if http://sqlblog.com/blogs/jamie_thomson/archive/2012/07/11/ssis-catalog-windows-updates-and-deployment-failures-due-to-system-core-mismatch.aspx you can make SQLCLR acts the same way that T-SQL acted with respect to errors. Then, you could replace T-SQL functions and procedures with SQLCLR without changing every caller. 6522 (that's a general error that means is not "an error in the SQLCLR stack occurred) is still with us. You get one if there is an unhandled exception in ExecuteNonQuery or ExecuteReader inside a SQLCLR proc.If you want this error to go away and want only the original SQL error (e.g. 547 referential integrity error) to be returned to the caller, the only way to do this is to use SqlPipe.ExecuteAndSend in your SQLCLR procs. If you have no catch block, a required privilege both the 6522 and the "original" (e.g. 547) error will be returned. If you're called from client code, the error number is e.g. 547, the 6522 follows afterward. If you want to "lose" the 6522 altogether use ExecuteAndSend and use a dummy try-catch block in your SQLCLR code. It would look like this: try { … … SqlContext.Pipe.ExecuteAndSend(cmd) } catch { // no code here } In this case you only get the original error e.g. the 547. Note that if you use SqlCommand's ExecuteNonQuery or ExecuteReader with the dummy try-catch concept, you lose the error entirely. Bear in mind that if you use T-SQL's TRY-CATCH in SQL Server 2005, there is no way to raise *exactly* the original error either. You can come close, but the is no RETHROW. You can use RAISERROR, but RAISERROR doesn't work with system errors. You can reformat the original error message in a user error. Upshot of this is that if you convert to either SQLCLR or T-SQL TRY-CATCH and depend on seeing the original error number at the caller (normally the case even if you have error handling in your procs), you're going to be changing the callers' code. Or using only ExecuteAndSend. Related PostsCombined provider: transactions and the return of 6522Error 6522:the repriseIsNull != IS NULL,
London working for Dunnhumby SSIS Catalog, Windows updates and deployment failures due to System.Core mismatch This is a heads-up for anyone doing development on SSIS. On my current project where we are implementing a SQL Server Integration Services (SSIS) 2012 solution we recently encountered a situation where we were unable to deploy any of our projects even though we had successfully deployed in the past. Any attempt to use the deployment wizard resulted in this error dialog: The text of the error (for all you search engine crawlers out there) was: A .NET Framework error occurred during execution of user-defined routine or aggregate "create_key_information": System.IO.FileLoadException: Could not load file or assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) System.IO.FileLoadException: System.IO.FileLoadException: at Microsoft.SqlServer.IntegrationServices.Server.Security.CryptoGraphy.CreateSymmetricKey(String algorithm) at Microsoft.SqlServer.IntegrationServices.Server.Security.CryptoGraphy.CreateKeyInformation(SqlString algorithmName, SqlBytes& key, SqlBytes& IV) . (Microsoft SQL Server, Error: 6522) After some investigation and a bit of back and forth with some very helpful members of the SSIS product team (hey Matt, Wee Hyong) it transpired that this was due to a .Net Framework fix that had been delivered via Windows Update. I took a look at the server update history and indeed there have been some recently applied .Net Framework updates: This fix had (in the words of Matt Masson) “somehow caused a mismatch on System.Core for SQLCLR” and, as you may know, SQLCLR is used heavily within the SSIS Catalog. The fix was pretty simple – restart SQL Server. This causes the assemblies to be upgraded automatically. If you are using Data Quality Services (DQS) you may have experienced similar problems which are documented at Upgr