"Error connecting to the local LDAP server" (OpenDS&TMS13.2.1)

[Martin Koch]

Did anyone else see this error, when accessing the (Legacy) Provisioning Directory in TMS 13.2.1.

It was upgraded from TMS13.1.2 earlier which worked like a charm. After the upgrade everything looked ok.

Error connecting to the local LDAP server The specified base DN cannot be found, please enter a valid base DN. Will try to reconnect in 5 seconds...

The "Verify that OpenDS is available." and index diagnostics on the local agent show: "Not completed within the timeout of 90 seconds."

If I restart (the started) OpenDS service it looked ok before, but it stopped working again afte some time

Some other things in addition:

OpenDS itself seems to answer, I can see in the problematic state that port 389 is open and I can connect with an ldap

browser to it, but it only shows the root. After restarting it also shows the dc=provisioning.

Last time the restart of opends showed this symptom in the provisioning directory:

[UNKNOWN MODEL/VERSION:] upfront all parameters.

After a complete TMS reboot it shows up fine again.

TMS is running on Win2003 with an express database on a virtual machine with 4gb ram, latest win updates

present and Java says its: build 1.6.0_33-b03

Any clue what could be the cause? If I see it happen again I guess I will open a TAC case for it.

Martin

[Martin Koch]

Dale: are there any plans to fix these limitations (I would hope that there are plans, ...) and what

is the timeframe to remove the "legacy" opends from TMS and VCS.

[daleritc]

Hi Martin,

Which limitations, i.e. in Legacy TMS Agent?

And Legacy TMS Agent will be removed from TMS (since it was embedded with TMS) in the next major TMS version release...which is TMS 14.1 (out in Dec 2102). On the VCS side, they will remove it in x8.0. Release time frame for x8.0 is late summer 2013.

/dale

[Magnus Ohm]

[Justin Ferello]

lol, nice.

Justin

[Martin Koch]

Mr Ohm,

Resistance is NOT futile.. It's Voltage divided by Current!

[Patrick Sparkman]

Dale - What will happen to users who haven't migrated to TMSPE by the next TMS 14 release, and they try to update their version of TMS?

[daleritc]

Hi Patrick,

Good question...and the answer is simply, you won't be able to upgrade to TMS 14.1 if your still running Legacy TMS Agent, i.e. the installer will detect your running Legacy TMS Agent and stop the upgrade. Therefore, this means that if you want to continue to use Legacy TMS Agent, then you can only go as far as the last TMS 13.x.x release. And this is why we're encouraging everyone to migrate to TMSPE...being that TMSPE...albeit a different name is an evolution of Legacy TMS Agent, although I know I'll probably get arguments otherwise

cheers,

Dale