GetNode API call fails in Content Server 10.0

We have an interface between our web product and Content Server. We are running version 10.0 with CSDS.

Our API sequence and results are described below.

Step 1: Authenticate

LivelinkCore.LivelinkAuthentication.AuthenticateUser(string userName, string userPassword)

This call returns a Token.

Step 2: Obtain the node

LivelinkCore.LivelinkDocumentManagement.Node GetNode(ref LivelinkCore.LivelinkDocumentManagement.OTAuthentication OTAuthentication, int ID)

for "ref LivelinkCore.LivelinkDocumentManagement.OTAuthentication OTAuthentication", we pass the token obtained in Step 1.

Result in the les.services log file:

2018-01-17 14:04:47,5593 INFO [7] Content Web Services 10.0.9 File Version: 10.0.9.1829
2018-01-17 14:04:47,5593 INFO [7] OS Version: Microsoft Windows NT 6.2.9200.0
2018-01-17 14:04:47,5593 INFO [7] CLR Version: 4.0.30319.42000
2018-01-17 14:04:47,5593 INFO [7] Machine Name: LIVELINK10
2018-01-17 14:04:47,5593 INFO [7] User Domain: OURDOMAIN
2018-01-17 14:04:47,5593 INFO [7] User Name: service.account
2018-01-17 14:04:47,5593 INFO [7] Command Line: c:\windows\system32\inetsrv\w3wp.exe -ap "OpenText - ECM" -v "v4.0" -l "webengine4.dll" -a \\.\pipe\iisipm0d6ca095-2984-4327-824d-051c64a655d1 -h "C:\inetpub\temp\apppools\OpenText - ECM\OpenText - ECM.config" -w "" -m 0 -t 20
2018-01-17 14:04:47,5593 INFO [7] Culture: en-US
2018-01-17 14:04:47,5593 INFO [7] ---------------
2018-01-17 14:04:52,6531 TRACE [9] Using BasicRequestContext
2018-01-17 14:04:52,6531 TRACE [9] static BasicServiceContext(): fDefaultHost = localhost, fDefaultPort = 2099, fDefaultEncoding = UTF8
2018-01-17 14:04:52,6531 TRACE [9] BasicServiceContext(): fServer = localhost, fServerPort = 2099, fServerEncoding = UTF8
2018-01-17 14:04:52,6531 TRACE [9] Service()
2018-01-17 14:04:52,6531 TRACE [9]   IServiceContext = BasicServiceContext[fServer=localhost,fServerPort=2099,fServerEncoding=UTF8]
2018-01-17 14:04:52,6531 TRACE [9]   IRequestContext = BasicRequestContext[fClientIPAddress=192.168.137.176,fServiceToken=,]
2018-01-17 14:04:53,6061 TRACE [9] begin: Authentication.AuthenticateUser(service.account,<password>)
2018-01-17 14:04:54,1530 TRACE [9] end:   Authentication.AuthenticateUser()
2018-01-17 14:04:54,7623 TRACE [9] BasicServiceContext(): fServer = localhost, fServerPort = 2099, fServerEncoding = UTF8
2018-01-17 14:04:54,7623 TRACE [9] Service()
2018-01-17 14:04:54,7623 TRACE [9]   IServiceContext = BasicServiceContext[fServer=localhost,fServerPort=2099,fServerEncoding=UTF8]
2018-01-17 14:04:54,7623 TRACE [9]   IRequestContext = BasicRequestContext[fClientIPAddress=192.168.137.176,fServiceToken=,]
2018-01-17 14:04:56,4811 TRACE [9]   IRequestContext.ServiceToken = v8%2BRewkUz6HhaRyHMiu%2BY%2Flh4cn1rTYBRhh3W7u2JlENRlj%2FE2Ae1ZOjvl5uzRpm
2018-01-17 14:04:56,4811 TRACE [9] begin: DocumentManagement.GetNode(79441)
2018-01-17 14:04:56,6374 TRACE [9] ThrowLivelinkException( -2147482645,The parameter is incorrect.,,,urn:DocMan.service.livelink.opentext.com)
2018-01-17 14:04:56,6374 WARN [9] Livelink error occurred
2018-01-17 14:04:56,6374 WARN [9]   Status: -2147482645
2018-01-17 14:04:56,6374 WARN [9]   Error Code: The parameter is incorrect.
2018-01-17 14:04:56,6374 WARN [9]   Error Message: The parameter is incorrect.
2018-01-17 14:04:56,6374 WARN [9]   ApiError:
2018-01-17 14:04:56,6686 TRACE [9]   IRequestContext.ServiceToken =

