Issue
When attempting to export a Fusion application, a 500 Internal Server Error occurs. The following message may be observed in the API response or logs:
"message": "An unknown ObjectImportExport error occurred",
"details": "Error when building export archive: KeeperErrorCode = NoNode for /collections/collection_name/state.json"This error indicates that the system was unable to build the export archive due to a missing collection reference.
Diagnosis
To confirm whether a missing collection is causing the export error:
Use the following endpoint to inspect the Solr cluster status:
https://<fusion-host>/api/solrAdmin/default/admin/collections?action=CLUSTERSTATUS&wt=jsonor in the Solr Admin UI (Cloud > Graph view), verify whether the collection listed in the error (e.g.,
collection_name) exists or not.If the collection does not appear in the graph view or in the CLUSTERSTATUS response, it no longer exists in Solr and is the likely cause of the error.
Environment
Fusion 5.x running in a Kubernetes-managed environment
Cause
The Fusion application references a Solr collection that no longer exists in the environment. When Fusion attempts to export the app, it tries to include metadata for that collection. If the collection is missing from Solr, Fusion fails to build the archive and returns a 500 error.
Resolution
Step 1: Confirm the collection is missing
Check if the missing collection is visible in the Solr Admin UI or by querying the cluster status API as shown above. If it is not present, proceed with the steps below.
Step 2: Remove the same collection reference from the Fusion app
If the collection is no longer present in Solr but still referenced in the Fusion application:
Navigate to the application in the Fusion UI.
Locate the reference to the missing collection (e.g.,
collection_name).Click the X icon next to the collection to remove it from the app configuration.
Note: There is no need to delete the collection from Solr if it is already missing. The error occurs because the reference exists in the app.
Step 3: Retry the application export
Once the same collection is deleted from Fusion UI referenced in the error and the app:
Use the Export API or Fusion UI to export the application again.
The export should now complete successfully.