Dotmim.Sync.SyncException: Error reading JObject from JsonReader
See original GitHub issueThis is appearing in our logs from time to time.
Dotmim.Sync.SyncException: Error reading JObject from JsonReader. Path '', line 0, position 0.
Once this appears for a user, it reappears repeatedly. The full strack trace
Dotmim.Sync.SyncAgent.<>c__DisplayClass53_0
<<SynchronizeAsync>b__0>d.MoveNext$catch$1 ()
System.Runtime.ExceptionServices
ExceptionDispatchInfo.Throw ()
System.Runtime.CompilerServices
TaskAwaiter.ThrowForNonSuccess (Task)
System.Runtime.CompilerServices
TaskAwaiter.HandleNonSuccessAndDebuggerNotification (Task)
System.Runtime.CompilerServices
TaskAwaiter.ValidateEnd (Task)
System.Runtime.CompilerServices
TaskAwaiter.GetResult ()
Dotmim.Sync.SyncAgent
<SynchronizeAsync>d__53.MoveNext ()
System.Runtime.ExceptionServices
ExceptionDispatchInfo.Throw ()
System.Runtime.CompilerServices
TaskAwaiter.ThrowForNonSuccess (Task)
System.Runtime.CompilerServices
TaskAwaiter.HandleNonSuccessAndDebuggerNotification (Task)
System.Runtime.CompilerServices
TaskAwaiter.ValidateEnd (Task)
Wbl.Services.DataService
<SyncAsync>d__44.MoveNext ()
We’ve had a report from one company impacted with this issue, that their machines have not been able to sync to each other for a few days. All their data appears to have synced to the server, but we can’t be sure.
Should we handle this exception in some way other than just logging it?
We have on the client
Dotmim.Sync.Sqlite 0.9.1
Dotmim.Sync.Web.Client 0.9.1
on the server
Dotmim.Sync.SqlServer.ChangeTracking 0.9.1
Dotmim.Sync.Web.Server 0.9.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
SyncException HttpResponseContextException · Issue #622
Hello there Mimetis, I tried it with one table (My users table) and got the following error: Dotmim.Sync.SyncException: Required property ...
Read more >Error reading JObject from JsonReader. Current ...
Cannot deserialize the current JSON array (e.g. [1,2,3] ) into type 'MMI_SpeechRecog.Model.LocationData' because the type requires a JSON object ...
Read more >Error Reading JObject from JsonReader
The error is caused by a file not being read properly (most likely due to it being corrupted in some way.) The fix...
Read more >Dotmim.Sync.SyncException: SQLite Error 14
On Broker machine event viewer : Dotmim.Sync.SyncException: SQLite Error 14: 'unable to open database file'. ---> Microsoft.Data.Sqlite.
Read more >Error reading JObject from JsonReader when starting ...
Solution: 1. Close Trados Studio 2021 and the error message 2. Go to C:\Users\%username%\AppData\Roaming\SDL Community\AppStore Integration ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

let me know 😃
Apologies; I’m struggling to understand. I’ve changed the SQL Server retention period to 60 days for each company database. Those companies that were out of date when the retention period was 14 days, still have local data, but have not been able to sync due to this issue.
When they get the version that allows them to sync, they will be within the new 60 days retention period. For those companies, how will DMS handle data that has not been synced for more than 14 days but less than 60 days?
EDIT: The big concern is for those companies that do all data entry on one machine. We can’t lose their data when they try to sync.