Error in CWS app after upgrading to CS16

I had created a CWS app that allowed users to create a folder structure with specific categories and permissions, a sort of "template" for an often used area of Content Server.

I am in process of doing my first test upgrade to CS16. After upgrading to CS16, I am receiving an error when running the application that I am not quite sure how to debug as the error simply says "an unknown error occurred".

I have not changed my code, I simply connected out to the newest version of CWS for each service used in my app. It seems like it can connect as the first step I do is authenticate as the "Admin" user and then check that the user has permissions to the folder they are trying to add this template to. That step works just fine.

The next step, when I call the "GetCategoryDefinition" of the Document Management service is where this "unknown error" occurs. Does anyone know of any thing that may have changed when upgrading from CS10.5 to CS16 in regards to CWS that I should look into as a potential cause of this error?

At first I thought maybe authentication, but we had already previously switched to OTDS well before the CS16 upgrade and the authentication part seems to be working just fine even in CS16.

Find more posts tagged with

Comments

appuGmail

You could enable these on the LL server

Debug=2, wantlogs=true, wantlapilogs=true

instead of doing GetCategoryDefinition try to get the Node Object of the Category

that way you know if you are indeed getting category objects its type(subtype) should say 131.

Usually code is backwards compatible but lost of products,modules,patches etc make the OT effort

rather complicated.Recently another poster complained of problems and an OT official said to upgrade to the latest and greatest

after I had debugged his trace conditions.

If a server trace is found then it is easier sometimes with API's server traces wont happen and client code has to be debugged.

..... 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 Tue, Jan 10, 2017 at 9:33 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Error in CWS app after upgrading to CS16 Posted byGorczyca, AJOn 01/10/2017 09:57 AM

I had created a CWS app that allowed users to create a folder structure with specific categories and permissions, a sort of "template" for an often used area of Content Server.I am in process of doing my first test upgrade to CS16. After upgrading to CS16, I am receiving an error when running the application that I am not quite sure how to debug as the error simply says "an unknown error occurred". I have not changed my code, I simply connected out to the newest version of CWS for each service used in my app. It seems like it can connect as the first step I do is authenticate as the "Admin" user and then check that the user has permissions to the folder they are trying to add this template to. That step works just fine.The next step, when I call the "GetCategoryDefinition" of the Document Management service is where this "unknown error" occurs. Does anyone know of any thing that may have changed when upgrading from CS10.5 to CS16 in regards to CWS that I should look into as a potential cause of this error?At first I thought maybe authentication, but we had already previously switched to OTDS well before the CS16 upgrade and the authentication part seems to be working just fine even in CS16.
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center CS16

AKropp

Hi AJ,

Maybe a quick and easy win… have you updated your service references/proxies? Sometimes that’s all it takes, and is something I would always recommend doing after an update/upgrade.

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, January 10, 2017 10:33 AM
To: eLink Recipient
Subject: Error in CWS app after upgrading to CS16

Error in CWS app after upgrading to CS16

Posted by Gorczyca, AJ On 01/10/2017 09:57 AM

I had created a CWS app that allowed users to create a folder structure with specific categories and permissions, a sort of "template" for an often used area of Content Server.

At first I thought maybe authentication, but we had already previously switched to OTDS well before the CS16 upgrade and the authentication part seems to be working just fine even in CS16.

[To post a comment, use the normal reply function]
Forum:	Content Web Services Forum
Content Server:	Knowledge Center CS16

AJ Gorczyca

Is wantLapiLogs still valid for CS16? I don't see any server trace logs after running my app, so not sure if server logs will be all that helpful. Is a trace file the only useful log to look in for trying to do CS debugginf on this?

AKropp

Yes it still works – main thing you’ll get is InArgs and OutArgs printed into the thread logs as assoc values so make sure you have debug=2 as well. Might help you see if something is missing from the input arguments or if the output has some error code or other unexpected data. Fiddler may be another useful data point to examine the SOAP envelopes going back and forth (or in the browser use F12 then capture a trace on the Network tab there as XML – this can be imported into Fiddler for easy reading).

Don’t hesitate to open a ticket with support if you need an extra pair of eyes on this one.

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, January 10, 2017 11:45 AM
To: eLink Recipient
Subject: Re Error in CWS app after upgrading to CS16

Re Error in CWS app after upgrading to CS16

Posted by Gorczyca, AJ On 01/10/2017 11:37 AM

[To post a comment, use the normal reply function]
Topic:	Error in CWS app after upgrading to CS16
Forum:	Content Web Services Forum
Content Server:	Knowledge Center CS16

AJ Gorczyca

Thanks Alex, maybe I will open a ticket. I tried 1st person who responded suggestion to simply attempt to get the node without getting the CategoryDefinition to ensure that the Document Management service was working a returning a Category object for the ID I was passing in.

Turns out that yes, the service itself is working as the node i got back was the expected Category node. For some reason there is an issue specific to me trying to use the one function of the Document Management service.

And yes, I did run a service update after repointing the the new CS16 services, so sadly I dont' think the easy fix is the answer.

Appu_Nair1

You should try what Alex Kropp said .I would have as well.WantlapiLogs is still valid for the time being ,my interpretation of that

is L API-Livelink API ,not to be confused with the old LAPI product.I ran than on a 16 I had and I see <inargs and <outargs and they do. Inargs is what your clinet program send outargs is what the LLserver sends back.If outargs dont have an error but still client produces an error it could be proxy related.