Upgrade from Elements 10 to 12 - Organiser Not Working

Question

I have upgraded a fairly large catalog (20,000+ photos) from Elements 10 to Elements 12.  The upgrade completes successfully but the catalog will not open in Elements 12.
Either organiser crashess immediately, or if I go into Organiser with a new catalog and then open the upgraded catalog from Manage Catalogs then the thumbnails are loaded and I get a "Please wait while the catalog is loaded..." dialog.  This would be fine if the catalog actually loaded, but many hours later it is still in the same mode with organiser unresponsive.
Using task manager I can see that Elements 12 Organiser (32 bit) is consuming memory but nothing with respect to CPU, Disk or Network.  Checking the logs (the ones I can find) they are not updating during that period leaving me to conclude that Organiser is dead.
The install itself appears OK as I can start a new catalog with problems.  Trying to repair the catalog indicates that the catalog has no errors.
I am running Windows 8 Pro.
Anyone else seeing similar issues / ideas on what I can do to recover the catalog?
Thanks

Answer 1

Ok after much pain, research and frustration I have figured out what the issue was.  There were some some records in my catalog table media_table with a volume_id without a corresponding record in the volume_table table.  I found this by looking at forums for common issues with previous catalogs.  Correcting the volume_id record in media_table solved the issues.
If your elements organiser is crashing its worth checking if you have a similar situation although will require some technical knowledge.  I would recommend that you ALWAYS backup your catalog before doing any corrections in the database in case you corrupt everything and only proceed if you are comfortable with what you are doing and the risks involved:
Download sqlite and ensure sqlite3.exe is in the same directory as your catalog file
Backup your catalog.pse12db file
From the command prompt cd into the directory where your catalog is located and run sqlite3.exe catalog.pse12db
select distinct(volume_id) from media_table where volume_id not in (select distinct(id) from volume_table);
If point 4 returns nothing your issue is different.  .quit will close the database connection.
If point 4 does return records then you have an issue.  My records should have been linked to a different record in volume_table so I ran an update statement to manually correct the volume_id in media_table.
I went back to my pse 10 backup catalog to see if this issue was caused during the conversion and it was not, the same problem existing in the old catalog.  How this occured I do not know but there must have been a bug introduced in pse12 as pse10 had the same issue and did not crash!
Hope this helps anyone else who is struggling with pse12 crashing!