Documentum 7.2 Content Server Configuration| Database Scripts

edited October 23, 2017 in Documentum #1

During Documentum 7.2 Content Server Configuration; get to a point "Select Database Home Directory".

I am not sure what is really required here; installing on Windows 2012 R2, Sql Server 2106 with Basic set up option (all services on same box).

Please advice.



  • DCTM_Guru
    edited October 16, 2017 #2

    I think its looking for your SQL Server root directory so that it can locate the appropriate libraries for that rdbms.

  • RajeevNarang
    edited October 16, 2017 #3

    I was trying to install it on Sql Server 2016 which is not supported with 7.2 version. I didn't face the same issue when I tried on another server with Sql Server 2014.

    C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER

    Lesson learned: Review the system requirements closely

    Even after I got fixed and changed the server collation; repo install got these errors.

    18:36:25,360 ERROR [Thread-186] com.documentum.install.server.installanywhere.actions.DiWAServerTestDatabaseVersion - The installer failed to verify SQL server pack: Failed to execute command: C:\PROGRA~1\MICROS~1\CLIENT~1\ODBC\110\Tools\Binn\..\Binn\sqlcmd.exe -w 800 /U sa /P "***" /S "WIN-XYZ" /i "C:\Users\username\AppData\Local\Temp\285862.tmp\testDatabaseVersionInput550722993517889563.tmp"  /o "C:\Users\username\AppData\Local\Temp\285862.tmp\testDatabaseVersionOutput6579814869073329465.tmp"

    com.documentum.install.shared.common.error.DiException: Failed to execute command: C:\PROGRA~1\MICROS~1\CLIENT~1\ODBC\110\Tools\Binn\..\Binn\sqlcmd.exe -w 800 /U sa /P "***" /S "WIN-XYZ" /i "C:\Users\username\AppData\Local\Temp\285862.tmp\testDatabaseVersionInput550722993517889563.tmp"  /o "C:\Users\username\AppData\Local\Temp\285862.tmp\testDatabaseVersionOutput6579814869073329465.tmp"




    at com.documentum.install.server.installanywhere.actions.DiWAServerTestDatabaseVersion.setup(

    at com.documentum.install.shared.installanywhere.actions.InstallWizardAction.install(

    at com.zerog.ia.installer.actions.CustomAction.installSelf(Unknown Source)

    at com.zerog.ia.installer.util.GenericInstallPanel$ Source)

    18:36:25,360  INFO [Thread-186]  - The INSTALLER_UI value is SWING

    18:36:25,360  INFO [Thread-186]  - The common.installOwner.password value is ******

    18:36:25,360  INFO [Thread-186]  - The SERVER.SECURE.ROOT_PASSWORD value is ******

  • DCTM_Guru
    edited October 17, 2017 #4

    What did you do to fix the issues?  Maybe you are still referencing 2016 SQL client.

  • Alvaro_de_Andres
    edited October 23, 2017 #5

    something went wrong while testing the database, you can see in the log where the output of the test was stored:


  • Enter: C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools
    Or where ever your SQL client tools installed.

  • Rasheed Mahmoud
    Rasheed Mahmoud Applications Support Manager

    I am facing the same issue please share the solution if possible
    OS : windows server 2016 OS
    SQL 2016 sp2 DB in a separate host
    Content Server 16.4

  • bacham
    bacham Junior Member

    If I remember correctly it is expecting the location of the sqlcmd.exe utility. The installer is not using the ODBC Data Source which the Content Server uses.

  • Hello experts,

    We are trying to configure Documentum services with below versions and other server configs.
    However, the installation is getting stuck at BPM process with the below mentioned error message.

    Documentum Version : 16.4
    OS : Windows 2016
    Database : Azure database with compatibility level set to SQL 2016 version
    Error message : The installer failed to execute BPM queue management support. Below is the screenshot.

    Could you please suggest what could be the issue here?? database compatibility or any other area??

  • What does that have to do with this thread? Open a new thread.

  • Hi Veeranjaneyulu,
    is it resolved? I am also facing similar issue.

  • Hi Veeranjaneyulu,
    is it resolved? I am also facing similar issue.

  • Download relevant sqlcmd and place it in the SQL Tools directory. DCTM will look for this file

Sign In or Register to comment.