Error publication

[PadmaPriya · Accepted solution]

Hello @MCO1 

Error:

Command=Export app;Result=400;ResultText=Error: PersistenceFailed    322ba881-0e69-46ab-a6c2-3122ce2f2029    10f39b74-01a4-4cb4-a31c-47f14839b872    0    SEMARK    mercanza    ec5191f5-c425-40bf-8a18-e9734813b011    CMC_GeneraAportaciones_B    Repository    ManagementAccess    /qrs/app/ec5191f5-c425-40bf-8a18-e9734813b011/export    Export app    400     The "GetAll" operation failed. (HTTP code: 400)    f6624cce-6b27-4f04-87e6-8b855a92da07

Please follow the below solution:

1. Stop Rim node and take Repository backup
2. Uninstall Rim node, removing local data and certificates
3. Stop Central node and backup Repository
4. Remove Central node transaction data from C:\ProgramData\Qlik\Sense\Repository\Transactions
5. Create "_operation.qrs" empty file in the same Transactions folder to reset sync on Central node
6. Use the custom recurse_cleanup.sql script attached to remove orphans and other lint from the Repository (directly in pgAdmin)
7. Remove all sync sessions using the SQL script in Appendix A, changing the date to current date for a thorough cleanup
   1. This step essentially returns the Central node to a "never synced" state. These sync sessions can considerably bloat the Repository over time
8. Start Central node services and wait for Startup Phase Complete in Repository Trace System log
9. Test all previously non-working operations and confirm the issues have disappeared
10. Remove the Rim node from QMC
    1. Trying to remove the Rim node before clean-up operations can fail, in which case the Rim node will have to be manually removed from the Repository, thus avoided
11. Install Rim node with Engine + Proxy roles
12. Disable custom sync rule that makes all apps available on Rim nodes as well, this is done to avoid binary app sync before the App storage path can be changed on the Rim node. Custom rule name is ResourcesOnNonCentralNodes
    1. Customer had a small C: drive that would've been quickly filled by sync transactions and apps if the rule is not disabled
13. Add Rim node to QMC and configure its Engine to point to the new App storage folder
14. Restart services on Rim node and verify that the new Engine settings have synced
    1. Open pgAdmin on Rim node (even with services started) and check the DocumentDirectory column in EngineServiceSettings table
15. Enable previously disabled Sync Rule to begin binary app sync and monitor the appropriate app folder on Rim node for content to start appearing
16. Once all sync operations are complete, take backups of both Repositories in this clean and operational state

in simple you may restore the ProgreSQL Database.

Thanks,

Padma Priya