Error saving metadata. Node does not exist...

[joaotpd]

Hi all,

I'm using alfresco/share 3.4.3 in linux.

I'm facing a issue when I try to save matadata changes for a space in share and in alfresco webclient.
In share i'm getting:

org.alfresco.service.cmr.repository.InvalidNodeRefException: Node does not exist: workspace://SpacesStore…‍

In alfresco webclient I get:

Fail to create new space: Node does not exist: workspace://SpacesStore…‍

The node in fact does not exist… I've search it in node browser… and I've already done a full re-index…

Anyone with the same problem? … I need to be able to update the metadata for this space… any ideas?

Thanks in advance…

João

[afaust]

Hello,

if the node does not exist, why would you want to update it? It might be that you have the wrong nodeRef for the space you want to update. How did you retrieve it to build your request? What API are you using (Forms API / Metadata ReST API)?

Regards
Axel

[joaotpd]

Hi,

Thanks for the answer…

The node I want to update exists. I can find it in node browser. But, when i try to update it, by changing his metadata, it says that ANOTHER NODE doesn't exist… My request is done in UI, webclient and share.

I suspect that the node refers another one that doesn't exist anymore… but, node browser shows is associations empty…

Thanks again,

João

[joaotpd]

… How can I "clean" this association? … or find out what's happening?? …

His there a way?! … …

Thanks,

João

[wabson]

Hi João,

When you say you are trying to save the metadata, what do you mean by this? Are you writing a web script or some other customisation that is trying to save some information, or are you simply using the Share application in its normal out-of-the-box state?

It seems to me that this is not really a development question, and should be asked in one of the user forums, but if I am wrong then please correct me.

Cheers,
Will

[joaotpd]

Hi,

Thanks for the reply…

The situation has been found by users in share interface. Then i try to update the node, using the webclient interface (without success) and then using a javascript that follows (thinking maybe its the "taggable" property):

var nodes = search.luceneSearch("@cm\\:name:\"NODENAME\"");
for each (var node in nodes) {
        node.properties["cm:taggable"] = null;
        node.save();
}‍‍‍‍‍

… when the script is executed… it returns the same: Node does not exist: workspace://SpacesStore…

I've put this question under this section because I think it's an issue that developers could help… but, maybe it's not the proper place… … I've no problem in move this to correct place… …

Thanks,

João

[wabson]

Hi João,

I would suggest you use the Node Browser to work out how the missing node is linked to this one. You suggest in an earlier post that it is an association, but you don't explain what led you to think that.

Generally I would say this is a highly unusual situation. I have seen problems with Lucene indexes previously but if you have deleted these and performed a full re-index I don't see how the problem could still be there. All I can think of is that some low-level operations at the DB or API level have resulted in this corruption - could that be the case?

Thanks,
Will

[joaotpd]

Hi Will,

Thanks for the help!

The node in question has the aspect "cm:taggable" and an association defined. So, my first thought was that one of its associations has been deleted… with this in mind I've done the full re-index without success.

The Node Browser shows the property "taggable" with value "–collection–" and the table "Associations" (with columns "To Node" and "Association Type") have no records.

I didn't do any low level operations.

What could be my next step? … …

João

[wabson]

Hi João,

If that's all the data that's available from the Node Browser then there seems to be little you can do to troubleshoot where the missing node is being referred from from the UI, if that is even the case.

Instead, I would suggest that you simply create a new space at the same level as the old one, move all the contents into the new space, and then remove the old one. It will be much quicker than spending a long time troubleshooting the exact problem.

If you have further problems, I would suggest you start a new thread in the general Content Management forum, since you are more likely to get the help you need there.

Cheers,
Will