cancel
Showing results for 
Search instead for 
Did you mean: 

Node does not exist Error inAlfresco enterprise edition 4.0

sukhbir
Champ in-the-making
Champ in-the-making
Hello Friends,

I have downloaded the Alfresco Enterprise edition 4.0 and started exploring it. Successfully installed the Alfresco 4.0 on the cloud machine.
While creating the tenants i am facing following issue

Steps
I created tenant using “create s3 /mnt/s3” using tenant admin console though it shows error on the browser but creates a tenant folder inside the s3 mapped drive (/mnt/s3)

Error
org.alfresco.service.cmr.repository.InvalidNodeRefException: Node does not exist: workspace://@s3@SpacesStore/91bb701b-620e-4851-927b-d20130745e27(null)

Can you please help me for this.

Regards,
Suukhbir
3 REPLIES 3

sukhbir
Champ in-the-making
Champ in-the-making
Hey guys,

it is resolved now.

We have mounted the drive but not created folders inside it. These folders created mainly for the tenant domain in muti-tenancy.
It is possible to map the s3 drive to alfresco for the multi-tenancy feature.


Regards,
Suukhbir

tnielsen91
Champ in-the-making
Champ in-the-making
Hi!  We are having the exact same issue.  Can you outline the steps you did to resolve the problem?  Thanks!

csering
Champ in-the-making
Champ in-the-making
I know this question is old, but I'd like to document our solution for the same issue.

We previously had 10 or so tenants already set up and was seeing this error when trying to create an additional tenant. We had just finished a large migration of content from an old Alfresco server to the current server, so I suspected we might need to reindex upon seeing the error. Note that our system had SOLR disabled and was using Lucene, so I forced a full reindex by setting index.recovery.mode=FULL in alfresco-global.properties and restarted. Remember to set index.recovery.mode back to AUTO after reindexing. WARNING: Doing a full reindex on a system with a high number of documents can take a very long time. Proceed with caution.

You could probably do the same in a SOLR-enabled environment by deleting your SOLR indexes and restarting.