Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
2022-12-31 15:30:01.590 AWEKAS: Exception = Type definitions should start with a '{', expecting serialized type 'AwekasResponse', got string starting with: 20221231 02:25:00 20221231 04:29:07
Yeah I've had this for a couple of days now - since Thursday evening. I think it may be a problem at their end as you can see the odd 500 response from their servers in MXdiags logs.
Unless they've changed their API and we don't know about the change?
I see the same error in my current MXdiags. The oldest file in my MXdiags folder is Dec 23rd and there are no such errors in it, so fairly recent issue. The AWEKAS site seems to have all the data so uploads are ok.
<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h2>Request Timeout</h2>
<p>This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase 'Connection Timeout'.</p>
</body>
</html>
This is being returned instead of the correct JSON response. My data is generally updating though, just some missed updates.
I looked at the "Exception = Object reference not set to an instance of an object." - it's a spurious message that should not occur, the previous error should have exited the routine but didn't, hence the code trying access something that had not been initialised.
Fixed in the next release.
I've got the same problem, it started on 29th December, and they haven't received any data from me since that point. Not related to moving to the latest build. I've not changed anything at my end, apart from updating to the latest build on the 2nd. Same errors in MXdiags in both builds.
