Cannot connect to existing SQL Server instance with EMC Documentum 6.5 SP2 Developer Edition

hi!

i cannot install EMC Documentum 6.5 SP2 Developer Edition, because it cannot establish connection to the existing database. My SQL Server is up, firewall ok, using both TCP/IP and Named Pipes, Server Browser is up. I can connect to it from other machines with SQL Management Studio, but Documentum Installer fails with this message:

* DATABASE_ENVIRONMENT: 'HResult 0x2, Level 16, State 1Named Pipes
Provider: Could not open a connection to SQL Server [2]. Sqlcmd:
Error: Microsoft
SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote
connections..Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.'.

can anyone help me with this?

Find more posts tagged with

Comments

T_Allen

I had the same issue with the 1.5 version of XCP Dev Edition only I also could not get SQL Server Management to connect to DB even though everything is on same machine. First, make sure you have System Data Source created in ODBC admin. Second, in any of the Documentum setup screens, try the IP address for the DocBroker instead of the name (I used 127.0.0.1). You may need to use it for the repository name as well although I did not have to. You may also need to use the SQL Server Instance name instead of the "actual" server name in some cases. I hope this is helpful.

jb33

Thanks for your advice, but unfortunately I can see no steps in the EMC Documentum Installer

wizard, where I could give IP address instead of name..

On the first screen it prompts for two directories,

on the second for Windows passoword,

on the third it asks whether I would like to use existing or preconfigured SQL Server database, and custom port, pw stuff

then a Data Source Name is asked, where I can give the created System DSN name, user + pw.

The DSN is a System DSN, test ok, but EMC Documentum cannot connect: "Login timeout expired"

:-(

T_Allen

Try setting up your DSN with an IP address instead of the server name. And, for your DSN, what protocol did you select for your SQL client connection? If everything is running locally on the same box you should select Named Pipes for the SQL client but TCP/IP should work as well. Is Named Pipes & TCP?IP protocol enabled for the SQL Server? I know it's strange but I would bet that this is a name resolution issue as I just went through this myself. For whatever reason the Documentum install could not resolve the local server name but IP address worked.

jb33

OK,

1, I have set up my DSN with 127.0.0.1\SQLEXPRESS

2, Named Pipes and TCP/IP both enabled, Remote Connect is also enabled

3, Server Browser running

4, connecting is possible from remote MS SQL Management Studio Express client

5, tried with two different ODBC drivers (SQL Server and SQL Native Clent)

you are right that name resolving causes similar problem as if I give a blahblah DSN

for Documentum, the error message is Login timeout.

if I set the DSN protocol to TCP/IP, the error message still says "HResult 0x2, Level 16, State 1Named Pipes Provider, etc.. Login timeout expired"

:-(

T_Allen

What is the OS you're installing on? If Windows Server 2008, (UAC) User Access Control may cause problems as well. You can turn it off or try running the setup.exe as Administrator (right click & run as...). In my situation I got further than you are getting now before I saw the problem. I didn't see it until it was time to configure the repository & DocBroker.

jb33

Hi Allen, I have Windows 7, UAC off.

Sumanth A

Windows 7??????

I do not think it is supported. Please check the Release notes and us ethe supported version of OS.

jb33

To be honest I started all this on XP SP3, but after a failed installation attempt, I am unable to retry as the installer says "DiWAOemInitialize failed! Other Documentum software is already installed.." After uninstalling, etc. the software, the Installer is no more able to run, after deleting the stuff in Program Files\Documentum still say this, so I had to move on to an other machine.. How can one uninstall this program if uninstaller cannot..? I think installation failure is something that uninstaller software should be able to handle.