FH Inspector Synchronization 2.0.6 Release Notes

If you added general notes to an inspection in FH Inspector, and if a reinspection was requested, the notes were not being forwarded to the reinspection as expected.

When you synchronized FH Inspector on the iPad with the FH database, the following series of errors appeared in succession.

Note: Sometimes these errors were preceeded by the synchroization process becoming hung. Once you canceled the synchronization, the error messages appeared.

Error 96: Nesting error, at line 31 of remotizeexpr
Error 1472: SQL statement parameter is required for non-prepared SQLEXEC() calls, at line 33 of execute
Error 107: Operator/operand type mismatch, at line 35 of execute

Synchronization was taking longer than normal, though no errors appeared. All records were being sychronized, even when no data had changed in a record since the last synchronization.

When you synchronized FH Inspector on the iPad with the FH database, an out-of-memory error appeared in the transaction summary.

ERROR Processing aborted due to error code: 43
There is not enough memory to complete this operation
at syncmainitems line 3197.

If you relicensed the FH Cloud synchronization utility, then synchronized the FH database with the FH Cloud, the following error appears.

Exception: The operation has timed out.

When you synchronized the FH database with the FH Cloud, the synchorization slowed as it processed, and then when pushing occupancy inspections to the FH Cloud, the following exception error appeared.

ERROR Processing aborted due to error code: 2071
User Thrown Error
at querycloud line 54

When you synchronized the FH database with the FH Cloud, when pushing occupancy inspections to the FH Cloud, the following exception error appeared.

ERROR Processing aborted due to error code: 1903
String is too long to fit
at addinspectionanswerelement line 2804

The following message was added to the violation notes every time a reinspection with open violations was performed.

Recheck violation record auto-generated from ManageMyInspections.com recheck request

Example: If you performed a reinspection three times, the message appeared three times in the violation notes.