topic Re: error in upgrading from 1.2.1 to 1.3.0dev in Alfresco Archive

error in upgrading from 1.2.1 to 1.3.0dev

cts_sergiu_dunc — Mon, 19 Jun 2006 11:19:35 GMT

Hello,I've read the upgrade document.I did the following steps: - stop alfresco 1.2.1 - unpack alfresco-tomcat-1.3.0dev.tar.gz in a clean /opt/alfresco - copy ./alf_data from 1.2.1 to the fresh /opt/alfresco - run the migration schema script# mysql alfresco < AlfrescoSchemaMigrate-1.3-mysql.sqlER

Re: error in upgrading from 1.2.1 to 1.3.0dev

cts_sergiu_dunc — Tue, 20 Jun 2006 09:14:10 GMT

I modified the migration script since MySQL-Max-4.1.18 treats the table names differrent with lower and upper cases. It had another error now:

ERROR 1062 (23000) at line 626: Duplicate entry '0-2-GROUP_EVERYONE' for key 2

After starting the upgraded 1.3.0dev the space permissions are not there.. All previous spaces have empty permissions, none from migrated 1.2.1 is there.

Could you give me some help here please ?

Thank you,
Sergiu

Re: error in upgrading from 1.2.1 to 1.3.0dev

ajshaw — Wed, 21 Jun 2006 09:32:25 GMT

I also get the same error, except mine says 'Duplicate entry '0-1-GROUP_EVERYONE' for key 2'.

I cannot start alfresco however. I also get lots of errors about patches not being installed. I am running 1.2.0 (on windows), how do i upgrade from 1.2.0 to 1.2.1 as recommended in the instructions?.

Re: error in upgrading from 1.2.1 to 1.3.0dev

ero — Sat, 24 Jun 2006 19:07:51 GMT

Hi,

Check if your Mysql has been patched with following:

ALTER TABLE applied_patch MODIFY id varchar(64) not null;

Re: error in upgrading from 1.2.1 to 1.3.0dev

cludt — Wed, 12 Jul 2006 11:06:01 GMT

Why is the temporary table t_applied_patch created? It is never filled with any data.

And why isn't the needed patch

ALTER TABLE applied_patch MODIFY id varchar(64) not null;‍

included in the mysql update script?

And why are the temporary tables not deleted?

Re: error in upgrading from 1.2.1 to 1.3.0dev

cludt — Wed, 12 Jul 2006 11:13:07 GMT

I still had some problems executing the last insert statement

insert into access_control_entry
  (
    id, acl_id, permission_id, authority_id, allowed
  )
  select
    id, acl_id, permission_id, authority_id, allowed
  from
    T_access_control_entry;‍‍‍‍‍‍‍‍

because the index over (acl_id,permission_id,authority_id) would not be unique.

How could this happen? Does this mean, that the former data has already been invalid or should this be possible to happen but has been overlooked by the developers?

Anyway, how can this be solved?

Re: error in upgrading from 1.2.1 to 1.3.0dev

heiko_robert — Thu, 13 Jul 2006 18:23:04 GMT

I've similar problems. I fixed all upper case and quote issues in the upgrade script and it run without any error. After deploying the new war file and setting the correct hybernate/repository-settings the server fails to startup. The first important error is:

Jul 11, 2006 8:58:52 PM net.sf.joott.uno.UnoConnection connect
INFO: connecting using "socket,host=localhost,port=8100,tcpNoDelay=1"…
Jul 11, 2006 8:58:52 PM net.sf.joott.uno.UnoConnection connect
INFO: connected
20:58:56,320 INFO [admin.patch.PatchExecuter] Checking for patches to apply …
20:59:01,299 ERROR [admin.patch.PatchServiceImpl] net.sf.acegisecurity.AuthenticationCredentialsNotFoundException: A valid SecureContext was not provided in the RequestContext
        at net.sf.acegisecurity.intercept.AbstractSecurityInterceptor.credentialsNotFound(AbstractSecurityInterceptor.java:477)
        at net.sf.acegisecurity.intercept.AbstractSecurityInterceptor.beforeInvocation(AbstractSecurityInterceptor.java:355)
        at net.sf.acegisecurity.intercept.method.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:77)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
        at org.alfresco.repo.security.permissions.impl.ExceptionTranslatorMethodInterceptor.invoke(ExceptionTranslatorMethodInterceptor.java:41)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
        at $Proxy16.getProperties(Unknown Source)

seems, that the server is unable to login? missing methods? wrong credentials?
environment: winXP, jdk 1.5.0_07, MySQL 5.0.22, alfresco-enterprise-tomcat-1.3.0

Re: error in upgrading from 1.2.1 to 1.3.0dev

andy — Fri, 14 Jul 2006 10:24:14 GMT

Hi

Please post the full output from the patch process.

Regards

Andy

Re: error in upgrading from 1.2.1 to 1.3.0dev

cludt — Wed, 19 Jul 2006 09:48:16 GMT

I still had some problems executing the last insert statement
insert into access_control_entry
  (
    id, acl_id, permission_id, authority_id, allowed
  )
  select
    id, acl_id, permission_id, authority_id, allowed
  from
    T_access_control_entry;‍‍‍‍‍‍‍‍
