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

**URL:** <https://community.cdata.com/t/sync-0-failed-to-cache-row-xxxx-null/1064>\
**Category:** CData Sync\
**Tags:** sql, question, cdata-sync\
**Created:** [March 25, 2025, 12:57pm UTC](https://community.cdata.com/t/sync-0-failed-to-cache-row-xxxx-null/1064 "2025-03-25T12:57:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jackolas](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@Jackolas](https://community.cdata.com/u/Jackolas)\
**Post date:** [March 25, 2025, 12:57pm UTC](https://community.cdata.com/t/sync-0-failed-to-cache-row-xxxx-null/1064/1 "2025-03-25T12:57:56Z")

</div>

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

 ![2b0b3716-5ad9-4871-83ff-5ed75942a8b7.png](https://us1.discourse-cdn.com/cdata/original/2X/7/7cb22f7a83540a3be977bc90d5b0be161ce4852b.png)

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&nbsp;&nbsp; &nbsp;2&nbsp;&nbsp; &nbsp;[|Q-Id| T-Id]&nbsp;&nbsp; &nbsp;[|Q-Id]&nbsp;&nbsp; &nbsp;[SQL |Bulk &nbsp;] 15 rows are being committed.  
> 2025-03-25T12:34:16.494+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[&nbsp; &nbsp;2| &nbsp; &nbsp;0| 1164]&nbsp;&nbsp; &nbsp;[CORE] [RealDB:SQLServer]Starting WriteToServer  
> 2025-03-25T12:34:16.494+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[&nbsp; &nbsp;2| &nbsp; &nbsp;0| 1164]&nbsp;&nbsp; &nbsp;[CORE] [RealDB:SQLServer]Invoke WriteToServer  
> 2025-03-25T12:34:16.508+0100&nbsp;&nbsp; &nbsp;1&nbsp;&nbsp; &nbsp;[&nbsp; &nbsp;2| &nbsp; &nbsp;0| 1164]&nbsp;&nbsp; &nbsp;[CORE] [RealDB:SQLServer]Invoke WriteToServer is failed. null  
> 2025-03-25T12:34:16.508+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[&nbsp; &nbsp;2| &nbsp; &nbsp;0| 1164]&nbsp;&nbsp; &nbsp;[CORE] [RealDB:SQLServer]Invoking rollbackTransaction.&nbsp;  
> 2025-03-25T12:34:16.509+0100&nbsp;&nbsp; &nbsp;0&nbsp;&nbsp; &nbsp;[|Q-Id| T-Id]&nbsp;&nbsp; &nbsp;[|Q-Id]&nbsp;&nbsp; &nbsp;[SQL |Bulk &nbsp;] Failed to cache row [15]&nbsp;  
> 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&nbsp;&nbsp; &nbsp;1&nbsp;&nbsp; &nbsp;[2|Q-Id| T-Id]&nbsp;&nbsp; &nbsp;[2|Q-Id]&nbsp;&nbsp; &nbsp;[SQL |Bulk &nbsp;] [Table ContainsDDL] Failed to cache row [15] null  
> 2025-03-25T12:34:16.509+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[&nbsp; &nbsp;2| &nbsp; &nbsp;0| 1164]&nbsp;&nbsp; &nbsp;[CORE] [RealDB:SQLServer]Invoking rollbackTransaction.&nbsp;  
> 2025-03-25T12:34:16.509+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[2|Q-Id| T-Id]&nbsp;&nbsp; &nbsp;[2|Q-Id]&nbsp;&nbsp; &nbsp;[SQL |Bulk &nbsp;] Table ContainsDDL Rollback transaction.  
> 2025-03-25T12:34:16.509+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[2|Q-Id| T-Id]&nbsp;&nbsp; &nbsp;[2|Q-Id]&nbsp;&nbsp; &nbsp;[SQL |Bulk &nbsp;] Temporary Table Mode Unable to transfer rows. Failed to cache row [15] null  
> 2025-03-25T12:34:16.509+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[2|Q-Id| T-Id]&nbsp;&nbsp; &nbsp;[2|Q-Id]&nbsp;&nbsp; &nbsp;[SQL |Bulk &nbsp;] Temporary Table Mode Unable to transfer rows. Failed to cache row [15] null  
> 2025-03-25T12:34:16.509+0100&nbsp;&nbsp; &nbsp;5&nbsp;&nbsp; &nbsp;[2|Q-Id| T-Id]&nbsp;&nbsp; &nbsp;[2|Q-Id]&nbsp;&nbsp; &nbsp;[SQL |Bulk &nbsp;] Table ContainsDDL Verify and begin transaction.

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

Anyone has an idea where is should look?

---

<div class="post-metadata">

**Author:** ![Jackolas](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@Jackolas](https://community.cdata.com/u/Jackolas)\
**Post date:** [March 26, 2025, 9:48am UTC](https://community.cdata.com/t/sync-0-failed-to-cache-row-xxxx-null/1064/2 "2025-03-26T09:48:52Z")

</div>

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&nbsp;“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.