LLIllegalOperationException calling LAPI_DOCUMENTS.CreateVersion

Jean_Royer_(eu0015968_-_(deleted))

Hi there,we get"com.opentext.api.LLIllegalOperationException: get(name) not implemented for this datatype"callingLAPI_DOCUMENTS.CreateVersion( 0, OID, path, versionInfo )from Java (see attachment for details on stacktrace and code).Now the funny thing is: This worked fine until the machine was upgraded to windows 2003.To make it even stranger: This error appeared, dispappeared and reappeared on my machine without any obvious reason. Once I changed the classpath using the same jars from an other location (c drive instead of d drive), and this made the error dispappear for a while. but this behaviour is not reproducible! Regarding the stacktrace this should either always work or never. Any idea what may be behind?

eLink User

Message from Carsten Kulms via eLinkOften this error indicates that something went really wrong in theexecution of the function at LES. Please check if there are anytrace...log files (written only if at least "detailed log level" isactivated). I don't think that the problem is caused by the upgrade to Win3k or theclasspath setting.You may also look at the following topics in this discussion for someexamples when and why this error can occur:https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=11341622&objAction=viewhttps://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=11341622&objAction=view&show=2For the interested reader some technical background:The stacktrace shows that the error occurs when the response from LES isto be evaluated by the client side LAPI code. Function parameters andreturn values are transfered via the `wire` in a special format ofLLValue-s ("marshalled"). The same applies LAPI-internal data, e.g. whatfunction to call at the LES and the overall status of the call (onreply): These items are transferred as fields of an Assoc.If, e.g. the execution of the LAPI function aborted at LES, then it mayhappen that no or no correct response is generated by LES. In that caseeven not the status information can be `unmarshalled` at the client. I.e. the (internal) Assoc which holds this data is missing. Then theattempt of the client LAPI code to read e.g. the status field willresult in "LLIllegalOperationException: get(name) not implemented forthis datatype" because the LLValue object worked with does not supportthis field access function (it is not an Assoc or Record; likely it is aUNDEFINED LLValue.)