because the index over (acl_id,permission_id,authority_id) would not be unique.

[…]

Sorry, this is not true. The last insert statement is not executed because I have null values for the acl_id column in the t_access_control_entry table. Is this related to invalid former data or are there more reasons why this could happen?

How can I fix this? I guess, replacing the null values by a random acl_id number won't work, as I may violate some other constraints.

Re: error in upgrading from 1.2.1 to 1.3.0dev

cludt — Thu, 20 Jul 2006 15:42:30 GMT

I've similar problems. I fixed all upper case and quote issues in the upgrade script and it run without any error. After deploying the new war file and setting the correct hybernate/repository-settings the server fails to startup. The first important error is:

Jul 11, 2006 8:58:52 PM net.sf.joott.uno.UnoConnection connect
INFO: connecting using "socket,host=localhost,port=8100,tcpNoDelay=1"…
Jul 11, 2006 8:58:52 PM net.sf.joott.uno.UnoConnection connect
INFO: connected
20:58:56,320 INFO [admin.patch.PatchExecuter] Checking for patches to apply …
20:59:01,299 ERROR [admin.patch.PatchServiceImpl] net.sf.acegisecurity.AuthenticationCredentialsNotFoundException: A valid SecureContext was not provided in the RequestContext
        at net.sf.acegisecurity.intercept.AbstractSecurityInterceptor.credentialsNotFound(AbstractSecurityInterceptor.java:477)
        at net.sf.acegisecurity.intercept.AbstractSecurityInterceptor.beforeInvocation(AbstractSecurityInterceptor.java:355)
        at net.sf.acegisecurity.intercept.method.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:77)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
        at org.alfresco.repo.security.permissions.impl.ExceptionTranslatorMethodInterceptor.invoke(ExceptionTranslatorMethodInterceptor.java:41)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
        at $Proxy16.getProperties(Unknown Source)

seems, that the server is unable to login? missing methods? wrong credentials?
environment: winXP, jdk 1.5.0_07, MySQL 5.0.22, alfresco-enterprise-tomcat-1.3.0

This error seems to be due to rules firing during patching. Switch off the rules by using the following file (to be placed in extension directory)

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>
 
<beans>
   <bean id="inbound" class="org.alfresco.repo.rule.RuleTypeImpl" parent="rule-type-base">
      <constructor-arg>
         <list>
         </list>
      </constructor-arg>
   </bean>

   <bean id="update" class="org.alfresco.repo.rule.RuleTypeImpl" parent="rule-type-base">
      <constructor-arg>
         <list>
         </list>
      </constructor-arg>
   </bean>
   
   <bean id="outbound" class="org.alfresco.repo.rule.RuleTypeImpl" parent="rule-type-base">
      <constructor-arg>
         <list>
         </list>
      </constructor-arg>
   </bean>
</beans>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: error in upgrading from 1.2.1 to 1.3.0dev

trying2alfresco — Thu, 03 Aug 2006 20:38:38 GMT

Hey Cludt,

I am having the same problem as you. Have you figured out how to get around it? Sure wouldn't mind some help.

Thanks.

Re: error in upgrading from 1.2.1 to 1.3.0dev

cludt — Fri, 04 Aug 2006 08:14:42 GMT

If you are talking about the mysql script, I have been given a new one from the alfresco support (my company is a registered partner). I am not sure if I am allowed to provide others with this script. I will check.

Re: error in upgrading from 1.2.1 to 1.3.0dev

trying2alfresco — Fri, 04 Aug 2006 14:19:39 GMT

cool. thanks.

Re: error in upgrading from 1.2.1 to 1.3.0dev

lmouillart — Fri, 11 Aug 2006 12:20:16 GMT

Hi trying2alfresco, i have the same error as you : 'Duplicate entry '0-1-GROUP_EVERYONE' for key 2'. Have you allready resolve this issue ?

Regards,
Laurent

Re: error in upgrading from 1.2.1 to 1.3.0dev

cludt — Fri, 11 Aug 2006 12:29:44 GMT

Hi Laurent,

this will also be solved by the new mysql script. I am still awaiting a post-reply from the support.

Chris

Re: error in upgrading from 1.2.1 to 1.3.0dev

derek — Wed, 16 Aug 2006 09:34:32 GMT

The scripts are kept up to date on HEAD.

Regards

Re: error in upgrading from 1.2.1 to 1.3.0dev

legba — Mon, 10 Dec 2007 23:56:28 GMT

Hi derek,
apparently the scripts are not anymore on HEAD: as far as I see the old revision are not accessible from the public svn (am I missing something?).

I tried the ones inside the old releases but the duplicate key problem is still there.

I also tried the script from this post:
http://forums.alfresco.com/viewtopic.php?t=2892
but to no avail.

Is there a script that correclty patches the database?

I am trying to upgrade from version 1.2 to version 2.1; following the path 1.2 -> 1.2.1 -> 1.3 -> 1.4 -> 2.0 -> 2.1 ( http://forums.alfresco.com/viewtopic.php?t=6199 )

Thanks in advance for your assistance.

Fabio