Issue with documentum installation? cannot set document type

Well the topic names covers it all..

Basically this is my third installation of documentum, but I'll admit I'm no guru (i cover dfs/dfc usually) so if this question is silly, I ask for some forgiveness

This being said, I installed documentum 6.7 64bit version on a windows 2008 enterprise 64bit machine with sql server 2008 enterprise 64bit..

All was well..

I loaded into the application server da and webtop.. apparently all is well, BUT!

see screen1.jpg..

If i try to create a document, I get an empty/greyed selection for the type of the new document! If by pure chance I want to try anyway without a set type, it warns me that the type cannot be null...

I cannot really point the source for an abnormality of this size!

Especially because if I circumvent the whole process using instead import, as seen in screen2.jpg I STILL cannot set a type,but i can move forward since it auto-recognize the formats, and then if i check the properties of the imported file after the whole thing, the file has a proper dm_document type...

Any advice?

I really can't pinpoint the possible source of the issue...

Thanks in advance,

Vitonofrio del Rosso

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

witchedwiz

indeed, although it hurts my pride a little to mark the question as answered when I'm not really sure what made this work out properly..

Oh well, after this project I'll take some time to try and fiddle with the settings of a new clean installation..

All comments

witchedwiz

still no luck.. uninstalled the whole thing, reinstalled and no luck..

what really bother me is that apparently there's no error of sorts..

the only "strange" thing that is notified near the end of the installation is:

and it ain't even marked as an error.. As a matter of fact checking the serverconfiguration log the only reference I get is

"Installing bundled DARs.

Finished installing bundled DARs."

If I check the install.log i get this near the end

"2010500 [Runnable bean context: Di WA Server Obtain Sql Sybase Data File Directory (ObtainSQLDatafileDirectory)] WARN com.documentum.install.server.common.services.db.DiServerDbSvrSqlServer - Invalid directory path, C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA, found

3974906 [Thread-1] WARN com.documentum.install.dacfg.common.services.dar.DiDarUtil - Could not find C:\Documentum\product\6.7\install\darsAdditional.xml. Will use empty actions list.

3974922 [Thread-1] WARN com.documentum.install.dacfg.common.services.dar.DiDarUtil - Could not find C:\Documentum\product\6.7\install\darsAdditional.xml. Will use empty actions list.

3974984 [Runnable bean context: Di WA Server Processing Add On Dars (processAddOnDars)] WARN com.documentum.install.dacfg.common.services.dar.DiDarUtil - Could not find C:\Documentum\product\6.7\install\darsAdditional.xml. Will use empty actions list."

So this actually starts making sense.. Thinking that maybe some of the bundled DAR messed up during the installation (although I didn't get a single notification in that direction during the whole process), i manually installed the dars in the DARsInternal via dardeployer and it didn't change a thing..

on the top of that there was not a single instance where the deployer gave me any error of sorts after the single dar installation...

I'm quite at loss.. Admittedly it's my first time installing the documentum suite on windows but I didn't have anything remotely similar when I installed the whole thing on a *nix system

BinayGupta

In DA if you go to Administration > Types. Do you see the object types there ?

witchedwiz

yeah that was my first thought..

All the types are correctly listed there, included the classic dm_document, sysobject, etc....

I'm trying to do a full reinstall yet again and check what's missing but I'm quite doubtful it will solve anything..

BinayGupta

Are you sure that its a problem on the content server ? Did you try creating an object using iapi or something else apart from webtop and da?

witchedwiz

admittedly I didn't..

I'll try to do a fast reinstall and try on the fly... I'll give you feedback asap.

witchedwiz

I ran the installer YET again, no change and it.. worked?

I'm quite puzzled as using the express installation it apparently either didn't require or managed to find darsAdditional.xml, as it wasn't listed as a missing file in the log... The nightmare is over and I can go

and finally start doing the actual work.

BinayGupta

mark the question as answered for others to reference.

witchedwiz

indeed, although it hurts my pride a little to mark the question as answered when I'm not really sure what made this work out properly..

Oh well, after this project I'll take some time to try and fiddle with the settings of a new clean installation..

ukamal

Strange this happened to types and not formats...in previous versions i.e. 5.3 SPx, this used to happen to formats when a new installation would not see formats. We reapplied the formats to the dm_document types. We ran the DD publisher job, got rid of all DMCLs and caches, then restarted all related servers. That usually did the trick.

I wonder if the issue was that DD publisher did not run correclty the first time during the installation. I am getting ready to test DCTM 6.6. In case you test this again, let me know as I am curios as well on the findings

witchedwiz

Did some lightning quick re-test yesterday..

Content server 6.7 64bit for windows sql..

apparently I'm able to "avoid" the type issue if i "close" the installation process granted i clear these step

1) CS full installation

2) Server configuration

3) add doc broker

4) run administrative script and install bundled dar

5) after the message "the bundled dar have been installed correctly, hurray!" close the installation process forcibly (click on x icon in the window frame)..

If I went through with the installation the repository would get somehow messed and I could not assign types anymore on document creation/import, on the other hand if I stop the installation process at that point (and that's pretty much the end, after that it simply restart the repository programmatically) the whole thing would go awry..

Tried the whole thing 4 times

1st) clean sweap, install cs, configure server, complete installation.. not working

2nd) delete docbroker, delete repository, reinstall docbroker and repository, halt installation after bundler dar.. working

3rd) clean sweap, install cs, configure server, install docbroker, install repository, halt installation after bundler dar.. working

4th) delete docbroker, delete repository, reinstall docbroker and repository, complete installation.. not working

As is I'll simply halt the installation process@ the step after the bundled dar installation.. seems safe and all is working apparently..

ukamal

Nice! Thanks for the follow up. Will keep that in my books for the future when I am testing