topic Re: admin user does not have sufficient priveleges after upgrade in Alfresco Archive

admin user does not have sufficient priveleges after upgrade

chapeaurouge — Tue, 07 Oct 2008 12:29:18 GMT

Hello all,Recently deployed the 3b war file on my server, which was previously running 2.9b.Everything works fine, except for one of my space, where even the admin user cannot delete anything. I get the Unable to delete Space due to system error: Access Denied. You do not have the appropriate permis

Re: admin user does not have sufficient priveleges after upgrade

mikeh — Tue, 07 Oct 2008 12:58:35 GMT

Could it be the same as this issue? http://forums.alfresco.com/en/viewtopic.php?f=8&t=14261

Mike

Re: admin user does not have sufficient priveleges after upgrade

chapeaurouge — Tue, 07 Oct 2008 13:17:52 GMT

I will try to put the old xml file, but I see the folders and all, and get no strack trace anywhere. I just cannot delete the folders/files, nor use the API to upload in that space, etc…

I'll report back when I put the older xml file in place. Cheers.

fred

Re: admin user does not have sufficient priveleges after upgrade

chapeaurouge — Tue, 07 Oct 2008 13:19:26 GMT

If this of some help, here is the trace i get from the webservices api, when i try to upload a document:

java.lang.RuntimeException: Error writing content to repository server
   at org.alfresco.webservice.util.ContentUtils.putContent(ContentUtils.java:276)
   at org.alfresco.webservice.util.ContentUtils.putContent(ContentUtils.java:148)
   at lu.invik.bi.print2file.Uploader.create(Uploader.java:114)
   at lu.invik.bi.print2file.ArcParser.main(ArcParser.java:53)
Caused by: java.lang.RuntimeException: Content could not be uploaded because user does not have sufficient priveledges.
   at org.alfresco.webservice.util.ContentUtils.putContent(ContentUtils.java:244)
   … 3 more‍‍‍‍‍‍‍‍

Re: admin user does not have sufficient priveleges after upgrade

chapeaurouge — Tue, 07 Oct 2008 13:24:34 GMT

Well, apparently, no.

I actually had forgotten to copy my custom extensions back in the extension folder. So the delete issue is gone, and the update issue should be as well.

My bad. Sorry about that. However, I guess the error message could have been a bit more explicit.