----------------------------

Can anyone out there help us to find out what is causing this issue? Is there another log we could look at? Is there any documentation on the status and error codes for this API?

Please advise - thank you!

Janice from WorkDynamics

Find more posts tagged with

Comments

AKropp

Hi Janice,

That error code looks like an unhandled exception. I suspect you’ll need to gather and analyze the Content Server logs themselves to see what’s going on. In opentext.ini set these parameters:

[General]

Debug=2

[Options]

WantLogs=True

WantLapiLogs=True

That should give you a full set with everything needed. Feel free to open a support ticket if you need a hand setting this up or analyzing the results and we’ll be happy to help.

Cheers,

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Wednesday, January 17, 2018 2:30 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: GetNode API call fails in Content Server 10.0

GetNode API call fails in Content Server 10.0

Posted byjmcguire@workdynamics.com (McGuire, Janice) On 01/17/2018 02:28 PM

We have an interface between our web product and Content Server. We are running version 10.0 with CSDS.

Our API sequence and results are described below.

Step 1: Authenticate

LivelinkCore.LivelinkAuthentication.AuthenticateUser(string userName, string userPassword)

This call returns a Token.

Step 2: Obtain the node

LivelinkCore.LivelinkDocumentManagement.Node GetNode(ref LivelinkCore.LivelinkDocumentManagement.OTAuthentication OTAuthentication, int ID)

for "ref LivelinkCore.LivelinkDocumentManagement.OTAuthentication OTAuthentication", we pass the token obtained in Step 1.

Result in the les.services log file:

2018-01-17 14:04:47,5593 INFO [7] Content Web Services 10.0.9 File Version: 10.0.9.1829
2018-01-17 14:04:47,5593 INFO [7] OS Version: Microsoft Windows NT 6.2.9200.0
2018-01-17 14:04:47,5593 INFO [7] CLR Version: 4.0.30319.42000
2018-01-17 14:04:47,5593 INFO [7] Machine Name: LIVELINK10
2018-01-17 14:04:47,5593 INFO [7] User Domain: OURDOMAIN
2018-01-17 14:04:47,5593 INFO [7] User Name: service.account
2018-01-17 14:04:47,5593 INFO [7] Command Line: c:\windows\system32\inetsrv\w3wp.exe -ap "OpenText - ECM" -v "v4.0" -l "webengine4.dll" -a\\.\pipe\iisipm0d6ca095-2984-4327-824d-051c64a655d1 -h "C:\inetpub\temp\apppools\OpenText - ECM\OpenText - ECM.config" -w "" -m 0 -t 20
2018-01-17 14:04:47,5593 INFO [7] Culture: en-US
2018-01-17 14:04:47,5593 INFO [7] ---------------
2018-01-17 14:04:52,6531 TRACE [9] Using BasicRequestContext
2018-01-17 14:04:52,6531 TRACE [9] static BasicServiceContext(): fDefaultHost = localhost, fDefaultPort = 2099, fDefaultEncoding = UTF8
2018-01-17 14:04:52,6531 TRACE [9] BasicServiceContext(): fServer = localhost, fServerPort = 2099, fServerEncoding = UTF8
2018-01-17 14:04:52,6531 TRACE [9] Service()
2018-01-17 14:04:52,6531 TRACE [9]   IServiceContext = BasicServiceContext[fServer=localhost,fServerPort=2099,fServerEncoding=UTF8]
2018-01-17 14:04:52,6531 TRACE [9]   IRequestContext = BasicRequestContext[fClientIPAddress=192.168.137.176,fServiceToken=,]
2018-01-17 14:04:53,6061 TRACE [9] begin: Authentication.AuthenticateUser(service.account,<password>)
2018-01-17 14:04:54,1530 TRACE [9] end:   Authentication.AuthenticateUser()
2018-01-17 14:04:54,7623 TRACE [9] BasicServiceContext(): fServer = localhost, fServerPort = 2099, fServerEncoding = UTF8
2018-01-17 14:04:54,7623 TRACE [9] Service()
2018-01-17 14:04:54,7623 TRACE [9]   IServiceContext = BasicServiceContext[fServer=localhost,fServerPort=2099,fServerEncoding=UTF8]
2018-01-17 14:04:54,7623 TRACE [9]   IRequestContext = BasicRequestContext[fClientIPAddress=192.168.137.176,fServiceToken=,]
2018-01-17 14:04:56,4811 TRACE [9]   IRequestContext.ServiceToken = v8%2BRewkUz6HhaRyHMiu%2BY%2Flh4cn1rTYBRhh3W7u2JlENRlj%2FE2Ae1ZOjvl5uzRpm
2018-01-17 14:04:56,4811 TRACE [9] begin: DocumentManagement.GetNode(79441)
2018-01-17 14:04:56,6374 TRACE [9] ThrowLivelinkException( -2147482645,The parameter is incorrect.,,,urn:DocMan.service.livelink.opentext.com)
2018-01-17 14:04:56,6374 WARN [9] Livelink error occurred
2018-01-17 14:04:56,6374 WARN [9]   Status: -2147482645
2018-01-17 14:04:56,6374 WARN [9]   Error Code: The parameter is incorrect.
2018-01-17 14:04:56,6374 WARN [9]   Error Message: The parameter is incorrect.
2018-01-17 14:04:56,6374 WARN [9]   ApiError:
2018-01-17 14:04:56,6686 TRACE [9]   IRequestContext.ServiceToken =

