This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 49%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGC%3C/text%3E%3C/svg%3E)
Dear colleagues,
Since some days ago one of our data insert process on SQL Server (based on SQL Intgeration Services) is failing with the error provided below.
We have followed all the suggestions displayed on the message (running DBCC CHECKDB, install latest CU) but error has appeared again after some days. Any idea about how to manage such a kind of error? Environment info: Microsoft SQL Server 2019 (RTM-CU24) (KB5031908) - 15.0.4345.5 (X64) Regards
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Cannotcontinue the execution because the session is in the kill state.".An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "A systemassertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a softwarebug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps toMicrosoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest ServicePack or in a Hotfix from Technical Support.".An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Location:"sql\\ntdbms\\storeng\\dfs\\trans\\xact.cpp":7960Expression: ITaskProxy::FIsCurrentTaskProxy (m_owningTaskProxy)
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
Additional SQL Server features and topics not covered by specific categories
Hi Greg,Yes, fast load was in use and we had the same idea. We change it to normal load and error seems to have disappeared. We will have to wait some more days to be sure that error has disappeared completely as it appeared intermitently but from my previous problems using "fast load" the trick seems promising.Many thx for you support
Happy to help.
Hi @Gonzalez Comas Alfons (F4E),
If you have got the dump file, you may contact Microsoft Support to help analyze it.
Regards，
Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.
Assertion errors are typically tokens of bugs in SQL Server. Since you have installed the most recent CU, I think you are best off opening a support case.
What does it say in the SQL Server error log?
Also, what options are being used in the OLE DB Destination? (e.g., is Fast Load being used?)