Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Import to cloud failed. Message: com.atlassian.confluence.importexport.v2.ImportExportException: ent

Bruce Yen March 23, 2021

Import to cloud failed. Message:

com.atlassian.confluence.importexport.v2.ImportExportException: entities.xml not found

The process almost finished, stopped at 83%, when through

export database (ok)

uploaded file (ok)

migrating to cloud (failed)

 

I was monitoring the migration/exports/extitlies.xml went up to about 262M. (the Data Migration progress detail line shows 23M). Then it was removed and migration failed.

Can someone share info. if you experience similar situation? Is there any limitation of free tier account (like size, timeout, etc.?) Thanks.

7 answers

3 accepted

2 votes
Answer accepted
Sri Kumar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 24, 2021

Hi All,

Good day. We are investigating the issue, We will keep you guys posted on this thread 

-Sri

Bruce Yen March 24, 2021

Fixed. Thanks.

1 vote
Answer accepted
Sri Kumar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 24, 2021

Hi All,

Please note that a Fix has been deployed. Please re-try the migration. It should succeed now.

Thank you

-Sri

Bruce Yen March 24, 2021

Fixed. I have successfully migration from server (5.10.0) to Cloud.

Thank you very much!

 

Bruce

Like Sri Kumar likes this
Edgars Vincans March 24, 2021

Same. Migrated without issues.

Thanks!

Like Sri Kumar likes this
0 votes
Answer accepted
Bruce Yen March 24, 2021

According to Sri:

 

Hi All,

Please note that a Fix has been deployed. Please re-try the migration. It should succeed now.

Thank you

-Sri

Alec Keeler March 24, 2021

First one of my 2 that failed tried and now works, about to try the second one

Didn't have to update the Cloud Migration Assistant app must be Atlassian end

Like Sri Kumar likes this
3 votes
Edgars Vincans March 23, 2021

Tried migrating from 7.4.5 to cloud (standard plan) and was getting same failure message.

The same message appears not only through the 'Cloud Migration Assistant' but also through the manual steps of exporting the individual space & trying to import it in the cloud.

I don't think you're limited with with your 'free tier account'

Alec Keeler March 24, 2021

Yeah I tried the manual export and import but didn't work for me as we are on 6.13.6 and it needs 6.14!!

At least I know that even if we were on 6.14 that wouldn't have helped

Alec

Like Bruce Yen likes this
Edgars Vincans March 24, 2021

Aha. We even made a copy of production instance. Upgraded it from 7.4.5 to 7.4.8, because in 7.4.6 there were some xml export fixes. But that also didn't help

Like Bruce Yen likes this
2 votes
Alec Keeler March 24, 2021

Seeing the same error trying to migrate from 6.13.6 on 2 of my 28 spaces

Trial migration last week worked fine now fails when trying to do final real migration

I am also seeing issues using the rest API from python (i have a script that checks for various things and fixes broken emoticons)

This script also worked last week but now fails  

This was attempting to download a page in storage format (using the atlassian api pip module for python)

confluence.get_page_by_id(page_id=my_page_id,expand='body.storage,version')

which gets converted to the API call

https://<youtsite>.atlassian.net/wiki/rest/api/content/<pageid>?expand=body.storage%2Cversion

Which returns the error

{"statusCode":500,"message":"org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only"}

The script iterates all the pages in a space, API call works for most but not for some

Alec Keeler March 24, 2021

Found that API issue was due to a JIRA link not being fixed, manually edited jira link on problem page and that API call now works

Like Bruce Yen likes this
Alec Keeler March 24, 2021

Thats despite having run JIRA Macro repair twice, page didn't respond correctly to API call until I manually edited the JIRA link

So API issue could well be a red herring for migration problem

But I still get the following any time I try to migrate the 2 spaces that failed

Import to cloud failed. Message: com.atlassian.confluence.importexport.v2.ImportExportException: entities.xml not found

Like Bruce Yen likes this
Alec Keeler March 24, 2021

yep API possibly red herring, API scripts works but trying migration

 

