Upgrade process from 6.0.12 EE SP2 to 6.1 GA1 fails even with a clean databaseuuuu

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 6.0.12 EE, 6.1.0 CE GA1
• Fix Version/s: --Sprint 11/12, 6.2.0 CE M2
• Component/s: Upgrades
• Labels:
  • 6.0.12.EE-SP2
  • 6.1GA1
  • Upgrade
  • community-verifier
• Environment: MySQL 5 and Tomcat 7 environnement
• Similar Issues: Show 4 results ; ;

  LPS-35280	Upgrade Process 6.0 EE SP2 (6.0.12) to 6.1 EE GA2 (6.1.20) fails during Verify Document Library Process.
  LPS-24339	Upgrade Process 6.0 EE SP2 to 6.1 RC doesn't work
  LPS-35034	Upgrade from 6.0.12 to 6.1.x using PostgreSQL fails if staging is activated
  LPS-25970	Upgrade to 6.1 throes FileExtensionException in v6_1_0.UpgradeImageGallery (Upgrading from 6.0.12 to 6.1.10)

When upgrading from 6.0.12 EE SP2 to 6.1 GA1 I have lots of Duplicates (even with a clean database) and then a error in the DL Upgrade Process (i am attaching the log error). The simplest process I tried was:

• Start 6.0.12-EE-SP2 with a clean database
• Check licence agreement and security question
• Shut down 6.0
• Start 6.1 GA1 pointing to this database
• Get the errors I attached

PD:I have been able a few days ago to upgrade from 6.0.12 EE SP2 to 6.1.RC, and then to 6.1 RC following the helpfull instructions I found here.
1- < a href="http://portal.gnenc.org/web/20725/blog/-/blogs/upgrade-liferay-6-0-6-to-liferay-6-1-rc1?_33_redirect=http%3A%2F%2Fportal.gnenc.org%2Fweb%2F20725%2Fblog%3Fp_p_id%3D33%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_count%3D1"> Link 1 </a>
2- <a href= "http://portal.gnenc.org/web/20725/blog/-/blogs/upgrade-from-liferay-6-1-rc1-to-ga1?_33_redirect=http%3A%2F%2Fportal.gnenc.org%2Fweb%2F20725%2Fblog%3Fp_p_id%3D33%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_count%3D1"> Link 2 </a>

[Drew Blessing]

Hi Jordi,

Thank you for your report.

This issue is a duplicate of LPS-18422 and will be closed. Please follow the mentioned issue for updates. Thanks!

[Michael Saechang]

Closing ticket as per Drew's comment. Thank you for verifying.