02-22-2015 08:51 PM
java.lang.IllegalStateException - Non-unique path: found : /app:company_home/app:user_homes 0
org.alfresco.repo.security.person.PortableHomeFolderManager.resolvePath(PortableHomeFolderManager.java:308)
org.alfresco.repo.security.person.PortableHomeFolderManager.getRootPathNodeRef(PortableHomeFolderManager.java:292)
org.alfresco.repo.security.person.PortableHomeFolderManager.getHomeFolder(PortableHomeFolderManager.java:340)
org.alfresco.repo.security.person.UsernameHomeFolderProvider.getHomeFolder(UsernameHomeFolderProvider.java:63)
org.alfresco.repo.security.person.PortableHomeFolderManager.homeFolderCreateAndSetPermissions(PortableHomeFolderManager.java:215)
org.alfresco.repo.security.person.PortableHomeFolderManager.makeHomeFolder(PortableHomeFolderManager.java:203)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
02-23-2015 08:54 AM
05-30-2017 06:07 AM
Hi Axel, I do have the same problem. This happened when I upgraded an Alfresco 3.0.0 to the latest 5.2
My user homes is called: app:company_home/cm:user_homes/
I have tried for a day now to get the namespace switched from cm: to app: (which is what it is looking for) using the Javascript API but without success. I also tried to recreate the folder but can't get it to be app: ....
Do you have any tips on how I could solve this? Thanks a lot in advance.
05-30-2017 06:21 PM
Using the JavaScript API you will have a hard time changing the QName of the child association to app:user_homes as the API includes some "convenience features" that often default to using the cm: prefix.
You best bet might be to simply do a quick&dirty update to the DB directly. Stop Alfresco, make a DB backup, and update the corresponding entry in the alf_child_assoc table. You only have to update the qname_ns_id to the value for the "http://www.alfresco.org/model/application/1.0" namespace URL (you can determine the ID from the alf_namespace table).
07-02-2017 11:51 AM
In case anybody else runs into this issue here is what is needed to fix it:
- As Axel said: fix the corresponding alf_child_assoc entry and set the qname_ns_id to the "app" id, which can be found in alf_namespace. For me this was the following update: update alf_child_assoc set qname_localname = "user_homes", qname_ns_id = 7 where id = 21; You find the correct id by using the node browser in Alfresco and traversing the database.
- The next step is also important: Reindex everything. Rebuild your solr4 index or it won't find anything still.
- The last step for me was to rename the "User Homes" folder to something else and back to "User Homes". Without this step it would not work for me, I tried for hours and found this by accident.
So perform these 3 steps to fix that error if your User Home is not working correctly.
02-23-2015 10:19 AM
05-14-2018 09:52 AM
Hello Guys,
My Alfresco has the same problem. I tried everything i guys told to do but no success. Can you guys help me to solve this?
Thanks!
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.