----------------------------

Can anyone out there help us to find out what is causing this issue? Is there another log we could look at? Is there any documentation on the status and error codes for this API?

Please advise - thank you!

Janice from WorkDynamics

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	My Support

jmcguire

Thank you very much, Alex!

We have generated the logs. Do they all get written to C:\OPENTEXT\logs on the server, or are any of them located in other folders?

jmcguire

We followed the instructions provided by Alex and found the following log entries in file "thread3.out" which appear to be relevant to our error:

01/18/2018 15:26:59 ------------------------------------------

01/18/2018 15:26:59 _LLENVIRON_ASSOC contains:

01/18/2018 15:26:59 REMOTE_ADDR=192.168.137.176

01/18/2018 15:26:59 End _LLENVIRON_ASSOC

01/18/2018 15:26:59 Login failed for user: , domain: , ip: 192.168.137.176

01/18/2018 15:26:59 Allocating UAPISession object for OTCS2010.

01/18/2018 15:26:59 ------------------------------------------

01/18/2018 15:26:59 inArgs: A<1,?,'Arguments'=A<1,?,'ID'=79441>,'ServiceMethod'='GetNode','ServiceName'='DocumentManagement','_ApiName'='InvokeService','_ClientVersion'='9.7.1','_ConnectionName'='','_Cookie'='v8%2BRewkUz6HhaRyHMiu%2BY5xhrjrO95B%2B6w1uqc3DH7Ad%2FdNUj8GGnS5xBEGN2o2q','_DomainName'='','_ImpersonateUserDomain'='','_LLENVIRON_ASSOC'=A<1,?,'REMOTE_ADDR'='192.168.137.176'>,'_Request'='llweb','_UserName'='','_UserPassword'='XXXXXXXXXX'>

01/18/2018 15:26:59 outArgs: A<1,?,'_apiError'='','_errMsg'='','_Status'=-2147482645,'_StatusMessage'='The parameter is incorrect.'>

01/18/2018 15:26:59 status: The parameter is incorrect. (-2147482645)

01/18/2018 15:26:59 msecs: 172

01/18/2018 15:26:59 =======================================

