Developer Edition 6.5 SP2 Windows SQL Installation Fails

I am trying to install the Developer Edition on a new server. I am sure at this point that I have fulfilled all the prerequisites, yet the install is failing during the "Configuring Content Server" stage.

The error indicates that a bat file "\dev_edition_6.5_sp2_windows_sql\temp\launchServerConfigurationProgram.bat" is failing. I see that this file is created in the temp folder, and may actually have been executed as I see the Documentum folders have been added to the class path. As soon as I acknowledge the pop-up error, the files in this temp folder are deleted.

I am an administrator on the server (a VMWare guest) Windows 2003 SP2. .Net and Java JRE is up to date. No Documentum software or SQL servers are installed. I am running the install through a Windows Remote Desktop client.

Windows Server 2003 SP2

Intel Xeon 1.6 GHz

4 GB RAM (PAE)

>60 GB free disk space

Java Version 1.6.0_16

.NET Framework 3.5 SP1

Installation logs are attached.

Message was edited by: jlecko

screenshot.bmp

install.log

setupError.log

Find more posts tagged with

Comments

s_ravi

I am facing the same problem but with different error. I have attached the setupError.log. I had installed Content Server 6.5 prior to this developer edition installation. As I found Content Server 6.5 installation way too complex, I had uninstalled.

Now My Installation of Developer Edition fails with error :

(Dec 16, 2009 5:49:46 PM), Setup.product.install, java.lang.NullPointerException, err, An exception occured in: DiWAOemInitialize, beanID: oemInitialize - DiWAOemInitialize failed!; For more detailed information, see the error log: C:\Applimation\Partners\EMC\Documentum\6_5SP2\dev_edition_6.5_sp2_windows_sql\setupError.log

(Dec 16, 2009 5:49:46 PM), Setup.product.install, java.lang.NullPointerException, err, java.lang.NullPointerException

at com.documentum.install.oem.common.services.DiOemEnvironmentVerifier.checkForTooManyDocbrokers(DiOemEnvironmentVerifier.java:39)

at com.documentum.install.oem.common.services.DiOemEnvironmentVerifier.checkValidOemEnvironment(DiOemEnvironmentVerifier.java:25)

at com.documentum.install.oem.common.beans.wizard.action.DiWAOemInitialize.inferUpdate(DiWAOemInitialize.java:105)

at com.documentum.install.oem.common.beans.wizard.action.DiWAOemInitialize.execute(DiWAOemInitialize.java:54)

at com.installshield.wizard.StandardWizardListener.execute(Unknown Source)

at com.installshield.wizard.StandardWizardListener.currentBeanChanged(Unknown Source)

at com.installshield.wizard.Wizard$RunThread.run(Unknown Source)

Any ideas ? And is there anyway we can manually cleanup the installation of documentum any install ?

-Ravi.

minnal

I had the same issue. Since i don't have any documentum uninstaller on the system this is what i did and it removed the problem. It is a manual process and takes LOT of your time and patience.

Step 1:

Cleanup all the folder maually by deleting. Folders like c:\documentum, c: program files\documentum etc

Search the whole system for 'documentum' and delete everything.

Step 2:

delete all the registry entries

go to Start->run->regedt and regedt32

Search for documentum in all forlders and delete everything with documentum on it. This is the one takes up LOT of your time.

Restart the machine and try to install the documentum developer edition again. Good Luck!