topic Re: Failed to copy authorities during upgrade to 3.2 in Alfresco Archive

Failed to copy authorities during upgrade to 3.2

tim-erwin — Mon, 28 Sep 2009 09:40:35 GMT

Hello,I'm trying to upgrade from 2.9 to 3.2 (2.9 > 3.0 is not an option due to reasons mentioned here) but fail with the following error:11:34:04,059 Userystem INFO [admin.patch.PatchExecuter] Applying patch 'patch.authorityMigration' (Copies any old authorities from the user store to the

Re: Failed to copy authorities during upgrade to 3.2

dbachem — Mon, 09 Nov 2009 11:37:13 GMT

Hi Tim,

last days i tried a migration from Alfresco 3.0 to 3.2r. Unfortunally a ran into the same problem and don't understand in detail what happens here.
Could you solve the problem in between?

Re: Failed to copy authorities during upgrade to 3.2

dward — Mon, 09 Nov 2009 12:11:48 GMT

It looks like some of your 3.0 groups have 'dangling' references to a non-existent user called "admin". The new 3.2 schema will not allow such dangling references as all group memeberships are now recorded using node child associations.

Anyway, to work around the problem, before upgrading 3.0, please create a user called "admin". You can delete him after the upgrade.

Please log this issue in JIRA so that we can improve the robustness of the upgrade.

Thanks.

Re: Failed to copy authorities during upgrade to 3.2

dbachem — Mon, 09 Nov 2009 19:03:02 GMT

I hope i have a solution for you, i commented the following text to https://issues.alfresco.com/jira/browse/ALFCOM-3442, which is a ticket referencing to this problem.

In our case, the reason for the failure was, that we have a subtype of "cmerson" in our model, the instances of this persons are placed in various workspace folders. Those persons can't be migrated due to implementation of PersonDaoImpl.getPersonOrNull(..). There is a callback containing a SQL statement which uses the concret type (without subtypes of "cmerson"!):


        HibernateCallback callback = new HibernateCallback()
        {
            public Object doInHibernate(Session session)
            {
                SQLQuery query = (SQLQuery) session.getNamedQuery(QUERY_PERSON_GET_PERSON_IGNORE_CASE);
                query.setParameter("qnamePropId", qNamePropId);
                query.setParameter("qnameTypeId", qNameTypeId);
                query.setParameter("userNameLowerCase", searchUserName.toLowerCase());      // Lowercase: ETHREEOH-1431
                query.setParameter("False", Boolean.FALSE);
                query.setParameter("storeProtocol", personStoreRef.getProtocol());
                query.setParameter("storeIdentifier", personStoreRef.getIdentifier());
                return query.list();
            }
        };
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

AFAIK this is the reason for the migration failure.

I could solve the problem deleting these users before migration. Hope this helps!

Kind regards, Dirk

Re: Failed to copy authorities during upgrade to 3.2

dward — Mon, 09 Nov 2009 19:19:38 GMT

This is fixed in HEAD.

Re: Failed to copy authorities during upgrade to 3.2

tim-erwin — Wed, 11 Nov 2009 09:24:54 GMT

Hi Dirk,

thanks for posting your solution. We don't have any special content types, however. Just a plain Alfresco with a lot of data in there. So, unfortunately, this doesn't help here. I'll try migration again as soon as the next update of Alfresco is out there.

Thanks anyways,
Tim

Re: Failed to copy authorities during upgrade to 3.2

dbachem — Thu, 12 Nov 2009 10:43:36 GMT

Hello Tim,

just some questions:

did you have a user named "admin" in your repository before migration? if not, try what dward recommended and create the user before you start to migrate.

do you use LDAP or any other authentication subsystem?

if you have the "admin" user in your system, maybe it is not what the PersonDaoImpl expected. It could be located on a different place for instance. so, did you create persons programmatically in your application?

To understand what happens, you should know, that the group objects hold a simple array of user-names, which are belonging to the group. So it seams that there is at least one group referencing to an "admin" user, which doesn't exist. You can easily check this if you use the node-browser and inspect all existing groups.

And finally: if you are going to migrate to community 3.2r (i think you used 3.2 in your tests), possibly you will get another exception: "There is no statement named select.AVMNodeEntitiesCountWhereNewInStore in this SqlMap". You can fix this in only 30 seconds and save a lot of time searching if you follow the patch i posted in the comments section of this jira ticket: https://issues.alfresco.com/jira/browse/ALFCOM-3611?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel :wink:

Dirk

—
Alfresco Community 3.2r: http://wiki.alfresco.com/wiki/Alfresco_Community_Edition_3.2r

Re: Failed to copy authorities during upgrade to 3.2

tim-erwin — Tue, 17 Nov 2009 10:23:57 GMT

Hi Dirk,

thanks a lot for taking time to help me. To answer your questions:

we always have and had the admin user that is there by default, we never changed it (except password)

we don't have any special authentication system

in general, we create users programmatically, however, for testing I used a "naked" system, only the admin user

Regards,
Tim

Re: Failed to copy authorities during upgrade to 3.2

mudassirshahabu — Thu, 11 Feb 2010 01:54:25 GMT

Tim,

Did you get solution to this problem. If yes, can you share your experience.

Let me share my experience. I ran to this problem and did not performed any migration. I am using 3.1.1 SP 1 and I think problem is with database rather than codebase.

I have same code base working fine with one machine DB. One I switch over to another db problem occurs ….

Thanks.

Re: Failed to copy authorities during upgrade to 3.2

tim-erwin — Thu, 11 Feb 2010 07:53:46 GMT

mudassirshahabuddin,

so, sorry, no solution so far. We're focusing on other things right now avoiding to even think about that issue…

Good luck
Tim