DAR Error When Creating Repository on Documentum 6.6 Windows 2008

When creating a new repository on Documentum 6.6 for Windows 2008 64bit with MSSQL 2008, you will encounter an error indicating that there are 3 DARs that failed to install (actually there are 4 failed but the "preset" is not shown).

This is due to a bug in composer that is fixable by Composer_6.6_CMPSR-3056_Hot_Fix.zip. This patch currently is not for public release and you need to raise a service request to get the file using Powerlink account.

I did try to work without this patch, and the solution is to install the DARs manually using installer from:

appname="c:\documentum\product\6.6\install\composer\ComposerHeadless\darinstaller.exe"
location="c:\documentum\product\6.6\install\DarsInternal"
dar files="presets, smart container, dmsclient, webtop"

Powerlink Reference

How to install Documentum 6.6 with SQL Server 2008 64bit

I tried installing the shiny new EMC Documentum 6.6 after my suggestion to an EMC forum that we should simplify Documentum installation. Unfortunately, we could wait another release as things didn't go any easier on 6.6, the introduction of support to Windows 2008 64bit made it a lot harder.

For those lost in the dark, here are the exact step-by-step procedure to get it right. Any deviation from this procedure will guarantee a failed installation.

1. Install Windows 2008 64bit
2. Install Windows Service pack 1
3. Install MS SQL Server 2008 64bit mode
3.1 then create a CASE SENSITIVE instance (on the next tab called "Collation" after you are prompted for SQL Agent User)
4. Install MS SQL Server 2008 SP1 64bit, get it from here
5. Install MS SQL 2008 Command Line utilities from here
6. Create an ODBC entry but do not use the ODBC from Control Panel. Run the program from "C:\Windows\SysWOW64\odbcad32.exe"
7. Install Documentum 6.6 (as you normally would)
8. Create a new Repository

I got the procedures from EMC Community thanks to Laurence Hart for his "Pie on Content Management" and Powerlink

Documentum 6 Doesn't Run Properly After Changing the IP or Hostname

If you're on a DHCP and the IP did changed, or for some reason you tried to mess up with the hostname and changed it to something else, you wont be able to use your docbase anymore. The bad thing is, you won't see any error while loading, in fact the docbase will startup normally.

The solution was posted on Powerlink, the versions affected are Documentum 6 and Documentum 6.5, you need to download a patch on the name "pkiD6ChangeId.bat".

[DM_SESSION_E_CLIENT_AUTHENTICATION_FAILURE]error: "Could not authenticate the client installation for reason: Client hostname in authentication string doesn't match value in registry"