Tms Installation with error.

[Bar1s]

Hi everyone,

I am trouble with Tms 13.1.2 installation. I am getting this error when ldap server installation part.

Also problem show up Tms Agent and Provisioning part. Any idea ?

[Kjetil Ree]

Do the log files referred to in the error message say anything useful?

Regards,

Kjetil

[Bar1s]

Hello All,

It was clean install Windows 2008 x64.

I have not any antivirus nor any security program. I am local admin user for this server, normally i am a domain user.

I am getting this error messages at OpenDsConfigLog.txt

TMPPATCH: C:\Program Files (x86)\TANDBERG\TMS\provisioning\database-patches\tmp

~1: C:\Program Files (x86)\TANDBERG\TMS\provisioning

A subdirectory or file C:\Program Files (x86)\TANDBERG\TMS\provisioning\database-patches\tmp already exists.

upgrade type:

The service name is invalid.

More help is available by typing NET HELPMSG 2185.

Disable replication

Establishing connections .....

Could not connect to localhost:4444.  Check that the server is running and

that the provided credentials are valid.

Error details:

javax.naming.CommunicationException: localhost:4444 [Root exception is

java.net.ConnectException: Connection refused: connect]

set log rotation policy and restrict access

wait 1

Connect Error

Result Code:  91 (Connect Error)

wait 2

Connect Error

Result Code:  91 (Connect Error)

wait 3

Connect Error

Result Code:  91 (Connect Error)

wait 4

Connect Error

Result Code:  91 (Connect Error)

wait 5

Connect Error

Result Code:  91 (Connect Error)

wait 6

Connect Error

Result Code:  91 (Connect Error)

wait 7

Connect Error

Result Code:  91 (Connect Error)

wait 8

Connect Error

Result Code:  91 (Connect Error)

wait 9

Connect Error

Result Code:  91 (Connect Error)

wait 10

Connect Error

Result Code:  91 (Connect Error)

Unable to start opends, will try again ..

C:\Program Files (x86)\TANDBERG\TMS\Provisioning\OpenDs-2.0\logs\native-windows.out

        1 file(s) copied.

The service name is invalid.

More help is available by typing NET HELPMSG 2185.

And  Opends_version.txt

OpenDS Directory Server 2.0.0

Build ID: 20090630082738Z

Major Version: 2

Minor Version: 0

Point Version: 0

Version Qualifier:

Revision Number: 5492

URL Repository: file:///svn-mirror/branches/b2.0

Fix IDs:

Debug Build: false

Build OS: SunOS 5.10 x86

Build User: builds

Build Java Version: 1.5.0_12

Build Java Vendor: Sun Microsystems Inc.

Build JVM Version: 1.5.0_12-b04

Build JVM Vendor: Sun Microsystems Inc.

Upgrade Event IDs: 1,2,3,4,5,6,7,8,9

--

           Name                 Build number         Revision number

Extension: snmp-mib2605         2.0.0                5492

[Magnus Ohm · Accepted solution]

Hi

Is this a clean installation on what server os (I assume 2008 64 bit) or is it an upgrade? If it's an upgrade what version are you upgrading from? If you re-run the installer do you see the same error every time?

As kjetil is saying it would be interesting to check what the logs are saying but when it comes down to sharing logs I strongly recommend you to open a TAC case if this issue is consistent. It might be worth checking the GP's and / or if there might be any security software blocking the installation.

The windows eventviewer might also help you find what is going on.

/Magnus

[Darren Lapierre · Accepted solution]

I have seen this screen a few times.

Are you installing / upgrading using a domain admin account vs a local admin account? I have seen the install hang at the ldap install section.

Also, do you have any anti-virus software installed? If so, disable it, uninstall everything (including openDS), and try the install/upgrade again.

[Bar1s]

Hi gents,

This totally up to gp security.

So I did clean install with no domain.

Now i haven' t problem.

Regards,

Baris.

[andrie prabudhi]

hi baris,

I have same problem with you, the message always appears, I try to install on server 2008 and 2003, the message still pop up, please... give my step by step guide to fix it.

[Bar1s]

Hi Andrie,

I just simply install Win2008 x64 standart edition without join domain and install Tms without any error. I didnt any special configuration.

Also I am agree with Magnus new Provisioning Extension is better choice. I am strongly suggest new Provisioning Extension.

Regards,

Baris.

[Magnus Ohm]

Hi

I would recommend you to ignore any errors with opends and setup the new provisioning extension if you plan to setup provisioning. Then you wont have to migrate later.

/Magnus

Sent from Cisco Technical Support iPhone App

[andrie prabudhi]

Hi all,

it works, I am install on win2008 server without join domain and disable firewall windows, I hope ok too when using win2003,

I have another question again, 2 days ago I was uninstall tms when the errors show up, and then I try to reinstall again, but the tms always ask sql user&pass, while sql removed along tms, any part missing when I remove them?

thx

[Bar1s]

Hi Andrie,

Database files not removed when you uninstalling Sql or Tms.

So setup will ask password for existing database.

Regards,

Baris.

Sent from Cisco Technical Support iPhone App