SQL Server 2019: Logreader broken RRS feed

  • General discussion

  • The transactional log reader seems to be broken in sql server 2019 RTM.

    I upgraded my test environment and run in the problem that the second step in the sql server agent job (run agent) is only doing retries because it fails.

    The only output you get (even with Outputverboselevel 2) is the one below with an empty text '' message.

    2019-11-12 10:16:30.566 Microsoft SQL Server Log Reader Agent 15.0.2000.5

    2019-11-12 10:16:30.566 Copyright (c) 2016 Microsoft Corporation

    2019-11-12 10:16:30.582

    2019-11-12 10:16:30.582 The timestamps prepended to the output lines are expressed in terms of UTC time.

    2019-11-12 10:16:30.582 User-specified agent parameter values:

                                        -Publisher WIN-4LTCDQ485TB

                                        -PublisherDB test

                                        -Distributor WIN-4LTCDQ485TB

                                        -DistributorSecurityMode 1


                                        -Outputverboselevel 2

                                        -Output C:\Temp\output.txt

    2019-11-12 10:16:30.597 Status: 0, code: 20015, text: ''.

    2019-11-12 10:16:30.597 Disconnecting from OLE DB  ''

    Problem can also be reproduced on a fresh installation of sql server 2019 on a fresh windows server 2019 vm.

    Can someone else confirm or has a working logreader on sql server 2019?

    Tuesday, November 12, 2019 10:38 AM

All replies

  • It is hard to say what is going on here.

    What you need to do is extract the job step, and locate your logreader.exe binary. Then from the command line pass the parameters to this binary and see what output you get.

    Tuesday, November 12, 2019 4:55 PM
  • I tried that but output gave only the same information from above.

    I was in contact with Microsoft now and it seems to be a bug in the installer from Sql Server 2019.

    The logreader.exe is searching for a file in the folder 

    C:\Program Files\Microsoft SQL Server\150\COM\Resources\1031

    , which is a localized folder for german.

    Sql Server was installed in english, so the file is in C:\Program Files\Microsoft SQL Server\150\COM\Resources\1033

    After copying the folder to 1031, it works.

    So it is a localization bug in the sql server installer, Microsoft is investigating it now and I think they will fix it in the next cu. 

    Tuesday, November 12, 2019 6:02 PM
  • Please try to open a command prompt and run the logread.exe with the parameters directly, see what the error is .

    I suspect your binary files have some issues.

    Wednesday, November 20, 2019 5:35 PM
  • The same bug in SQL 2019 RTM 15.0.2000.5 and replication


    Agent message code 20084. The process could not connect to Distributor 'DIST01'.


    Status: 0, code: 20015, text: ''

    In my case folder 1045 (Polish) was missing.

    C:\Program Files\Microsoft SQL Server\150\COM\Resources\1033 - default english

    C:\Program Files\Microsoft SQL Server\150\COM\Resources\1045 - MISSING !!!

    After copy 1033 with name 1045 everything works OK.

    Process Monitor from sysinternals is usefull in this kind of errors


    Friday, January 3, 2020 10:57 PM