I search of a Livelink miracle for multiple Livelink problems

[ombra17]

I work for an organization that implemented Livelink approximately 1 year ago. Since the deployment of LL we have experienced our fair share of problems but managed to get the document management application working moderately smoothly and problem free, until recently. Now a number of our users are unable to access LL Explorer 4.2. They are receiving the following error messages:

·Unable to establish connection with Livelink server. Error occurred in the security provider library.
·Unable to connect to “name of server”. Do you want to switch to offline mode for this server?
·Server Unavailable. Error=[0x80040234]
·Invalid username and password. *We are receiving this message even though NTLM Directory Services Authentication is active.

*They are able to access LL Browser 9.1 but occasionally encounter the same symptoms.

Not all of our users have reported problems with Livelink Explorer but I have reason to believe that the majority of them have given up and have simply not made an effort to notify our Help Desk.

We have performed the following steps in an attempt to resolve our dilemma but have made no progress:
·Brought in OpenText consultants – were unable to pinpoint the cause or root of our problem.
·Re-imaged computer.
·Reset user’s roaming profiles.
·Moved computer to a different subnet and/or moved computer to another data/com-port
·Released and renewed computer’s IP address and DNS
·Performed packet sniffing (still waiting for those results)
·Server side upgrades and patches
·Disabled firewall and anti-virus software


We have pretty much taken every possible direction and route that our IT department and OpenText could think off. What I’m asking for is something maybe out of the ordinary that we haven’t thought of yet. Something so bizarre that it would make me question the possible solution. Anything really. Any suggestions would be greatly appreciated.

 

[appnair]

If you run logs with 2 or 11 in the opentext.ini file you should be able to see who is connecting and how(remote user)
employ logs at web server and take alook at there too.I believe LLexplorer uses probably not LAPI but something similar.You say you are using NTLM.We employ hidden passwords here so the livelink admin can actually see the
hidden passwords in a log file.As a last resort when you get the error for the explorer user you can take that userid/password and actually try logging in to the http interface.Hope I am making sense.You should really try to mimimize the variables in trouble shooting rather than try everything at once for which you could install another livelink server without directory services and try asking users to connect using regular/userid /password.How frequently do you rest passwords?

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[elaap1234]

There is a problem with LLExplorer 4.2 in the environment you describe. [highlight]By upgrading to 4.4.2 the problems should be resolved.[/highlight] The problems you have experienced are also covered in the release notes for version 4.4.2.

 

[VOLFONI]

Hi,
make a "reset user pasword" for all user in Admin pages. Even if authentication is based on Directory service and therefore in the LDAP, some credentials are -surprinsingly - still in the DB. Reseting solves some problems

hi