My developer says: "What I'm guessing is that our security token which is passed as _Cookie'='v8%2BRewkUz6HhaRyHMiu%2BY5xhrjrO95B%2B6w1uqc3DH7Ad%2FdNUj8GGnS5xBEGN2o2q' in the request is invalid. The cookie contains information which is incorrect, and we can't decrypt the cookie since we don't know the encryption used, the salt, the key."

I have a log file from a different test system, and that security token is much longer than ours and looks like this:

WiPQlVc%2Ba9xcIugbMxpM7P37nKI6uJXBnl%2B64YZCJD9cqytJI1lzmZcWVdTJ8bHy8r7uVXoML1SlBRHNvlSMd09xkwiWG9SjUzOO6os%2FQFg%3D .

We are wondering if the "%" sign is a delimiter in the token, and why the two tokens are such different lengths.

appuGmail

The simplest thing for you to do is you might have WSDL's that you might be sourcing,go to that server and find the application that the WSDL is configured

Now if the web.Config says localhost:2099 that means there's a livelink server running on it.

Try to bring the livelink's URL

usually it takes the form

http://<server>/<cgi>/livelink.exe

Does it come up with a userid/password form then use the same user and password as your code is using

note this is not your domain password but something an admin has set in livelink.

There could be many variations in the above

1)The link may not show you a userid/password form

2)It can be tied to a OTDS authentication mechanism

3)It can be a webserver that is IWA put.

The easiest is anonymous and a default deployment of OT webservices

If one of the above works then make sure that your developer code may be taking the cookie form one server and un bknownst to you the

server it is hitting might be a different one(All of those can be made to work)

Have a look at some links in my blog I used to do a lot of LL API dev and have undergone most of the usual problems developers face

https://appukili.wordpress.com/2015/02/23/common-debug-protocol/

https://appukili.wordpress.com/2013/06/07/content-server-cs10-single-sign-on/

https://appukili.wordpress.com/2013/02/16/single-sign-on-and-content-web-services-update/

OT has introduced OTDS as the authentication layer simply stated all requests to a livelink server CGI,SOAP all go to that and return a token,

this token or cookie is what will be used by livelink to let the user in.Your log makes me think that you are not a OTDS shop and perhaps the

web server which hosts your WSAPI has IWA whereas it needs anonymous scheme.

..... appnair appunair( Livelink Rocks )

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

On Fri, Jan 19, 2018 at 1:36 PM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

RE GetNode API call fails in Content Server 10.0 2 Posted byjmcguire@workdynamics.com (McGuire, Janice)On 01/19/2018 02:33 PM

We followed the instructions provided by Alex and found the following log entries in file "thread3.out" which appear to be relevant to our error:01/18/2018 15:26:59 ------------------------------------------01/18/2018 15:26:59 _LLENVIRON_ASSOC contains:01/18/2018 15:26:59 REMOTE_ADDR=192.168.137.17601/18/2018 15:26:59 End _LLENVIRON_ASSOC01/18/2018 15:26:59 Login failed for user: , domain: , ip: 192.168.137.17601/18/2018 15:26:59 Allocating UAPISession object for OTCS2010.01/18/2018 15:26:59 ------------------------------------------01/18/2018 15:26:59 inArgs: A<1,?,'Arguments'=A<1,?,'ID'=79441>,'ServiceMethod'='GetNode','ServiceName'='DocumentManagement','_ApiName'='InvokeService','_ClientVersion'='9.7.1','_ConnectionName'='','_Cookie'='v8%2BRewkUz6HhaRyHMiu%2BY5xhrjrO95B%2B6w1uqc3DH7Ad%2FdNUj8GGnS5xBEGN2o2q','_DomainName'='','_ImpersonateUserDomain'='','_LLENVIRON_ASSOC'=A<1,?,'REMOTE_ADDR'='192.168.137.176'>,'_Request'='llweb','_UserName'='','_UserPassword'='XXXXXXXXXX'>01/18/2018 15:26:59 outArgs: A<1,?,'_apiError'='','_errMsg'='','_Status'=-2147482645,'_StatusMessage'='The parameter is incorrect.'>01/18/2018 15:26:59 status: The parameter is incorrect. (-2147482645)01/18/2018 15:26:59 msecs: 17201/18/2018 15:26:59 ======================================= My developer says: "What I'm guessing is that our security token which is passed as _Cookie'='v8%2BRewkUz6HhaRyHMiu%2BY5xhrjrO95B%2B6w1uqc3DH7Ad%2FdNUj8GGnS5xBEGN2o2q' in the request is invalid. The cookie contains information which is incorrect, and we can't decrypt the cookie since we don't know the encryption used, the salt, the key."I have a log file from a different test system, and that security token is much longer than ours and looks like this:WiPQlVc%2Ba9xcIugbMxpM7P37nKI6uJXBnl%2B64YZCJD9cqytJI1lzmZcWVdTJ8bHy8r7uVXoML1SlBRHNvlSMd09xkwiWG9SjUzOO6os%2FQFg%3D .We are wondering if the "%" sign is a delimiter in the token, and why the two tokens are such different lengths.
[To post a comment, use the normal reply function]
Topic: GetNode API call fails in Content Server 10.0
Forum: Content Server Development Forum
Content Server: My Support

