topdavis 3 Posted July 4, 2021 Share Posted July 4, 2021 Any idea why I keep getting this error daily since 5/28/2021: Remove Old Sync Data failed Type definitions should start with a '{', expecting serialized type 'Foo`1', got string starting with: at ServiceStack.Text.Common.DeserializeTypeRefJson.StringToType(ReadOnlySpan`1 strType, TypeConfig typeConfig, EmptyCtorDelegate ctorFn, KeyValuePair`2[] typeAccessors) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Common\DeserializeTypeRefJson.cs:line 173 at ServiceStack.Text.Common.DeserializeType`1.StringToTypeContext.DeserializeJson(ReadOnlySpan`1 value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Common\DeserializeType.cs:line 58 at ServiceStack.Text.Json.JsonReader`1.Parse(ReadOnlySpan`1 value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Json\JsonReader.Generic.cs:line 103 at ServiceStack.Text.Json.JsonReader`1.Parse(String value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Json\JsonReader.Generic.cs:line 83 at ServiceStack.Text.JsonSerializer.DeserializeFromString[T](String value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\JsonSerializer.cs:line 47 at NanoApi.File.Read[T]() at NanoApi.JsonFile`1.Delete(Predicate`1 lambda) at Emby.Kodi.SyncQueue.Data.DbRepo.DeleteOldData(Int64 dtl) at Emby.Kodi.SyncQueue.ScheduledTasks.FireRetentionTask.Execute(CancellationToken cancellationToken, IProgress`1 progress) at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker.ExecuteInternal(TaskOptions options) Link to comment Share on other sites More sharing options...
Luke 37065 Posted July 5, 2021 Share Posted July 5, 2021 @topdavis Moving to Kodi section. Please attach the complete emby server log. thanks. Link to comment Share on other sites More sharing options...
quickmic 1344 Posted July 5, 2021 Share Posted July 5, 2021 On 7/4/2021 at 5:57 PM, topdavis said: Any idea why I keep getting this error daily since 5/28/2021: Remove Old Sync Data failed Type definitions should start with a '{', expecting serialized type 'Foo`1', got string starting with: at ServiceStack.Text.Common.DeserializeTypeRefJson.StringToType(ReadOnlySpan`1 strType, TypeConfig typeConfig, EmptyCtorDelegate ctorFn, KeyValuePair`2[] typeAccessors) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Common\DeserializeTypeRefJson.cs:line 173 at ServiceStack.Text.Common.DeserializeType`1.StringToTypeContext.DeserializeJson(ReadOnlySpan`1 value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Common\DeserializeType.cs:line 58 at ServiceStack.Text.Json.JsonReader`1.Parse(ReadOnlySpan`1 value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Json\JsonReader.Generic.cs:line 103 at ServiceStack.Text.Json.JsonReader`1.Parse(String value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\Json\JsonReader.Generic.cs:line 83 at ServiceStack.Text.JsonSerializer.DeserializeFromString[T](String value) in C:\BuildAgent\work\912418dcce86a188\src\ServiceStack.Text\JsonSerializer.cs:line 47 at NanoApi.File.Read[T]() at NanoApi.JsonFile`1.Delete(Predicate`1 lambda) at Emby.Kodi.SyncQueue.Data.DbRepo.DeleteOldData(Int64 dtl) at Emby.Kodi.SyncQueue.ScheduledTasks.FireRetentionTask.Execute(CancellationToken cancellationToken, IProgress`1 progress) at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker.ExecuteInternal(TaskOptions options) Could be a special charecter issue: 'Foo`1' -> "`" Link to comment Share on other sites More sharing options...
topdavis 3 Posted July 6, 2021 Author Share Posted July 6, 2021 Emby Server Log file embyserver.txt Link to comment Share on other sites More sharing options...
Luke 37065 Posted July 6, 2021 Share Posted July 6, 2021 Under the server's data folder there should be a syncdata sub-folder. You could try deleting that, then restarting the server and see if that helps. Link to comment Share on other sites More sharing options...
topdavis 3 Posted July 22, 2021 Author Share Posted July 22, 2021 I am so sorry I forgot to respond to this sooner, but deleting and restarting fixed the problem and it has not returned since doing so. 1 Link to comment Share on other sites More sharing options...
Luke 37065 Posted July 22, 2021 Share Posted July 22, 2021 Thanks for the feedback. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now