Restoring Confluence XML site backups fails: Import failed. Check your server logs ...
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When trying to restore a XML site backup, it fails near the end of the import with the following error:
Import failed. Check your server logs for more information. Transaction rolled back because it has been marked as rollback-only
The following appears in the atlassian-confluence.log
2017-06-26 07:53:21,952 ERROR [Long running task: Importing data] [atlassian.confluence.importexport.KeyInitPostImportTask] execute Problem when init Confluence key after a site import
-- url: /confluence/longrunningtaskxml.action | traceId: 3598ae31fb625e39 | userName: admin | referer: https://www.<YOURCONFLUENCEURLhere>/confluence/admin/restore-local-file.action | action: longrunningtaskxmlDiagnosis
Run the following query to determine if you are missing or have a malformed Server ID in the database of the source instance.
select * from BANDANA where bandanakey = 'confluence.server.id';Cause
The Server ID is malformed or missing from the source instance database. When restoring a XML site backup, Confluence looks for the server ID when creating application links.
Resolution
Manually add the correct Server ID to the database.
Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Use the following insert into statement to add the Server ID.
INSERT INTO BANDANA VALUES (FREE-BANDANAID-VALUE, '_GLOBAL', 'confluence.server.id', '<string>Your-Server-ID</string>');Create a new XML site backup for restore.