I get exactly the same thing.
Does anyone got any ideas as to what would resolve this problem?
To resolve your problem one needs to know how livelink is setup in your org
If you ask your livelink administrator for a webgui login and he gives out this
http://<mycompany>/livelink/livelink.exe|llisapi.dll|livelink when you try this does your livelink show you a login form then for lapi methods it is using livelink authentication.So your session is made like
(servername,lapiport,lapisuser,lapipassword) here lapiport is the livelink server port usually 2099 and the user and password is a valid livelink user.
to the If you go staright in at the URL then some sort of SSO is employed so the session becomes to the webserver as in SSO scenarios it is the webserver who authenticates you and passes you to livelink.Something similar to this code if the livelink is on a webserver(iis) can be attempted.It has always worked for me.
http://communities.opentext.com/communities/llisapi.dll/open/2124975
Now if your livelink is a on a java tomcat deployment or apache then you will need to sort out whether livelink auth or sso auth is at play here.A tool called 'lapi test connection' utility which you can find in the KB can be used to figure that one out.
LAPI is pretty old and obsolete,do you still want to work with it?
