Update Node error

Hello,

I've written a program in .NET that will update the attributes of Emails stored in Livelink.

However, when I call UpdateNode the server logs suggest an error has been thrown and the attributes do not get updated. Below is the error:

DocMan.NodeIdAndNodeTypeConflict

Further checking of the logs suggests that the Node ID is correct and the Node Type is 'Generic Node'.

The problem is sporadic. Sometimes it will update the attributes but most of the time it doesn't.

Has anyone seen this error/know what causes it?

Thanks

Find more posts tagged with

Comments

sgrasley

Email nodes are not supported by the web services (because there is no ServiceNode implementation for that subtype). As a result, retrieving an email node results in a Node with type GenericNode, which is why you're getting that error.

Andrew_Coyle

Why does it sometimes work then?

I am not importing the emails. I am grabbing the category defintition of a custom category and changing the attribute values. Sometimes it will update succesfully, other times not.

Thanks

sgrasley

Hi, Andrew.

For which type of node are you updating the attributes?

Thanks,

Scott

Andrew_Coyle

An email node.

Below are the web service logs:

First, a succesful update:

2010-04-07 15:26:12,1916 TRACE [8] begin: DocumentManagement.UpdateNode(Node[fCatalog=0,fComment=,fContainerInfo=,fCreateDate=11/03/2010 14:37:33,fCreatedBy=1000,fDisplayType=Unknown,fFeatures=,fID=208235,fIsContainer=False,fIsReference=False,fIsReservable=False,fIsVersionable=False,fMetadata=Metadata[fAttributeGroups=OpenText.Livelink.Service.DocMan.AttributeGroup[],]OpenText.Livelink.Service.DocMan.Metadata,fModifyDate=30/03/2010 17:42:01,fName=Fw Glencore comments againt Longpeng l/c application 2,fNickname=,fParentID=251187,fPartialData=False,fPermissions=NodePermissions[fAddItemsPermission=True,fDeletePermission=True,fDeleteVersionsPermission=True,fEditAttributesPermission=True,fEditPermissionsPermission=False,fModifyPermission=True,fReservePermission=True,fSeeContentsPermission=True,fSeePermission=True,]OpenText.Livelink.Service.DocMan.NodePermissions,fPosition=,fReferenceInfo=,fReleased=False,fReservationInfo=,fType=GenericNode,fVersionInfo=,fVolumeID=-2000,]OpenText.Livelink.Service.DocMan.Node)
2010-04-07 15:26:12,2698 TRACE [8] end: DocumentManagement.UpdateNode()

Then an unsuccesful update:

2010-04-07 15:26:12,7229 TRACE [8] begin: DocumentManagement.UpdateNode(Node[fCatalog=0,fComment=,fContainerInfo=,fCreateDate=11/03/2010 14:37:33,fCreatedBy=1000,fDisplayType=Unknown,fFeatures=,fID=208235,fIsContainer=False,fIsReference=False,fIsReservable=False,fIsVersionable=False,fMetadata=Metadata[fAttributeGroups=OpenText.Livelink.Service.DocMan.AttributeGroup[],]OpenText.Livelink.Service.DocMan.Metadata,fModifyDate=07/04/2010 15:26:12,fName=Fw Glencore comments againt Longpeng l/c application 2,fNickname=,fParentID=251187,fPartialData=False,fPermissions=NodePermissions[fAddItemsPermission=True,fDeletePermission=True,fDeleteVersionsPermission=True,fEditAttributesPermission=True,fEditPermissionsPermission=False,fModifyPermission=True,fReservePermission=True,fSeeContentsPermission=True,fSeePermission=True,]OpenText.Livelink.Service.DocMan.NodePermissions,fPosition=,fReferenceInfo=,fReleased=False,fReservationInfo=,fType=GenericNode,fVersionInfo=,fVolumeID=-2000,]OpenText.Livelink.Service.DocMan.Node)
2010-04-07 15:26:12,7385 TRACE [8] ThrowLivelinkException( 903101,DocMan.NodeIdAndNodeTypeConflict,The Node ID and Node Type conflict.,,urn:DocMan.service.livelink.opentext.com)
2010-04-07 15:26:12,7385 WARN [8] Livelink error occurred
2010-04-07 15:26:12,7385 WARN [8]   Status: 903101
2010-04-07 15:26:12,7385 WARN [8]   Error Code: DocMan.NodeIdAndNodeTypeConflict
2010-04-07 15:26:12,7541 WARN [8]   Error Message: The Node ID and Node Type conflict.
2010-04-07 15:26:12,7541 WARN [8]   ApiError:

The same Node object is passed through to the method, the same document etc. Seems very strange.

sgrasley

Hi, Andrew.

I would expect the update to always be unsuccessful... I'll have to investigate further.

Thanks,

Scott

Andrew_Coyle

Further testing this morning shows the metadata is being passed through exactly the same when it fails and when it's succesful. There seems to be no consistency to the methods failure.

Andrew_Coyle

I have implemented a temporary fix and am sharing it here for anyone else who finds this problem.

Since updatenode seems to work about 1 out of every 2 times, I put a loop around updatenode, catching the exception that is thrown and telling the loop that it hasn't worked, at which point the method is called again until it is succesful.

I set a max number of loops to ensure it doesn't get tied up with another problem.

Not the best solution, but it works for now until I can fix it properly.