Project Failed to Export in ALM?
Question ID: 109186

We have the the following issue during an upgrade and migration of our projects,. We received the following message:

Failed to export project;
Project export failed. The exported project size exceeded 2048 megabytes.;

What should we do koto resolve this issue and get the project migrated since the scp creation is failing?


Marked as spam
Posted by (Questions: 379, Answers: 35)
Asked on October 11, 2019 4:29 pm
Answers (1)
Private answer

Hi HomerJ,

Unfortunately the size constraints are limiting the ability to create a qcp and export. You will have to create a back up of the project schema from the DB and a back up of the project repository and then migrate those to the new server. Restore the back up to the DB instance for the new server, run the sql commands within the installation/ upgrade guide on the restored project schema to align the td user for the new system, and then restore the repository to the new path location for the project repository, edit the dbid.xml file to reflect the new server and DB information to include passwords, path, etc, and then restore the project to the new server using the edited dbid.xml file. All of the steps and directions are detailed in the installation and migration guide for the new version. There is no way to use the qcp with such a large sized file (and this is only something newly available as in the past qcp files were only able to move projects between the same version so 11.52 to 11.53 and were mainly used for archival and creation of test environments solely due to the limitations of their adaptability).

I hope this helps clarify things,

Marked as spam
Posted by (Questions: 0, Answers: 770)
Answered on October 11, 2019 4:31 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top