AKropp

Hi Janice,

The % characters you see are because the values are URL-encoded. For example, on your working token you’ll see it ends in %3D which is actually an = (equals) sign. Now that you mention it, I think whenever I’ve looked at a token value it always ends in %3D or = (depending on if I’m seeing it URL-encoded or not). Yours pretty clearly does not.

Might want to look closer at your authentication code and step through in the debugger. Just to extract the salient lines from the C# samples the bare minimum without any error handling would be something like:

AuthenticationClient authClient = new AuthenticationClient(); //create service client

string authToken = authClient.AuthenticateUser(username, password); //authenticate user

OTAuthentication otAuth = new OTAuthentication(); //create OTAuthentication object

otAuth.AuthenticationToken = authToken; //populate object

DocumentManagementClient docManClient = new DocumentManagementClient(); //create service client

Node myNode = (ref otAuth, 123456); //passing in OTAuthentication object by reference, nodeID

I also just noticed you mentioned CSDS being in the picture in your original message… unfortunately I do not know if there are any additional considerations when that’s involved. I know the above snippet will work with livelink auth and with sync’d OTDS users, but CSDS isn’t something I’ve ever had any experience with. If someone else out there has done the auth against CSDS via CWS maybe they can chime in if there’s an extra hurdle there.

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Friday, January 19, 2018 2:36 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: RE GetNode API call fails in Content Server 10.0 2

RE GetNode API call fails in Content Server 10.0 2

Posted byjmcguire@workdynamics.com (McGuire, Janice) On 01/19/2018 02:33 PM

We followed the instructions provided by Alex and found the following log entries in file "thread3.out" which appear to be relevant to our error:

01/18/2018 15:26:59 ------------------------------------------

01/18/2018 15:26:59 _LLENVIRON_ASSOC contains:

01/18/2018 15:26:59 REMOTE_ADDR=192.168.137.176

01/18/2018 15:26:59 End _LLENVIRON_ASSOC

01/18/2018 15:26:59 Login failed for user: , domain: , ip: 192.168.137.176

01/18/2018 15:26:59 Allocating UAPISession object for OTCS2010.

01/18/2018 15:26:59 ------------------------------------------

01/18/2018 15:26:59 outArgs: A<1,?,'_apiError'='','_errMsg'='','_Status'=-2147482645,'_StatusMessage'='The parameter is incorrect.'>

01/18/2018 15:26:59 status: The parameter is incorrect. (-2147482645)

01/18/2018 15:26:59 msecs: 172

01/18/2018 15:26:59 =======================================

I have a log file from a different test system, and that security token is much longer than ours and looks like this:

WiPQlVc%2Ba9xcIugbMxpM7P37nKI6uJXBnl%2B64YZCJD9cqytJI1lzmZcWVdTJ8bHy8r7uVXoML1SlBRHNvlSMd09xkwiWG9SjUzOO6os%2FQFg%3D .

We are wondering if the "%" sign is a delimiter in the token, and why the two tokens are such different lengths.

[To post a comment, use the normal reply function]
Topic:	GetNode API call fails in Content Server 10.0
Forum:	Content Server Development Forum
Content Server:	My Support