Json converter error: Object serialized to Integer. JObject instance expected

Follow

Adam Bukowski

• March 08, 2024 08:25

Hello, our Chinese partner has this error while parsing WSJF files which work perfectly fine on my machine with Norwegian locale:

2024-03-07T16:25:53.5426073+08:00;;Virinco.WATS.Logging.Client Error: 0 : 2024-03-07T16:25:53.5436034+08:00;;Message="An error occured during file conversion, see inner exception for details";
{"ClassName":"System.ArgumentException","Message":"Object serialized to Integer. JObject instance expected.","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   在 Virinco.Newtonsoft.Json.Linq.JObject.FromObject(Object o, JsonSerializer jsonSerializer)\r\n   在 Virinco.WATS.Integration.JsonConverter.WATSStandardJsonConverter.ParseStep(JObject jObject, SequenceCall seqCall)\r\n   在 Virinco.WATS.Integration.JsonConverter.WATSStandardJsonConverter.ParseRoot(JObject jToken, UUTReport result)\r\n   在 Virinco.WATS.Integration.JsonConverter.WATSStandardJsonConverter.ParseUUT(JObject jReport, TDM api)\r\n   在 Virinco.WATS.ClientService.Converter.ConvertFile(ConversionItem ci, TDM api)","RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":"8\nFromObject\nVirinco.Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=dbc0e1bf149d1e88\nVirinco.Newtonsoft.Json.Linq.JObject\nVirinco.Newtonsoft.Json.Linq.JObject FromObject(System.Object, Virinco.Newtonsoft.Json.JsonSerializer)","HResult":-2147024809,"Source":"Virinco.Newtonsoft.Json","WatsonBuckets":null,"ParamName":null}

 

I cannot identify in which part of the .json file the error is generated and what is causing it. Does anyone have an idea?

0

• 

  Sebastian Grans

  • March 08, 2024 21:01

  We are hitting the same issue.
  
  I also tried to upload the example json file that is provided on the help center page, and it also fails.
  
  On the bottom of this page.
  https://support.virinco.com/hc/en-us/articles/360015705199-WATS-Standard-JSON-Format-WSJF

  0

  Comment actions Permalink
• 

  Anders Kristiansen

  • March 11, 2024 10:30

  Hi Adam and Sebastian,

  A bug was introduced in WATS Client 6.1.105 that causes most WSJF file to give this error...

  We just released a fix for this with WATS Client 6.1.108.

  1

  Comment actions Permalink

Please sign in to leave a comment.