2021-03-24 08:12:49,719 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6180: "Adds a multi-column index to content table that speeds up many common queries." - Ok
2021-03-24 08:12:49,719 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6175: "Upgrade to build number: 6175" - Ok
2021-03-24 08:12:49,719 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6169: "Upgrade to build number: 6169" - Ok
2021-03-24 08:12:49,719 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6161: "Upgrade to build number: 6161" - Ok
2021-03-24 08:12:49,719 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6139: "Upgrade to build number: 6139" - Ok
2021-03-24 08:12:49,720 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6122: "Remove the legacy Confluence Thread Dump Plugin from the user installed plugins" - Ok
2021-03-24 08:12:49,720 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6116: "Upgrade to build number: 6116" - Ok
2021-03-24 08:12:49,722 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 6112: "Finds all attachments that are missing a content_status and marks them as current" - Ok
2021-03-24 08:12:49,722 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5914: "Upgrade the customizations from the ondemand doctheme to the format expected by the standard confluence doctheme" - Ok
2021-03-24 08:12:49,724 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5702: "Enables membership aggregation across directories" - Ok
2021-03-24 08:12:49,724 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5613: "Upgrade to build number: 5613" - Ok
2021-03-24 08:12:49,724 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5612: "Upgrade to build number: 5612" - Ok
2021-03-24 08:12:49,724 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5604: "Upgrade to build number: 5604" - Ok
2021-03-24 08:12:49,725 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5603: "Upgrade to build number: 5603" - Ok
2021-03-24 08:12:49,725 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5602: "Upgrade to build number: 5602" - Ok
2021-03-24 08:12:49,725 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 5601: "Upgrade to build number: 5601" - Ok
2021-03-24 08:12:49,725 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 4984: "Upgrade to build number: 4984" - Ok
2021-03-24 08:12:49,726 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 4950: "Upgrade to build number: 4950" - Ok
2021-03-24 08:12:49,726 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 4526: "Remove the legacy remotable apps plugin from the user installed plugins" - Ok
2021-03-24 08:12:49,726 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Build number 4517: "Migrate all Page Templates using a storage format round-trip conversion" - Not Ok
2021-03-24 08:12:49,726 INFO [pool-74-thread-1] [atlassian.confluence.upgrade.AbstractUpgradeManager] getExportBuildNumber Backward compatibility for export: "Migrate all Page Templates using a storage format round-trip conversion" prevents compatibility before 4517
2021-03-24 08:13:03,252 WARN [alert-dispatch:thread-1] [confluence.alert-log] log 1616573583251 ; WARNING ; JVM ; JVM-1002 ; Garbage collection exceeded time limit ; not-detected ; ; ; {"durationInMillis":3798,"windowInMillis":20000,"limitPercent":10,"threadMemoryAllocations":"","threadDump":[]}
2021-03-24 08:13:03,253 WARN [alert-dispatch:thread-1] [atlassian-monitor] log 2021-03-24T08:13:03.251Z Component 'Java' alerted 'Garbage collection exceeded time limit' (details: {"durationInMillis":3798,"windowInMillis":20000,"limitPercent":10,"threadMemoryAllocations":"","threadDump":[]}, trigger: {"pluginKey": "not-detected"})
2021-03-24 08:13:31,834 WARN [Caesium-1-2] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is turned off']
2021-03-24 08:14:53,275 INFO [Caesium-1-1] [service.stepexecutor.space.SpaceImportExecutor] info Initiate confluence space import with stepId: f9e27202-dd91-4689-acfc-38df3481f6dc
-- stepConfig: fcd9cf34-c0b8-47b1-9c9a-9fd5567b015e | cloudId: 07e7abbd-7f2f-4b24-9e8d-1e34b32ec6d4 | planName: Migration011 | stepType: CONFLUENCE_IMPORT | stepId: f9e27202-dd91-4689-acfc-38df3481f6dc | planId: e11a4fb1-09d1-4924-88c4-d2de74f2f22f | cloudUrl: https://nexor.atlassian.net | taskName: Migrate space DI | taskId: 9e02debc-cb9c-49cc-bb53-a2f2fff7411e
2021-03-24 08:14:55,564 INFO [Caesium-1-1] [service.stepexecutor.space.SpaceImportExecutor] info Initiated import task. Response: ConfluenceImportExportTaskStatus{id='v2-spi-d74b04eb-3005-4f17-9b0b-b46835fd852a', elapsedTime=0s, percentageComplete=0, successful=false, complete=false, message='null', result='null'}
-- stepConfig: fcd9cf34-c0b8-47b1-9c9a-9fd5567b015e | cloudId: 07e7abbd-7f2f-4b24-9e8d-1e34b32ec6d4 | planName: Migration011 | stepType: CONFLUENCE_IMPORT | stepId: f9e27202-dd91-4689-acfc-38df3481f6dc | planId: e11a4fb1-09d1-4924-88c4-d2de74f2f22f | cloudUrl: https://nexor.atlassian.net | taskName: Migrate space DI | taskId: 9e02debc-cb9c-49cc-bb53-a2f2fff7411e
2021-03-24 08:16:56,470 ERROR [Caesium-1-1] [agent.service.stepexecutor.ProgressTracker] error Step failed, message: Import to cloud failed. Message: com.atlassian.confluence.importexport.v2.ImportExportException: entities.xml not found
-- stepConfig: fcd9cf34-c0b8-47b1-9c9a-9fd5567b015e | cloudId: 07e7abbd-7f2f-4b24-9e8d-1e34b32ec6d4 | planName: Migration011 | stepType: CONFLUENCE_IMPORT | stepId: f9e27202-dd91-4689-acfc-38df3481f6dc | planId: e11a4fb1-09d1-4924-88c4-d2de74f2f22f | cloudUrl: https://nexor.atlassian.net | taskName: Migrate space DI | taskId: 9e02debc-cb9c-49cc-bb53-a2f2fff7411e

Like # people like this
2 votes
Joe George March 23, 2021

I'm also seeing this error when trying to migrate. I'm on 7.2.0.

0 votes
Bruce Yen March 23, 2021

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events