We have observed that this issues occurred only on instances upgraded to 9.3.0 using dev upgrade packages.
If we use 9.3.0 version instance downloaded from Sugar cloud then the upgrade is successful using 10.0.0 dev upgrade package.
Thanks & Regards,
Thanks for the updates, i think the issue is in 9.3.0 upgrade package because if we use 9.3.0-dev upgrade package to upgrade till 9.3.0 then only upgrade to version 10.0.0 fails in Post upgrade stage.
This issue not occurring on 9.3.0 instances downloaded from cloud backup.
I hope this information is useful to check the issues in previous upgrade packages, all log files are uploaded in initial post.
In the upgrade package you find a modules/Reports/SeedReports.php which is executed in POST installation step 4.
Here the stock reports are listed with unique GUIDs (at the end of the line) which MUST NO be present in the system when the upgrade is executed. You could remove them permanently from the database before installation or you could comment the line in SeedReports.php.
Principal Solution Architect – Professional Services, EMEA
SugarCRM Deutschland GmbH
Thanks for the updates, we have got 142 reports IDs and from the file modules/Reports/SeedReports.php from that we found 29 ID's already in database, we have deleted all 29 reports matching with IDs existing in upgrade package and upgraded instance to version 10.0.0 successfully.
post upgrade we have checked database and only 14 Reports found from 142 IDs.
Is it possible to provide updated upgrade packages to avoid such issues.