nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

VersionServiceException after upgrade to Alfresco 3 Lab

gianlucam

Hi

I've upgraded to Alfresco 3 Lab Stable from Alfresco 2.1. My documents are versionable by aspect.
When I try to check in a document, the operation failed with error:

"The current implementation of the version service does not support the creation of branches"

If I remove aspect, the operation success.
After I've removed tha aspect, if I add the versionable aspect again, the operation success.
It seems like versionable aspect inherited from version 2.1 are wrong.

is There a solution that is not remove all the versionable aspect and add them again ?

Thanks

Find more posts tagged with

Comments

jbonjean

Hi,
I have exactly the same problem, did you find a solution ?
Thanks,

Julien

jbonjean

Ok, after debugging Alfresco, it seems that I need to use deprecated version store.
I suppose that something gone wrong during migration or maybe it is a bug in Alfresco 3.0 wich make it not backward compatible with 2.1. The fact is that version history is not build the same way in both versions; 3.0 assumes that versions hierarchy depends on versionNumber whereas it does not seems to be the case in previous versionstore.

Solution is to add "version.store.onlyUseDeprecatedV1=true" to my custom-repository.properties
But I don't know what could be effects of this option on other features.

Julien

jbonjean

I found the wiki page : http://wiki.alfresco.com/wiki/3.0_Version_Store
Problem could be linked with Frozen node associations (ver:versionedAssoc) ?

andrepra

I got the same problem. (2.1 -> 3.0 Stable). File repository.properties contains this warning

version.store.deprecated.lightWeightVersionStore=workspace://lightWeightVersionStore
version.store.version2Store=workspace://version2Store
# WARNING: For non-production testing only !!! Do not change (to avoid version store issues, including possible mismatch). Should be false since lightWeightVersionStore is deprecated.
version.store.onlyUseDeprecatedV1=false
‍‍‍‍‍‍

I don't think that is the right thing to do. Anybody found others solutions?

Andrea

jbonjean

Yes, I saw this warning, that's why I didn't set this property on production config yet. But users cannot update theirs documents so I will really need a solution soon. For me, it's a migration process bug.

Julien

andrepra

I just try on another document and the version works. In my previous post I tried to apply a simple script that increase the version.

document.createVersion('', true); 
‍‍‍

also changing the code in

var newDoc = document.checkout();
newDoc.checkin("Release", true);
‍‍‍‍

i got the same error :"The current implementation of the version service does not support the creation of branches".

After that i tried to use checkin and checkout from the UI on that file and i got other errors.
Trying on another file everything works fine. I don't know why. Maybe the first file was corrupted. Both files were created after the migration to 3.0 so the migration process to the new version model was not applied to this files.
Now i'm going to perform other test and if i have other informations i'll post again.

Andrea

andrepra

Ok, after many test i found that the API document.createVersion(history, major) create a lot of problems. Using that i get something corrupted and update of the document that happens after this call get a null pointer exception.
I changed this call simulating a checkin/checkout (previous code) and everything (seems) works fine.

Andrea
-

jbonjean

I'm not sure it's the same problem. I'm not using script, just using Alfresco update functionality. And document created in 3.0 are working well, only document migrated from 2.1 (and already versioned) have this bug.

alarocca

This issue seems to be already resolved:

https://issues.alfresco.com/jira/browse/ETHREEOH-1540

Should be great if any good soul at Alfresco would give us at least a tip.

Greetings

alarocca

Solved. Thanks to Jan Volka who helped me to find the patch within the HEAD repository.

First of all, you have to get and compile the patch:

http://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/HEAD/root/projects/repository/source/java/org/alfresco/repo/admin/patch/impl/MigrateVersionStoreUpdateCounterPatch.java

Then go to ..\tomcat\webapps\alfresco\WEB-INF\classes

Copy the .class file into \org\alfresco\repo\admin\patch\impl (create the missing folder)

Edit \alfresco\patch\patch-services-context.xml and append to the bottom (before </beans>) the following:

    <bean id="patch.migrateVersionStoreUpdateCounter" class="org.alfresco.repo.admin.patch.impl.MigrateVersionStoreUpdateCounterPatch" parent="basePatch" >
        <property name="id"><value>patch.migrateVersionStoreUpdateCounter</value></property>
        <property name="description"><value>patch.migrateVersionStoreUpdateCounter.description</value></property>
        <property name="fixesFromSchema"><value>0</value></property>
        <property name="fixesToSchema"><value>129</value></property>
        <property name="targetSchema"><value>130</value></property>
        <!– helper beans/properties –>
        <property name="versionCounterService">
            <ref bean="versionCounterService" />
        </property>
    </bean>
‍‍‍‍‍‍‍‍‍‍‍‍

Finally edit \alfresco\messages\patch-service.properties and append to the bottom the following:

patch.migrateVersionStoreUpdateCounter.description=Update internal version2Store counter (if needed).
patch.migrateVersionStoreUpdateCounter.result=Update internal version2Store counter (if needed): {0}
‍‍‍

Now you can migrate your Alfresco with confidence. Enjoy it.

Best regards,
Alessandro

This issue seems to be already resolved:

https://issues.alfresco.com/jira/browse/ETHREEOH-1540

Should be great if any good soul at Alfresco would give us at least a tip.

Greetings

varsenault

But, will this be released in an official Labs version soon?

sureshj

I had upgraded from Alfresco 2.1 Community Edition to Alfresco Labs3 Stable with random checks earlier in April. Now I am experiencing similar problem here in our production repository with the error:

"Unable to check in Content Node due to system error:The current implementation of the version service does not support the creation of branches"

If I update the above mentioned patch in the production server now, will it solve the problem? Also, can anybody help me with the class file required to fix this?

Thanks in advance for the help!!!

efvrvo

This error occurred with me using 3.4d when I tried to update a document version using a javascript inside an advanced workflow.