TRUSTEE validating table not found

I am trying to do the schema extention to deploy contract management template.

I have downloaded Schema Extensions. which has Solutions2.xml file.

When I try to Generate the Object Model it give following error and doesn't generate the .dat file

Jan 22 12:54:15.809: ERROR [CreateDat] (MetaData Table) EXT::TRUSTEE validating table not found when adding (MetaData) EXT::AUTHOR to (Document) APP::ITDOCUMENT

Anyone know what this error means???

Any help would be greatly appreciated.

Find more posts tagged with

Comments

dbguy

The XML is wrong. Search for the definition of AUTHOR and fix it to point to namespace BASE, name DIT_TRUSTEE.

Piyush

Thank you very much for the quick reply. I got that going. Now When I am trying to migrate from to this new object model my migrate log throws following error

java.io.StreamCorruptedException: invalid stream header

Here is the stack trace. It also give a worning of "Bad Password". Which password its talking about.

please help

Here is the snapshot of log file generated my migrate tool.

Mon Jan 22 17:24:08.019: INFO [main] CmsInvokerMain: Validating Installation
Mon Jan 22 17:24:08.034: INFO [main] File 'lib/security/local_policy.jar:4368:1605592442' matches
Mon Jan 22 17:24:08.034: INFO [main] File 'lib/security/US_export_policy.jar:4355:3938255137' matches
Mon Jan 22 17:24:08.034: INFO [main] Installation Validation passed
Mon Jan 22 17:24:08.050: INFO [main] *****************************************************************************
Mon Jan 22 17:24:08.050: INFO [main] * Please be sure that no one else is using the database being migrated AND *
Mon Jan 22 17:24:08.050: INFO [main] * that you have a backup of the database!!! *
Mon Jan 22 17:24:08.050: INFO [main] * *
Mon Jan 22 17:24:08.050: INFO [main] * This program can make large and irreversible changes in the database *
Mon Jan 22 17:24:08.050: INFO [main] * that it is applied to! *
Mon Jan 22 17:24:08.050: INFO [main] *****************************************************************************
Mon Jan 22 17:24:08.050: INFO [main] Executing Library Migrate...
Mon Jan 22 17:24:08.050: INFO [main] ResourceHandler: Resource found in relative local filesys: file:/C:/worksitemp4/mpserver/config/objectmodels/worksitemp40.dat
Mon Jan 22 17:24:08.050: INFO [main] ResourceHandler: Resource found in relative local filesys: file:/C:/worksitemp4/mpserver/config/objectmodels/ToolkitOM.dat
Mon Jan 22 17:24:08.081: INFO [main] ResourceHandler: Resource found in relative local filesys: file:/C:/worksitemp4/mpserver/config/objectmodels/worksitemp40.dat
Mon Jan 22 17:24:08.081: INFO [main] ResourceHandler: Resource found in relative local filesys: file:/C:/worksitemp4/mpserver/config/objectmodels/ToolkitOM.dat
Mon Jan 22 17:24:08.237: INFO [HeapSpaceMonitor] HeapSpaceThread: total=2m used=2m free=593k
Mon Jan 22 17:24:08.347: INFO [main] Initializing Database Manager...
Mon Jan 22 17:24:08.347: INFO [main] Initializing Connection Pool Manager...
Mon Jan 22 17:24:08.347: INFO [main] EnterpriseConfig.addCluster( worksitempd )
Mon Jan 22 17:24:08.363: INFO [main] ClusterConfig.setModified( false ) for cluster worksitempd
Mon Jan 22 17:24:08.409: INFO [main] PmClient: findServiceOnServer: cluster=172.20.16.41
Mon Jan 22 17:24:08.425: INFO [main] PmClient.initialize(): pm port is 1118
Mon Jan 22 17:24:08.535: INFO [main] PmClient.initialize(): PmServer object is com.imanage.cms.fc.pm.PmServer_Stub[RemoteStub [ref: [endpoint:[001fntwedlab01:1115](remote),objID:[704baa:1104bf7f2c4:-8000, 1]]]]
Mon Jan 22 17:24:08.535: INFO [main] PmClientPool: pm server on server hostname=172.20.16.41 ipaddress=172.20.16.41 is available
Mon Jan 22 17:24:09.035: WARN [main] ClusterConfig: Bad Password
java.io.StreamCorruptedException: invalid stream header
at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
at java.io.ObjectInputStream.(Unknown Source)
at com.imanage.cms.fc.config.ClusterConfig.getClusterConfigFromEncryptedByteArray(ClusterConfig.java:268)
at com.imanage.cms.fc.pm.PmClient.loadConfiguration(PmClient.java:351)
at com.imanage.cms.fc.config.EnterpriseConfig.loadClusterConfig(EnterpriseConfig.java:784)
at com.imanage.cms.fc.config.EnterpriseConfig.addCluster(EnterpriseConfig.java:91)
at com.imanage.cms.fc.config.ClusterConfig.getLocalClusterConfig(ClusterConfig.java:87)
at com.imanage.cms.t1.librarymigrate.ImLibraryMigrateMain.run(ImLibraryMigrateMain.java:143)
at com.imanage.cms.t1.librarymigrate.ImLibraryMigrateMain.main(ImLibraryMigrateMain.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.imanage.cms.fc.main.CmsInvokerMain.executeMainMethod(CmsInvokerMain.java:103)
at com.imanage.cms.fc.main.CmsInvokerMain.execute(CmsInvokerMain.java:43)
at com.imanage.cms.fc.main.CmsInvokerMain.main(CmsInvokerMain.java:27)
Mon Jan 22 17:24:09.035: WARN [main] warn: exception=java.lang.IllegalArgumentException: Bad Password
at com.imanage.cms.fc.config.ClusterConfig.getClusterConfigFromEncryptedByteArray(ClusterConfig.java:275)
at com.imanage.cms.fc.pm.PmClient.loadConfiguration(PmClient.java:351)
at com.imanage.cms.fc.config.EnterpriseConfig.loadClusterConfig(EnterpriseConfig.java:784)
at com.imanage.cms.fc.config.EnterpriseConfig.addCluster(EnterpriseConfig.java:91)
at com.imanage.cms.fc.config.ClusterConfig.getLocalClusterConfig(ClusterConfig.java:87)
at com.imanage.cms.t1.librarymigrate.ImLibraryMigrateMain.run(ImLibraryMigrateMain.java:143)
at com.imanage.cms.t1.librarymigrate.ImLibraryMigrateMain.main(ImLibraryMigrateMain.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.imanage.cms.fc.main.CmsInvokerMain.executeMainMethod(CmsInvokerMain.java:103)
at com.imanage.cms.fc.main.CmsInvokerMain.execute(CmsInvokerMain.java:43)
at com.imanage.cms.fc.main.CmsInvokerMain.main(CmsInvokerMain.java:27)

Mon Jan 22 17:24:09.035: ERROR [main] LibrarayMigrate ended with error(s)...
Mon Jan 22 17:24:09.035: ERROR [main] error: exception=java.lang.NullPointerException
at com.imanage.cms.t1.librarymigrate.ImLibraryMigrateMain.run(ImLibraryMigrateMain.java:145)
at com.imanage.cms.t1.librarymigrate.ImLibraryMigrateMain.main(ImLibraryMigrateMain.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.imanage.cms.fc.main.CmsInvokerMain.executeMainMethod(CmsInvokerMain.java:103)
at com.imanage.cms.fc.main.CmsInvokerMain.execute(CmsInvokerMain.java:43)
at com.imanage.cms.fc.main.CmsInvokerMain.main(CmsInvokerMain.java:27)

dbguy

The real problem is here:

Mon Jan 22 17:24:08.535: INFO [main] PmClientPool: pm server on server hostname=172.20.16.41 ipaddress=172.20.16.41 is available
Mon Jan 22 17:24:09.035: WARN [main] ClusterConfig: Bad Password

There is a Library Migrater bug that it does not work correctly if there is a cluster password. The workaround is to reset the password, do the migration, and then set it back.

william_ha

I was planning to extend the database table and column after I did it once. However, the second attempt was not successful. Bad password is not the problem here I guess 'cause it is not in the error log. This is what I get from the log:

Tue Feb 06 11:03:22.395: INFO [main] Initializing Migrater...
Tue Feb 06 11:03:22.395: INFO [main] Migrating...
Tue Feb 06 11:03:22.395: INFO [main] Reading dictionary files...
Tue Feb 06 11:03:22.692: INFO [main] Read dictionary file /C:/app/local/mpserver/config/objectmodels/worksitemp40.dat
Tue Feb 06 11:03:22.880: INFO [main] Read dictionary file /C:/app/local/mpserver/config/objectmodels/CMS.dat
Tue Feb 06 11:03:22.880: INFO [main] Confirming database and -from dictionary match
Tue Feb 06 11:03:22.974: ERROR [main] -from Dictionary and database don't seem to match

May I know what is the problem?

dbguy

In the second time, the "from" file is the "to" file from the first time. I mean, first time you went from worksitemp40.dat to something.dat. The second time, you have to go from somtehing.dat to CMS.dat.

william_ha

1. I thought it is possible to delete the field/table by reOpen the something.xml to replace and deploy the something.dat to the SQL server. Is there any way to delete/edit an existing field/table once it is deployed?

2. Or I assume developer normally just leave the field and unregister the extended properties they don't need from the web configuration page?

3. The issue with creating somethingNEW.dat from something.dat is we cannot edit/delete a field or table from the existing database table. Every new thing has to be built on top of the existing *.dat/database. Is that correct?

Thanks dbguy, for the advice and reminder

dbguy

At this time there is no way of deleting or modifying an added field; all changes are additions to an existing model. To answer your questions:

1. No.

2. Yes.

3. Yes.