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
