Issue with schema publishing after installing Universal Records Management

Question

Installing URM over Content Server has been by far the most random experience I've had so far with any technology... Out of 6 installation attemts of URM, only 1 has been entirely successful.... with no errors.... the rest have errors that makes it impossible to work with the product... The funny thing is that the installation is nothing more than the installation of two components via Component Manager, with a few non-important options in the middle that have always been set to the same value...
First of all, in the installation guide of URM there are no mentions of required avaliable space in the Database Tablespace (idc_system) and in about half of our attempts (yes the other half didn't generate issues with this...) the 300Mb Tablespace filled up and caused the installation to pause until I added another datafile to that tablespace.
Secondly, the error that is a constant present in all failed installations is this one:
Unable to publish the schema. Unable to publish the view 'MediaTypes_View' with relationship 'ObjectTypes_MediaTypes'. Failed to append row. Mismatched number of columns in data result set [ Details ]
An error has occurred. The stack trace below shows more information.
!csSchemaUnableToPublish!csSchemaUnableToPublishView2,MediaTypes_View,ObjectTypes_MediaTypes!syFailedAppendRow
intradoc.common.ServiceException: ! csSchemaUnableToPublishView2,MediaTypes_View,ObjectTypes_MediaTypes
     at intradoc.server.schema.StandardSchemaPublisher.publishViewRelationshipFragments(Unknown Source)
     at intradoc.server.schema.StandardSchemaPublisher.publishViewValues(Unknown Source)
     at intradoc.server.schema.StandardSchemaPublisher.doPublishing(Unknown Source)
     at intradoc.server.schema.StandardSchemaPublisherThread.run(Unknown Source)
Caused by: java.lang.Error: !syFailedAppendRow
     at intradoc.data.DataResultSet.addRow(Unknown Source)
     at physicalcontentmanager.PhysicalContentManagerFilters.customizeMediaTypeSchema(PhysicalContentManagerFilters.java:688)
     at physicalcontentmanager.PhysicalContentManagerFilters.doFilter(PhysicalContentManagerFilters.java:114)
     at intradoc.shared.PluginFilters.filter(Unknown Source)
     at intradoc.server.schema.StandardSchemaPublisher.publishViewRelationshipFragment(Unknown Source)
     at intradoc.server.schema.StandardSchemaPublisher.processViewRelationshipPath(Unknown Source)
     at intradoc.server.schema.StandardSchemaPublisher.publishViewRelationshipFragmentsForView(Unknown Source)
     ... 4 more
This error appears immediatly at the end of the server's first startup, just after all database changes are done upon installing URM. This last attempt I actually went to check the Content Server logs before I tried to login to the instance just to be sure that I wasn't responsible in any way for creating this error, and as I expected it was already there, since this relation is created by one of the Records components.... This error is a product of the URM installation itself and makes it impossible to run any Check-Ins or searches, due to the non-working relation causing Javascript errors which don't allow the forms to load values into any drop-down lists...
We also register every "move" we make during installations, and as we reviewed what we did we feel we did exactly the same steps (it's not that hard in a one-click installation process...), why only ONE of the installations went okay we're entirely clueless about.... What we do know is that we seriously need this issue fixed, not only is it costing us a ridiculous ammount of time in "attempts" but come on.. this issue shouldn't really exist in a public release... unless we're the only ones being affected by it?
On a side note, the URM installation was done over a "fresh" component-clean installation of Content Server, so there was nothing of our own custom components that could interact incorrectly with a component of the URM installation.
If anyone has seen this issue before, please write something here. Thanks in advance,
- Tiago Dias
Message was edited by:
user602700
Message was edited by:
user602700

Answer 1

you should issue a support ticket yourself and get a SR number... that's probably faster than going through the sales guy.
I'd suggest turning on the "schema" trace section, make it verbose, and restart. You may need to disable all component (including URM) before doing this.
Something is wrong with the "MediaTypes_View" definition file, which is here somewhere:
contentserver/data/schema/views/
just not sure what...