We have just experienced this same issue on v 2.28_411b09b. Running maintenance has not helped so far as maintanance keep running for some unreasonable time. Please help resolve.
This has been resolved, the error was caused by a data element which was of float type and later changed to integer while float values were already entered.
1 Like
So how was it resolved?
1 Like
Identified the data element from the log file and changed the type to Number.
1 Like