Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 10966016
KB4039736 - FIX: SSIS package does not start when it's run by a CLR stored procedure whose user does not have SYSADMIN permissions - Microsoft Support
Last update date:
7/20/2023
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2016 Service Pack 1
SQL Server 2017 on Windows (all editions)
Affected releases:
build lower than 14.0.3006.16
Fixed releases:
14.0.3006.16
Description:
Symptoms
Assume that you launch Microsoft SQL Server 2016 or 2017 Integration Services (SSIS 2016) package by using the common language runtime (CLR) stored procedure. When you run the CLR stored procedure which calls the SQLContext.WindowsIdentity property, you may notice that the SQLContext.WindowsIdentity property returns a NULL value for impersonated calls in SQL Server due to which the SSIS package does not start. This issue occurs if the CLR procedure is owned by a user who has a Windows login (not a SQL Server login) that does not have the SYSADMIN permissions. Additionally, you may receive an error message that resembles the following: The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Windows Authentication.
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 1 for SQL Server 2017 Cumulative Update 5 for SQL Server 2016 SP1 Note: To fix this issue, Trace flag (TF) 4637 must be enabled.
