# Checking errors, related to #1400. Unexpected result count: 0, expected 1

**URL:** https://forum.duplicati.com/t/checking-errors-related-to-1400-unexpected-result-count-0-expected-1/5876
**Category:** Support
**Created:** [January 3, 2019, 7:19pm UTC](https://forum.duplicati.com/t/checking-errors-related-to-1400-unexpected-result-count-0-expected-1/5876 "2019-01-03T19:19:24Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [January 4, 2019, 2:40pm UTC](https://forum.duplicati.com/t/checking-errors-related-to-1400-unexpected-result-count-0-expected-1/5876/4 "2019-01-04T14:40:33Z")

</div>

> [@JonMikelV](#):
>
> I’m not sure how the #1400 error is related to snapshots but if that solved the problem, great!

I haven’t heard that anyone knows why this old error is back again, but the best-informed guess might be

> [@New warnings/errors occurring after updating to 2.0.4.5](https://forum.duplicati.com/t/new-warnings-errors-occurring-after-updating-to-2-0-4-5/5602/2):
>
> The #1400 refers to this issue: It seemed to happen when reading files that we actively being changed. Since the file shown is the transaction journal for the backup, I think this is the case as well.

and to extend the thought (at my own risk), if a snapshot freezes the file view, that might avoid the error…

---

_[View the full topic](https://forum.duplicati.com/t/checking-errors-related-to-1400-unexpected-result-count-0-expected-1/5876)._