AnsweredAssumed Answered

Lab 3 stable fresh install forced to 'readOnly' mode

Question asked by ktsoi on Apr 17, 2009
Latest reply on Apr 22, 2009 by ktsoi
I am running into a similar problem.  All I've done is download alfresco-labs-war-3Stable.tar.gz, extracted and copied alfresco.war to my tomcat webapps directory as instructed in the install guide, ran the mysql setup script provided with the tar.gz, and started up tomcat.  I am getting the following error during startup:
Validation of patch 'patch.wcmFolders' failed. Patch is applicable to a newer schema than the schema of this build (1,002).
fixesToSchema: 9,999
targetSchema: 10,000.
If this patch should always be run once on every installation, please ensure that the 'fixesToSchema' value is set to '${version.schema}'.

When I login to alfresco, I am getting the following error:
org.springframework.dao.InvalidDataAccessApiUsageException: Write operations are not allowed in read-only mode (FlushMode.NEVER/MANUAL): Turn your Session into FlushMode.COMMIT/AUTO or remove 'readOnly' marker from transaction definition.

Why is alfresco in read-only mode, and how do I change alfresco to not 'read-only'?  Sorry for sounding frustrated, but how can something so simple (deploying the alfresco.war file) be causing so much problems?  I've seen a lot of post already with people running into the 'Write operations are not allowed in read-only mode' with no response.  Please help!  Thanks.

Outcomes