Below is an excerpt of the error message seen in the docapp installer log.
ERROR: Installation cannot proceed.
DfException@1d0:: THREAD: main; MSG: [DM_API_E_NOTYPE]error: "Type name 'dm_application' is not a valid type."; ERRORCODE: 100; NEXT: null
ERROR: Installation cannot proceed.
DfException@1d0:: THREAD: main; MSG: [DM_API_E_NOTYPE]error: "Type name 'dm_application' is not a valid type."; ERRORCODE: 100; NEXT: null at com/documentum/fc/server/session/DfiSessionDMCL.dmAPIGet (DfiSessionDMCL.java) at com/documentum/fc/client/DfSession.apiGet (DfSession.java) at com/documentum/fc/client/DfPIntObjectL. (DfPIntObjectL.java) at com/documentum/fc/client/DfObjectCache.createPIntObject (DfObjectCache.java) at com/documentum/fc/client/DfObjectCache.newObject (DfObjectCache.java) at com/documentum/fc/client/DfSession.newObject (DfSession.java) at com/documentum/ApplicationManager/DfApplication.newApplication (DfApplication.java) at com/documentum/ApplicationInstall/DfAppInstallerUtilities.createLivePackage (DfAppInstallerUtilities.java) at com/documentum/ApplicationInstall/DfAppInstaller.createEnvironment (DfAppInstaller.java) at com/documentum/ApplicationInstall/DfAppInstaller.startInstall (DfAppInstaller.java)
ABORT TRANSACTION
RESOLUTION:
This error occurs because the dm_application object type is not installed in the Documentum environment. This means the 'headstart.ebs' script failed or was not executed.
Check the following path on the Content Server:
\documentum\dba\config\
Search for the 'headstart.out' file.
Open the file, look for creation of dm_application type.
If the 'headstart.out' file is not listed, this means the script wasn't executed.
Run the 'headstart.ebs' script. Follow the instructions as listed in the Content Server documentation for executing a script.
Once this is executed. The dm_application type, will be created.
Re-run the docapp installer, the docapp installation will now succeed.
No comments:
Post a Comment