Mandatory aspect missing on locked node - unable to perform any action on the node

[jjacobwip]

Hi,

I have a weird scenario where a document is missing a mandatory aspect (aspect got added to content model after the creation of node) and it is in locked state. I think it ended up in this state because the node was in locked state when the aspect change happened.

I cant add the aspect manually as Alfresco complains that the node is locked. I cant delete/unlock (using LockService) the node because it throws integrity check errors complaining that mandatory aspects are missing.

How do I delete/add the missing aspect/unlock this document?

Any help is appreciated.

Thanks,
Jerry

[jpotts]

Have you tried using CMIS to cancel the checkout?

Jeff

[jjacobwip]

Thanks Jeff.

I tried to query this document through CMIS Workbench and I am getting the below exception. It looks like this node is in a real messed up state. If there is any way I can delete it, that'll be great. 

Caused by: org.alfresco.service.cmr.repository.TemplateException: 11110351 Error during processing of the template 'Expression node.nodeRef is undefined on line 175, column 33 in org/alfresco/cmis/lib/links.lib.atom.ftl.'. Please contact your system administrator.
        at org.alfresco.repo.template.FreeMarkerProcessor.process(FreeMarkerProcessor.java:206)
        at org.springframework.extensions.webscripts.AbstractWebScript.renderTemplate(AbstractWebScript.java:876)
        at org.springframework.extensions.webscripts.DeclarativeWebScript.renderFormatTemplate(DeclarativeWebScript.java:267)
        at org.springframework.extensions.webscripts.DeclarativeWebScript.execute(DeclarativeWebScript.java:147)
        … 25 more
Caused by: freemarker.core.InvalidReferenceException: Expression node.nodeRef is undefined on line 175, column 33 in org/alfresco/cmis/lib/links.lib.atom.ftl.
‍‍‍‍‍‍‍‍‍

[jpotts]

If you have Enterprise support you should open a ticket. If you don't, you might see if someone in IRC (#alfresco on freenode) can help you delete it by making updates to the database directly.

If you don't already have any nodes created with that aspect you could shut down your server, remove the aspect from your content model, restart, delete the node, shut down, add the aspect back to your content model, and then move forward. But I suspect it is too late for that.

Jeff

[jjacobwip]

We already have content created with this aspect. We'll work with the support team to get it resolved.

Thanks again for your inputs.