Log Shipping Agent Error Message

  • sidewing

    Old Hand

    Points: 333

    Hi all,

    I am trying to configure log shipping and getting following error in agent job history.(SQL Server 2019)

    There was no problem with sql server 2017 and 2016 in same configuration.

    The backup file was created normally but error message is logged.

    ----------------------------------------------------------------------------------------------------------------

    2019-12-04 11:16:50.90 Starting transaction log backup. ID: '26c94b60-7380-4ddd-8dc7-ae2ae70630c7'

    2019-12-04 11:16:50.90 *** ERROR: Unable to log history / error messages.(Microsoft.SqlServer.Management.LogShipping) ***

    2019-12-04 11:16:50.90 *** error: Failed to convert parameter value from SqlGuid to String.(System.Data) ***

    2019-12-04 11:16:50.90 *** error: The object must implement IConvertible.(mscorlib) ***

    2019-12-04 11:16:50.90 Retrieving backup settings ID: '26c94b60-7380-4ddd-8dc7-ae2ae70630c7'

    2019-12-04 11:16:50.91 *** ERROR: Unable to log history / error messages.(Microsoft.SqlServer.Management.LogShipping) ***

    2019-12-04 11:16:50.91 *** error: Failed to convert parameter value from SqlGuid to String.(System.Data) ***

    2019-12-04 11:16:50.91 *** error: The object must implement IConvertible.(mscorlib) ***

    -----------------------------------------------------------------------------------------------------------------

    Can anyone tell me what is the problem in this?

     

    • This topic was modified 7 months ago by  sidewing.
    • This topic was modified 7 months ago by  sidewing.
    • This topic was modified 7 months ago by  sidewing.
    • This topic was modified 7 months ago by  sidewing.
    • This topic was modified 7 months ago by  sidewing.
    • This topic was modified 7 months ago by  sidewing.
  • sidewing

    Old Hand

    Points: 333

    In addition, I found the following phenomena:

    Column [last_backup_file], [last_backup_date] of msdb.dbo.log_shipping_primary_databases and msdb.dbo.log_shipping_monitor_primary table is not updated. It's NULL.

    It seems to be related to the error message noted above.

     

  • Leo.Miller

    SSChampion

    Points: 12855

    This is a known issue, and we have also seen it, plus seen it in SQL Server 2017, although I can't recall at what CU level. We found that Log Shipping works, end to end, and it's only the write of log that isn't working. From what we have been told MS are not looking to fix it. We did some digging and from what we could find, the error is coming out of a stored procedure that's sitting in the Resource DB, and we don't have visibility on this or the ability to fix it.

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

  • Leo.Miller

    SSChampion

    Points: 12855

    You may want to move this topic to the SQL 2019 forum here:  https://www.sqlservercentral.com/forums/forum/sql-server-vnext?view=all

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply