cancel
Showing results for 
Search instead for 
Did you mean: 

Failed export operation

rgeimer
Champ in-the-making
Champ in-the-making
I tried running a complete repository export from the web client, and I get the following error:

Please correct the export errors below then click OK.

    * Failed to execute export: javax.transaction.RollbackException: Transaction didn't commit: Hibernate operation: could not load an entity: [org.alfresco.repo.domain.hibernate.VersionCountImpl#component[protocol,identifier]{protocol=workspace, identifier=lightWeightVersionStore}]; uncategorized SQLException for SQL [select versioncou0_.protocol as protocol7_0_, versioncou0_.identifier as identifier7_0_, versioncou0_.version_count as version3_7_0_ from version_count versioncou0_ where versioncou0_.protocol=? and versioncou0_.identifier=? for update]; SQL state [41000]; error code [1205]; Lock wait timeout exceeded; try restarting transaction; nested exception is java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction

Any help would be appreciated.
6 REPLIES 6

trying2alfresco
Champ in-the-making
Champ in-the-making
I am having the same problem.

kevinr
Star Contributor
Star Contributor
I have raised a JIRA item for this issue:
http://issues.alfresco.com/browse/AR-943

Thanks for reporting it.

Kevin

trying2alfresco
Champ in-the-making
Champ in-the-making
Hey Kevinr,

Thanks for raising the issue. Just wanted to let you know that I am not running 1.4. I am running 1.3 but still having the same problem.

kevinr
Star Contributor
Star Contributor

trying2alfresco
Champ in-the-making
Champ in-the-making
Thanks Kevinr. Does that mean the new builds won't have this problem. Also is there anything I can do to get it working on my current installation

kevinr
Star Contributor
Star Contributor
It should yes. I'm not sure how to get it working on 1.3, for customers we would be able to deliver a specific patched build for you e.g. 1.3.X - for the community version, then the recommended path would be to wait for the next build, and patch in the code for the fix from 1.4 into a 1.3 build.

Thanks,

Kevin