Chapter 8: Routine operation and compatibility
When a check fails
| Symptom | Check before changing data |
|---|---|
| Encryption mismatch or FI_CRYPT | Exact system passphrase, effective group and file keys, registration, and administration tree |
| A file remains encrypted after a planned decryption | Replacement import completed; no individual key or inherited group key remains effective |
| A file remains unencrypted after a planned encryption | Eligible organization, saved passphrase and key settings, correct database and application selection, Replace rather than Merge |
| Fewer records after import | Correct CSV and heading choice, complete export, import errors, file selection, duplicate-key errors, and matching structures |
| Missing index or failed index verification | Follow Decide whether to rebuild a missing or damaged index; rebuild from a copy of the original datafile before considering physical recovery |
| Different path from the example | APPXPATH, APPX_0SA_PATH, file and group path overrides, and the actual export location |
| CSV is readable although the APPXIO file is encrypted | Expected export behavior; protect the CSV separately |
Keep the failing log and original copies. Correct an identified configuration problem before repeating a destructive import or changing keys.