Unable to cast object of type 'Newtonsoft.Json.Linq.JValue' to type 'Newtonsoft.Json.Linq.JArray'.

  • 167Views
  • Last Post 24 June 2019
  • Topic Is Solved
0
votes
Burke Autrey posted this 15 June 2019

Been getting this error all day.  Please help.  None of my integrations are working.

Unable to cast object of type 'Newtonsoft.Json.Linq.JValue' to type 'Newtonsoft.Json.Linq.JArray'.

Order By: Standard | Newest | Votes
0
votes
Burke Autrey posted this 15 June 2019

It just makes it worse to be charged for my subscription during an outage with no response from anyone at SkyVia.

0
votes
Burke Autrey posted this 15 June 2019

Well, apparently some or all of the integration is working and the error message may just be related to the final display of the results of the integration (e.g. number of objects added, updated, etc.).  Not sure but it looks that way as some data is getting through even though the state of the last run is Failed.

Would be nice to hear something from the crew at SkyVia.

0
votes
Mariia Zaharova posted this 18 June 2019

Dear Burke!

The error is related to some QuickBooks field(s) and the data being retrieved for this field(s). We could not reproduce such an issue with our QuickBooks instance. If you encounter this issue again, please let us know and allow us to run your package in the test mode for deeper investigation and fixing it.

 

Best regards, 

Mariia

 

0
votes
Burke Autrey posted this 18 June 2019

That's just not likely Mariia.  The integration stopped working for three days (3am GMT-5 on June 14 to 3am GMT-5 on June 17) and just started working again with no changes by me and, presumably, no changes by Intuit/Quickbooks.  Was there an update by Skyvia about the time this started?  Was there a fix pushed at the end of this time that got it working again?

You are welcome to run my package in test mode if you think that will help.

 

Burke

0
votes
Mariia Zaharova posted this 19 June 2019

There were no fixes regarding this error for the last few days. The last Skyvia update was done on June 11.

Test run will definitely help if the error occurs permanently.

Unfortunately, at the moment we cannot tell you an exact reason of the error and cannot investigate it further as it does not occur anymore in your packages.

 

Best regards,

Mariia

0
votes
Burke Autrey posted this 22 June 2019

May I suggest that you instrument the code/product such that errors like this are logged so you can understand what happened and make the product less fragile?  You are saying that neither of us made any changes and I started seeing errors.  And neither of us made any changes and the errors stopped.  If all of that is true and QB made no changes, then there must be an error in the environment (network, disk, etc.).  If you have no logs of any errors and only surface runtime errors to the user with no knowledge of it, and can only troubleshoot if the error persists, then you have an application that is not safe for your users to rely on for production tasks.  That's not a very comforting situation.  You don't want that.  Customers will abandon you for more stable alternatives.

Will mark this as Is Solution but you should not consider it closed.  Reach out to me if you'd like to discuss.

 

Burke

0
votes
Mariia Zaharova posted this 24 June 2019

Dear Burke!

 

Thank you for your response.

 

We do have logging and in most cases that's enough for fixing an issue. But in some cases issues depend on some specific custom fields, objects, settings or data being transfered between data sources, and this requires additional investigation for better result.

Thank you for using Skyvia, we appreciate your choice.

We are doing our best to improve Skyvia and make our service better for your convenience. 

 

Best regards,

Mariia

Close