Help in debuging an issue with LiveLink 9.5

[kamilx2]

Hello
I try to log in to a Web Gui Console with Admin account and get the error message "LiveLink Error: Error Logging in. Couldn't connect" (I know that if it was a problem with incorrect user or password then the message would be different than that.
Could you advice me how to start debugging the issue?

Best Regards.
Kamil

 

[appnair]

put debug=2 wantlogs=true Then if you are completely new right under the loader section there is a min/max thread indicator which would say 5 change that to 1 and re-start
Keep Security as Livelink and make your webserver anonymous.

Then try if you get the message again then look in the connect logs for what the LL software has in the start does it indicate something like Ksql allocationg login.
The livelink threads are client to Oracle or SQlserver. If it indicates failure use the DB connection user and see if you can connect from the same box to the db in question.

The Admin user you are trying is a KUAF user.KUAF comes into play only if LL can connect to the database.If you can rule that out and assure it is the right database go to another 9.5 livelink steal that Admin user's password update it on this databse and try.If it is the admin.index password you have forgotten then it is also easy to reset.

Note stealing the Admin user's password will not work if the <OTHOME> of two different database livelink's are also different say your production has been installed in c:\OpenText and in TEST you have that as f:\oneoflivelink\opentext then that would not jive because that is used in the seeding of the password

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in

 

[kamilx2]

I found this entry:
"KSql::Connect('ACLLDB','','livelinkuser','*','APIEngine','API100') --> 'Could not connect.',[sec: 0 msec: 24]" in the log file and then fix the issue.
Thank you for help.

 

[LAMINI]

With an OT SUpport contract, as this is a common issue, they have a "fix" in the case events like this happen.