Skip to main content
Solved

Sync – “[0] Failed to cache row [XXXX] null"

  • March 25, 2025
  • 1 reply
  • 196 views
J
Forum|alt.badge.img+1

Since the update to Sync version 25.1.9207 we are getting some strange errors from different tasks.

All these tasks worked without problems before the update.

So far i have not found any difference (except for the tables) between tasks that work and that won’t work. It even fails on small datasets (19 in this example, a 16.000.000+ tasks works without problem)

And the log also is not showing a lot of info:

2025-03-25T12:34:16.494+0100    2    [ |Q-Id| T-Id]    [ |Q-Id]    [SQL |Bulk  ] 15 rows are being committed.
2025-03-25T12:34:16.494+0100    5    [    2|    0| 1164]    [CORE] [RealDB:SQLServer]Starting WriteToServer
2025-03-25T12:34:16.494+0100    5    [    2|    0| 1164]    [CORE] [RealDB:SQLServer]Invoke WriteToServer
2025-03-25T12:34:16.508+0100    1    [    2|    0| 1164]    [CORE] [RealDB:SQLServer]Invoke WriteToServer is failed. null
2025-03-25T12:34:16.508+0100    5    [    2|    0| 1164]    [CORE] [RealDB:SQLServer]Invoking rollbackTransaction. 
2025-03-25T12:34:16.509+0100    0    [ |Q-Id| T-Id]    [ |Q-Id]    [SQL |Bulk  ] Failed to cache row [15] 
StackTrace:
Failed to rollback transaction Bulk load data was expected but not sent. The batch will be terminated.

2025-03-25T12:34:16.509+0100    1    [2|Q-Id| T-Id]    [2|Q-Id]    [SQL |Bulk  ] [Table ContainsDDL] Failed to cache row [15] null
2025-03-25T12:34:16.509+0100    5    [    2|    0| 1164]    [CORE] [RealDB:SQLServer]Invoking rollbackTransaction. 
2025-03-25T12:34:16.509+0100    5    [2|Q-Id| T-Id]    [2|Q-Id]    [SQL |Bulk  ] Table ContainsDDL Rollback transaction.
2025-03-25T12:34:16.509+0100    5    [2|Q-Id| T-Id]    [2|Q-Id]    [SQL |Bulk  ] Temporary Table Mode Unable to transfer rows. Failed to cache row [15] null
2025-03-25T12:34:16.509+0100    5    [2|Q-Id| T-Id]    [2|Q-Id]    [SQL |Bulk  ] Temporary Table Mode Unable to transfer rows. Failed to cache row [15] null
2025-03-25T12:34:16.509+0100    5    [2|Q-Id| T-Id]    [2|Q-Id]    [SQL |Bulk  ] Table ContainsDDL Verify and begin transaction.

 

I manually checked all the data and can find no difference in the data when the task was working and now

Anyone has an idea where is should look?

 

Best answer by Jackolas

I found the cause of this problem

Its a discrepancy between the Source table Field type and the target table field type.

The source field was a “decimal(4,0)” while the target field was “nvarchar(4)”.

In the previous version of Sync this was no problem and the data got transported anyway without any issue. But after the update this gives the NULL error. It seems that its now very picky that the source field type exactly matches the target field type.

 

    This topic has been closed for replies.

    1 reply

    J
    Forum|alt.badge.img+1
    • Jackolas
    • Author
    • Apprentice
    • Answer
    • March 26, 2025

    I found the cause of this problem

    Its a discrepancy between the Source table Field type and the target table field type.

    The source field was a “decimal(4,0)” while the target field was “nvarchar(4)”.

    In the previous version of Sync this was no problem and the data got transported anyway without any issue. But after the update this gives the NULL error. It seems that its now very picky that the source field type exactly matches the target field type.

     

      State of AI Data Connectivity Report: 2026 Outlook
      Terms and ConditionsCookie settingsAccessibility statement