Did this problem start happening immediately after the upgrade, or were you collecting data for a period of time, and then it started happening?
If it happened immediately after the upgrade, please invite me ( mitche...@gmail.com ) as a developer so that I can confirm that the AppEngine instance is still in good condition.
Assuming I determine that everything is OK, or if this started happening after collecting data after the upgrade, you should then upgrade to ODK Aggregate 1.4.5.
The error message may indicate that there is a data corruption issue in one of your submissions. The ODK Aggregate 1.4.5 release provides better logging of the details of that problem.
I set up the ODK Aggregate with Google App Engine as the back end server in 2013. The ODK aggregate was 1.3.4 version. I upgraded it upto 1.4.1. Now, ODK Aggregate cannot export the forms to CSV neither it is publishing the forms as Google Spreadsheets or Fusion tables.
I was told to upgrade the ODK Aggregate to the latest version but since I am not able to back up the data (one of the questionnaires has more than 15,000 entries), is it safe to upgrade the Aggregate without backing up the data?
I tried using ODK Briefcase to pull the data but it failed after fetching 1400 instances.
And when I click the publish button in the Aggregate, the following error pops up;
Error: Problem persisting data or accessing data (Somehow DB entities for publisher got into problem state)
You received this message because you are subscribed to the Google Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
University of Washington
Thank You for your quick response.
We were collecting data for a long time now. The problem of exporting to CSV or publishing the data started before upgrading the Aggregate.
I could upgrade 2 versions up (currently we are using version 1.4.1). We don't want to take risk of upgrading to the latest versions without backing up the data.
Is there any way to store the data before proceeding to the upgrading of the Aggregate?
And also is there any way to find out the corrupted data in the Submissions?
On Wednesday, April 8, 2015 at 3:16:48 PM UTC-4, Mitch Sundt wrote:
> On Wed, Apr 8, 2015 at 10:45 AM, wrote: