CDC not working on SQL SERVER 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-1083046%22%20slang%3D%22en-US%22%3ECDC%20not%20working%20on%20SQL%20SERVER%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083046%22%20slang%3D%22en-US%22%3E%3CP%3EI%20cannot%20make%20CDC%20on%20SQLSERVER%202019%20to%20work%20and%20facing%20follow%20error%3A%3C%2FP%3E%3CP%3EJob%20Log%20File%20Viewer%3A%3C%2FP%3E%3CPRE%3E%3CSPAN%20class%3D%22pln%22%3EThe%20call%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22kwd%22%3Eto%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20sp_MScdc_capture_job%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22kwd%22%3Eby%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20the%20Capture%20Job%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22kwd%22%3Efor%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22kwd%22%3Edatabase%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22str%22%3E'XXXX'%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20failed%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E.%3C%2FSPAN%3E%3C%2FPRE%3E%3CP%3ESQL%20Server%20Log%20File%20Viewer%3A%3C%2FP%3E%3CPRE%3E%3CSPAN%20class%3D%22pln%22%3EProcess%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E151%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20generated%20fatal%20exception%20c000000d%20EXCEPTION_INVALID_CRT_PARAMETER%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E.%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20SQL%20Server%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22kwd%22%3Eis%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20terminating%20this%20process%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E.%3C%2FSPAN%3E%3C%2FPRE%3E%3CP%3ESQLSERVER%20%40%40version%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%3CSPAN%20class%3D%22pln%22%3EMicrosoft%20SQL%20Server%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E2019%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3ERTM-GDR%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E)%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3EKB4517790%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E)%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E-%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22lit%22%3E15.0.2070.41%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3EX64%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E)%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20%20%20Oct%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E28%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22lit%22%3E2019%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22lit%22%3E19%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E%3A%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E56%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E%3A%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E59%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20%20%20Copyright%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3EC%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E)%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22lit%22%3E2019%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20Microsoft%20Corporation%20%20Enterprise%20Edition%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E64%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E-%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3Ebit%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E)%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22kwd%22%3Eon%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20Windows%20Server%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E2019%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3E%20Standard%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E10.0%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E%26lt%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3EX64%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E%26gt%3B%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3EBuild%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22lit%22%3E17763%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E%3A%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E)%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pun%22%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22pln%22%3EHypervisor%3C%2FSPAN%3E%3CSPAN%20class%3D%22pun%22%3E)%3C%2FSPAN%3E%20%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20Google%20the%20error%20and%20it%20seem%20to%20be%20a%20bug%20from%202016%20version%20and%20prior%20which%20already%20fixed%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22post-text%22%3E%3CP%3EDid%20anybody%20face%20that%20issue%3F%20I%20think%20that%20might%20be%20something%20related%20to%20a%20bug%20which%20prevent%20my%20CDC%20to%20start.%3C%2FP%3E%3C%2FDIV%3E%3CDIV%20class%3D%22post-taglist%20grid%20gs4%20gsy%20fd-column%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22post-taglist%20grid%20gs4%20gsy%20fd-column%22%3EP%2Fs%3A%20I%20also%20attached%20an%20image%20of%20Log%20File%20Viewer%20which%20execute%20the%20CDC%20stored%20Procedure%20and%20exception%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

I cannot make CDC on SQLSERVER 2019 to work and facing follow error:

Job Log File Viewer:

The call to sp_MScdc_capture_job by the Capture Job for database 'XXXX' failed.

SQL Server Log File Viewer:

Process 151 generated fatal exception c000000d EXCEPTION_INVALID_CRT_PARAMETER. SQL Server is terminating this process.

SQLSERVER @@version:

 

Microsoft SQL Server 2019 (RTM-GDR) (KB4517790) - 15.0.2070.41 (X64)   Oct 28 2019 19:56:59   Copyright (C) 2019 Microsoft Corporation  Enterprise Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor) 

 

I've tried Google the error and it seem to be a bug from 2016 version and prior which already fixed

 

Did anybody face that issue? I think that might be something related to a bug which prevent my CDC to start.

0 Replies