topic Re: Manage System User Errors in Alfresco Archive

Manage System User Errors

dnguyen — Mon, 11 Feb 2013 21:45:26 GMT

Hello,Whenever I select 'Manage System Users —> Show All' I get these errors, Can someone please show me how to fix it ? I am using version 3.2r. I really appreciate your help!javax.faces.FacesException: javax.faces.FacesException: Could not retrieve value of component with path : {Component-Pa

Re: Manage System User Errors

abarisone — Tue, 12 Feb 2013 09:12:22 GMT

Hi,
I would suggest you, if possible, to migrate to a newer Alfresco version like 4.2.c
At least migrate to 3.2r2 which is more stable than 3.2r

Regards,
Andrea

Re: Manage System User Errors

dnguyen — Tue, 12 Feb 2013 12:59:00 GMT

Hello Andrea,

I did migrate to 3.2r and still have problem, I haven't migrated to 4.2c yet. But what would cause the problem though ?

Re: Manage System User Errors

abarisone — Tue, 12 Feb 2013 13:16:50 GMT

Hi,
really I don't know, even because I have too few elements to give an answer.
By the way at the end of your stack you got <cite>caused by: java.lang.IllegalStateException: Non-unique path: found : /app:company_home/app:user_homes 0</cite> which is quite serious.
It seems something related to some user's home got corrupted…

Regards,
Andrea

Re: Manage System User Errors

dnguyen — Tue, 12 Feb 2013 14:04:24 GMT

Yeah the problem started after I deleted a user. For whatever reason is, after I deleted a user it didn't delete the user home. Is there a way that we can delete the user home manually ?

Thanks

Re: Manage System User Errors

abarisone — Tue, 12 Feb 2013 14:41:40 GMT

Hi,
this post may be useful http://forums.alfresco.com/forum/installation-upgrades-configuration-integration/configuration/manually-remove-corrupt-user-not especially following the JIRA link provided.
It seems that it was an issue fixed on version 3.3, so you can another step migrating to 3.3 (I would suggest 3.3.g)

Regards,
Andrea

Re: Manage System User Errors

dnguyen — Tue, 12 Feb 2013 15:27:01 GMT

Yeah, I just migrated to 3.3g and still get the same error. At this point I am not sure if migrating to 4.2 would fix the issue.