Tracking down a CMSA Asset in ContentSpace for deletion

Tracking down a CMSA Asset in ContentSpace for deletion:
Sometimes, a customer might face the “ALC-ACM-002-001″ error in CMSA Asset Manager for an asset when trying to delete it.

As per one of the customer, the error details are as follows,

It doesn't show any details on the Letter Edit screen and doesn't preview either. So at the moment you can't edit/delete, it is stuck. How to clear the system from this asset?

Error Ref:

Code ALC-ACM-002-001 (Solutions - Asset Composer)

Type Error

Cause Provide valid object identifier for the {0}.

Action An invalid object identifier was given. Verify that the object identifier is valid (not null and not empty).
Reason:

This error may occur due to one of the possible reasons,

1. Either the asset itself has gone corrupt.

2. It’s quite possible that the asset might have got deleted in the background but the related index didn’t get flushed. Hence, due to the stale index it’s still showing up in the search results.
Solution:

When the asset itself is corrupt

Then we need to remove it from the ContentSpace as follows,

a. Login to ContentSpace UI with admin credentials, http://server:port/contentspace

b. Go to Administration Console and click on Node Browser, http://server:port/contentspace/faces/jsp/dialog/container.jsp

ContentSpace Administration Console

c. Select the Store Reference as, workspace://SpacesStore.

ContentSpace Node Browser

d. Select ‘lucene’ as the Search Type from the drop down and type in the following query and click Search,

‘TYPE:Asset_Type\:Asset_Type AND @Asset\:name:Asset_Name’

e.g. Let say you want to search for a Letter named “Policy Jacket”, then the Lucene query would be,

TYPE:Letter\:Letter AND @Asset\:name:”PolicyJacket”

ContentSpace Lucene Search

e. In the result, click on the link in the Name field.

ContentSpace Lucene Result

f. There will be a primary path detailing the actual path of the Node in ContentSpace.

Primary Path of a CMSA Asset in ContentSpace

g. Follow the path in the Company Home-> Data Store UI and delete the Node.

Tracking the CMSA Asset in Data Store

When the index is corrupt

a. Stop the Application Server.

b. Go to \\Adobe\Adobe LiveCycle ES2\lccs_data folder.

b. Move the folder ‘lucene-indexes’ as backup to somewhere safe.

c. Start the Application Server to generate the indexes fresh.

DIGITAL JUICE