Help - Cannot continue the execution because the session is in the kill state.

%3CLINGO-SUB%20id%3D%22lingo-sub-540054%22%20slang%3D%22en-US%22%3EHelp%20-%20Cannot%20continue%20the%20execution%20because%20the%20session%20is%20in%20the%20kill%20state.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-540054%22%20slang%3D%22en-US%22%3E%3CP%3EI%20try%20to%20execute%20a%20update%20query%20in%20SQL%20Server%202016%20(v13.0.5026.0)%20and%20get%20these%20error%20messages%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EUPDATE%20tableName%20SET%20fieldName1%20%3D'a%20long%20query%20with%20some%20html%20tags%20and%20all%20it%20has%203600%20chars'%20WHERE%20fieldName2%20%20%3D%2012345%3C%2FPRE%3E%3CP%3E%26nbsp%3BAnd%20get%20this%20error%2C%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EMsg%20596%2C%20Level%2021%2C%20State%201%2C%20Line%200%3CBR%20%2F%3ECannot%20continue%20the%20execution%20because%20the%20session%20is%20in%20the%20kill%20state.%3C%2FP%3E%3CP%3EMsg%200%2C%20Level%2020%2C%20State%200%2C%20Line%200%3CBR%20%2F%3EA%20severe%20error%20occurred%20on%20the%20current%20command.%20The%20results%2C%20if%20any%2C%20should%20be%20discarded.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EAs%20Microsoft%20website%20suggested%2C%20I%20tried%20an%20update%20to%20Cummulative%20Update(CU6)%20and%20changed%20to%2013.0.5292.0%20It%20says%20CU1%20update%20has%20to%20fix%20it%20but%20doesn't%20solve%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20query%20creates%20a%20dump%20file%2C%20and%20the%20log%20has%20the%20following%20message%3A%3C%2FP%3E%3CP%3ESqlDumpExceptionHandler%3A%20Process%20ID%20generated%20fatal%20exception%20c0000005%20EXCEPTION_ACCESS_VIOLATION.%20SQL%20Server%20is%20terminating%20this%20process.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20same%20update%20query%20works%20on%20other%20table%20in%20the%20same%20database.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20great.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1392169%22%20slang%3D%22en-US%22%3ERe%3A%20Help%20-%20Cannot%20continue%20the%20execution%20because%20the%20session%20is%20in%20the%20kill%20state.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1392169%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F336596%22%20target%3D%22_blank%22%3E%40shah_chandra%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheck%20you%20have%202016-SP2%20-CU12%20installed.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F4536648%2Fcumulative-update-12-for-sql-server-2016-sp2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F4536648%2Fcumulative-update-12-for-sql-server-2016-sp2%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I try to execute a update query in SQL Server 2016 (v13.0.5026.0) and get these error messages:

 

UPDATE tableName SET fieldName1 ='a long query with some html tags and all it has 3600 chars' WHERE fieldName2  = 12345

 And get this error,

Msg 596, Level 21, State 1, Line 0
Cannot continue the execution because the session is in the kill state.

Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

As Microsoft website suggested, I tried an update to Cummulative Update(CU6) and changed to 13.0.5292.0 It says CU1 update has to fix it but doesn't solve the issue.

 

This query creates a dump file, and the log has the following message:

SqlDumpExceptionHandler: Process ID generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

 

The same update query works on other table in the same database.

 

Any help would be great.

1 Reply