Missing content after upgrade from 3.4.c->4.0.e->4.2.c

[swhitman]

After upgrading, a user noticed that some of the spaces in Alfresco Explorer were empty. Not even the admin user can see the content. It is there because if the user tries to recreate the file he gets the error message: Duplicate child name not allowed: …

I have not yet been able to find a definitive pattern between the files that are visible and those that are not.

The upgrade was done on a virtual test server before doing it in the production server, but the problem was not noticed.

The only un-ordinary thing done during the upgrade process was the recommendation in this post: https://issues.alfresco.com/jira/browse/ALF-17483 to execute the update query on the alf_node_properties table. We followed the instructions from this post because we were getting the referenced error message.

Any ideas on how to diagnose this.

[swhitman]

A little bit more information. We get these messages in the log file:
alfresco.log.2013-05-06:17:58:30,727 WARN  [org.alfresco.repo.module.ModuleServiceImpl] A previously-installed module 'org_alfresco_module_wcmquickstart' (version 1.0) is not present in your distribution.
alfresco.log.2013-05-06:17:58:30,743 WARN  [org.alfresco.repo.module.ModuleServiceImpl] A previously-installed module 'org.alfresco.module.quickr' (version 1.0) is not present in your distribution.

[swhitman]

We started over from our original 3.4.c backup and installed 4.0.e (without doing anything out of the ordinary). We have the problem in that version as well.

I found the name of a missing file in two tables, alf_child_assoc and alf_node_properties. Can anyone point me to a description of these tables?

[swhitman]

We installed 3.4.c x64 from a backup of our x86 3.4.c server to see if it was a 32 vs. 64 bit problem. It was not, the missing content was no longer missing. We did notice that for 3.4.c the Web Quick Start was set to install by default. For 4.0.e, the default was *not* to install Web Quick Start. When 4.0.e was installed with Web Quick Start our problem was resolved. Not wanting to have to start the production upgrade over from our 3.4.c data, we tried installing the Web Quick Start as a module on a 4.2.c server we used for testing. Once the module was installed our missing content came back!

I can fairly confidently say that we have not intentionally used Web Quick Start. Why some of our content depended on this module and other content did not will remain a mystery unless someone on this forum takes enough interest to post the answer.