topic Alfresco broken after upgrade to 4.2.f in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311956#M265086 <HTML><HEAD></HEAD><BODY><SPAN>Hello all,</SPAN><BR /><SPAN>could anyone assist me with an upgrade from alfresco community 4.2.e to 4.2.f on ubuntu linux 12.04?</SPAN><BR /><SPAN>After successfully completing the new installation and validating it, I try to point alfresco to the old root data directory. I get the following error after a restart:</SPAN><BR /><BR /><SPAN>00:29:56,214 INFO&nbsp; [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco root data directory ('dir.root') is: /opt/alfresco-4.2.f/alf_data_repo</SPAN><BR /><SPAN>00:29:56,224 ERROR [org.alfresco.repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: System content not found in content store.</SPAN><BR /><SPAN>00:29:56,224 ERROR [org.alfresco.repo.admin.ConfigurationChecker] Ensure that the 'dir.root' property is pointing to the correct data location.</SPAN><BR /><BR /><SPAN>If i try to use the new (empty) repository, alfresco starts correctly.</SPAN><BR /><SPAN>here is my tomcat/shared/classes/alfresco-global.properties :</SPAN><BR /><BR /><SPAN>###############################</SPAN><BR /><SPAN>## Common Alfresco Properties #</SPAN><BR /><SPAN>###############################</SPAN><BR /><BR /><SPAN>dir.root=/opt/alfresco-4.2.f/alf_data_repo</SPAN><BR /><BR /><SPAN>alfresco.context=alfresco</SPAN><BR /><SPAN>alfresco.host=&lt;snip&gt;</SPAN><BR /><SPAN>alfresco.port=8080</SPAN><BR /><SPAN>alfresco.protocol=http</SPAN><BR /><BR /><SPAN>share.context=share</SPAN><BR /><SPAN>share.host=&lt;snip&gt;</SPAN><BR /><SPAN>share.port=8080</SPAN><BR /><SPAN>share.protocol=http</SPAN><BR /><BR /><SPAN>### database connection properties ###</SPAN><BR /><SPAN>db.driver=org.postgresql.Driver</SPAN><BR /><SPAN>db.username=alfresco</SPAN><BR /><SPAN>db.password=&lt;snip&gt;</SPAN><BR /><SPAN>db.name=alfresco</SPAN><BR /><SPAN>db.url=jdbc<img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" />ostgresql://localhost:5432/${db.name}</SPAN><BR /><BR /><SPAN>### FTP Server Configuration ###</SPAN><BR /><SPAN>ftp.enabled=true</SPAN><BR /><SPAN>ftp.port=21</SPAN><BR /><BR /><SPAN>### RMI service ports ###</SPAN><BR /><SPAN>alfresco.rmi.services.port=50500</SPAN><BR /><SPAN>avm.rmi.service.port=0</SPAN><BR /><SPAN>avmsync.rmi.service.port=0</SPAN><BR /><SPAN>attribute.rmi.service.port=0</SPAN><BR /><SPAN>authentication.rmi.service.port=0</SPAN><BR /><SPAN>repo.rmi.service.port=0</SPAN><BR /><SPAN>action.rmi.service.port=0</SPAN><BR /><SPAN>deployment.rmi.service.port=0</SPAN><BR /><BR /><SPAN>### External executable locations ###</SPAN><BR /><SPAN>ooo.exe=/opt/alfresco-4.2.f/libreoffice/program/soffice.bin</SPAN><BR /><SPAN>ooo.enabled=true</SPAN><BR /><SPAN>ooo.port=8100</SPAN><BR /><SPAN>img.root=/opt/alfresco-4.2.f/common</SPAN><BR /><SPAN>img.dyn=${img.root}/lib</SPAN><BR /><SPAN>img.exe=${img.root}/bin/convert</SPAN><BR /><SPAN>swf.exe=/opt/alfresco-4.2.f/common/bin/pdf2swf</SPAN><BR /><SPAN>swf.languagedir=/opt/alfresco-4.2.f/common/japanese</SPAN><BR /><BR /><SPAN>jodconverter.enabled=false</SPAN><BR /><SPAN>jodconverter.officeHome=/opt/alfresco-4.2.f/libreoffice</SPAN><BR /><SPAN>jodconverter.portNumbers=8100</SPAN><BR /><BR /><SPAN>### Initial admin password ###</SPAN><BR /><SPAN>alfresco_user_store.adminpassword=&lt;snip&gt;</SPAN><BR /><BR /><SPAN>### E-mail site invitation setting ###</SPAN><BR /><SPAN>notification.email.siteinvite=false</SPAN><BR /><BR /><SPAN>### License location ###</SPAN><BR /><SPAN>dir.license.external=/opt/alfresco-4.2.f</SPAN><BR /><BR /><SPAN>### Solr indexing ###</SPAN><BR /><SPAN>#index.subsystem.name=solr</SPAN><BR /><SPAN>#dir.keystore=${dir.root}/keystore</SPAN><BR /><SPAN>#solr.port.ssl=8443</SPAN><BR /><BR /><SPAN>### Solr indexing ###</SPAN><BR /><SPAN>#index.subsystem.name=solr</SPAN><BR /><SPAN>#dir.keystore=${dir.root}/keystore</SPAN><BR /><SPAN>#solr.port.ssl=8443</SPAN><BR /><SPAN>index.subsystem.name=lucene</SPAN><BR /><SPAN>index.recovery.mode=AUTO</SPAN><BR /><SPAN>dir.keystore=${dir.root}/keystore</SPAN><BR /><SPAN>#solr.port.ssl=8443</SPAN><BR /><SPAN>#dir.keystore=${dir.root}/keystore</SPAN><BR /><SPAN>#solr.port.ssl=8443</SPAN><BR /><BR /><BR /><SPAN>### BPM Engine ###</SPAN><BR /><SPAN>system.workflow.engine.jbpm.enabled=false</SPAN><BR /><SPAN>authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap1:ldap</SPAN><BR /><BR /><SPAN>nfs.enabled=false</SPAN><BR /><BR /><SPAN># This flag enables use of this LDAP subsystem for authentication. It may be</SPAN><BR /><SPAN># that this subsytem should only be used for synchronization, in which case</SPAN><BR /><SPAN># this flag should be set to false.</SPAN><BR /><SPAN>ldap.authentication.active=true</SPAN><BR /><BR /><SPAN>#</SPAN><BR /><SPAN># This properties file brings together the common options for LDAP authentication rather than editing the bean definitions</SPAN><BR /><SPAN>#</SPAN><BR /><SPAN>ldap.authentication.allowGuestLogin=true</SPAN><BR /><SPAN># How to map the user id entered by the user to that passed through to LDAP</SPAN><BR /><SPAN># - simple </SPAN><BR /><SPAN>#&nbsp;&nbsp;&nbsp; - this must be a DN and would be something like</SPAN><BR /><SPAN>#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; uid=%s,ou=People,dc=company,dc=com</SPAN><BR /><SPAN># - digest</SPAN><BR /><SPAN>#&nbsp;&nbsp;&nbsp; - usually pass through what is entered</SPAN><BR /><SPAN>#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; %s</SPAN><BR /><SPAN># If not set, an LDAP query involving ldap.synchronization.personQuery and ldap.synchronization.userIdAttributeName will </SPAN><BR /><SPAN># be performed to resolve the DN dynamically. This allows directories to be structured and doesn't require the user ID to</SPAN><BR /><SPAN># appear in the DN.</SPAN><BR /><SPAN>ldap.authentication.userNameFormat=</SPAN><BR /><BR /><SPAN># The LDAP context factory to use</SPAN><BR /><SPAN>ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory</SPAN><BR /><BR /><SPAN># The URL to connect to the LDAP server </SPAN><BR /><SPAN>ldap.authentication.java.naming.provider.url=ldap://&lt;snip&gt;:389</SPAN><BR /><BR /><SPAN># The authentication mechanism to use for password validation</SPAN><BR /><SPAN>ldap.authentication.java.naming.security.authentication=simple</SPAN><BR /><BR /><SPAN># Escape commas entered by the user at bind time</SPAN><BR /><SPAN># Useful when using simple authentication and the CN is part of the DN and contains commas</SPAN><BR /><SPAN>ldap.authentication.escapeCommasInBind=false</SPAN><BR /><BR /><SPAN># Escape commas entered by the user when setting the authenticated user</SPAN><BR /><SPAN># Useful when using simple authentication and the CN is part of the DN and contains commas, and the escaped \, is </SPAN><BR /><SPAN># pulled in as part of an LDAP sync</SPAN><BR /><SPAN># If this option is set to true it will break the default home folder provider as space names can not contain \</SPAN><BR /><SPAN>ldap.authentication.escapeCommasInUid=false</SPAN><BR /><BR /><SPAN># Comma separated list of user names who should be considered administrators by default</SPAN><BR /><SPAN>ldap.authentication.defaultAdministratorUserNames=</SPAN><BR /><BR /><SPAN># This flag enables use of this LDAP subsystem for user and group</SPAN><BR /><SPAN># synchronization. It may be that this subsytem should only be used for </SPAN><BR /><SPAN># authentication, in which case this flag should be set to false.</SPAN><BR /><SPAN>ldap.synchronization.active=true</SPAN><BR /><BR /><SPAN># The authentication mechanism to use for synchronization</SPAN><BR /><SPAN>ldap.synchronization.java.naming.security.authentication=simple</SPAN><BR /><BR /><SPAN># The default principal to use (only used for LDAP sync)</SPAN><BR /><SPAN>ldap.synchronization.java.naming.security.principal=&lt;snip&gt;</SPAN><BR /><BR /><SPAN># The password for the default principal (only used for LDAP sync)</SPAN><BR /><SPAN>ldap.synchronization.java.naming.security.credentials=&lt;snip&gt;</SPAN><BR /><BR /><SPAN># If positive, this property indicates that RFC 2696 paged results should be</SPAN><BR /><SPAN># used to split query results into batches of the specified size. This</SPAN><BR /><SPAN># overcomes any size limits imposed by the LDAP server.</SPAN><BR /><SPAN>ldap.synchronization.queryBatchSize=0</SPAN><BR /><BR /><SPAN># If positive, this property indicates that range retrieval should be used to fetch</SPAN><BR /><SPAN># multi-valued attributes (such as member) in batches of the specified size.</SPAN><BR /><SPAN># Overcomes any size limits imposed by Active Directory.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><BR /><SPAN>ldap.synchronization.attributeBatchSize=0</SPAN><BR /><BR /><SPAN># The query to select all objects that represent the groups to import.</SPAN><BR /><SPAN>ldap.synchronization.groupQuery=(&amp;(objectclass=posixGroup)(!(cn~=Mailboxes)))</SPAN><BR /><BR /><SPAN># The query to select objects that represent the groups to import that have changed since a certain time.</SPAN><BR /><SPAN>ldap.synchronization.groupDifferentialQuery=(&amp;(objectclass\=posixGroup)(!(modifyTimestamp&lt;\={0}))(!(cn~=Mailboxes)))</SPAN><BR /><BR /><SPAN># The query to select all objects that represent the users to import.</SPAN><BR /><SPAN>ldap.synchronization.personQuery=(objectclass\=inetOrgPerson)</SPAN><BR /><BR /><SPAN># The query to select objects that represent the users to import that have changed since a certain time.</SPAN><BR /><SPAN>ldap.synchronization.personDifferentialQuery=(&amp;(objectclass\=inetOrgPerson)(!(modifyTimestamp&lt;\={0})))</SPAN><BR /><BR /><SPAN># The group search base restricts the LDAP group query to a sub section of tree on the LDAP server.</SPAN><BR /><SPAN>ldap.synchronization.groupSearchBase=&lt;snip&gt;</SPAN><BR /><BR /><SPAN># The user search base restricts the LDAP user query to a sub section of tree on the LDAP server.</SPAN><BR /><SPAN>ldap.synchronization.userSearchBase=&lt;snip&gt;</SPAN><BR /><BR /><SPAN># The name of the operational attribute recording the last update time for a group or user.</SPAN><BR /><SPAN>ldap.synchronization.modifyTimestampAttributeName=modifyTimestamp</SPAN><BR /><BR /><SPAN># The timestamp format. Unfortunately, this varies between directory servers.</SPAN><BR /><SPAN>ldap.synchronization.timestampFormat=yyyyMMddHHmmss'Z'</SPAN><BR /><BR /><SPAN># The attribute name on people objects found in LDAP to use as the uid in Alfresco</SPAN><BR /><SPAN>ldap.synchronization.userIdAttributeName=uid</SPAN><BR /><BR /><SPAN># The attribute on person objects in LDAP to map to the first name property in Alfresco</SPAN><BR /><SPAN>ldap.synchronization.userFirstNameAttributeName=givenName</SPAN><BR /><BR /><SPAN># The attribute on person objects in LDAP to map to the last name property in Alfresco</SPAN><BR /><SPAN>ldap.synchronization.userLastNameAttributeName=sn</SPAN><BR /><BR /><SPAN># The attribute on person objects in LDAP to map to the email property in Alfresco</SPAN><BR /><SPAN>ldap.synchronization.userEmailAttributeName=mail</SPAN><BR /><BR /><SPAN># The attribute on person objects in LDAP to map to the organizational id&nbsp; property in Alfresco</SPAN><BR /><SPAN>ldap.synchronization.userOrganizationalIdAttributeName=o</SPAN><BR /><BR /><SPAN># The default home folder provider to use for people created via LDAP import</SPAN><BR /><SPAN>ldap.synchronization.defaultHomeFolderProvider=largeHomeFolderProvider</SPAN><BR /><BR /><SPAN># The attribute on LDAP group objects to map to the authority name property in Alfresco</SPAN><BR /><SPAN>ldap.synchronization.groupIdAttributeName=cn</SPAN><BR /><BR /><SPAN># The attribute on LDAP group objects to map to the authority display name property in Alfresco</SPAN><BR /><SPAN>ldap.synchronization.groupDisplayNameAttributeName=description</SPAN><BR /><BR /><SPAN># The group type in LDAP</SPAN><BR /><SPAN>ldap.synchronization.groupType=posixGroup</SPAN><BR /><BR /><SPAN># The person type in LDAP</SPAN><BR /><SPAN>ldap.synchronization.personType=inetOrgPerson</SPAN><BR /><BR /><SPAN># The attribute in LDAP on group objects that defines the DN for its members</SPAN><BR /><SPAN>ldap.synchronization.groupMemberAttributeName=member</SPAN><BR /><BR /><SPAN># If true progress estimation is enabled. When enabled, the user query has to be run twice in order to count entries.</SPAN><BR /><SPAN>ldap.synchronization.enableProgressEstimation=true</SPAN><BR /><BR /><SPAN># Requests timeout, in miliseconds, use 0 for none (default)</SPAN><BR /><SPAN>ldap.authentication.java.naming.read.timeout=0</SPAN><BR /><BR /><BR /><SPAN>Thanks for your help.</SPAN></BODY></HTML> Sun, 23 Mar 2014 00:04:25 GMT gianfi 2014-03-23T00:04:25Z Alfresco broken after upgrade to 4.2.f https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311956#M265086 Hello all,could anyone assist me with an upgrade from alfresco community 4.2.e to 4.2.f on ubuntu linux 12.04?After successfully completing the new installation and validating it, I try to point alfresco to the old root data directory. I get the following error after a restart:00:29:56,214 INFO&nbsp; [or Sun, 23 Mar 2014 00:04:25 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311956#M265086 gianfi 2014-03-23T00:04:25Z Re: Alfresco broken after upgrade to 4.2.f https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311957#M265087 <HTML><HEAD></HEAD><BODY><SPAN>Can you once again ensure that the directory path (path specified with dir.root property) is correct ?</SPAN><BR /><BR /><SPAN>Also you can refer these links (its related to your problem) :</SPAN><BR /><BR /><A href="https://forums.alfresco.com/comment/87023#comment-87023" rel="nofollow noopener noreferrer">https://forums.alfresco.com/comment/87023#comment-87023</A><BR /><BR /><A href="http://forums.alfresco.com/comment/19020#comment-19020" rel="nofollow noopener noreferrer">http://forums.alfresco.com/comment/19020#comment-19020</A><BR /></BODY></HTML> Sun, 23 Mar 2014 08:01:36 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311957#M265087 sanket 2014-03-23T08:01:36Z Re: Alfresco broken after upgrade to 4.2.f https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311958#M265088 <HTML><HEAD></HEAD><BODY><SPAN>Dear Sanket,</SPAN><BR /><SPAN>thanks for your reply.</SPAN><BR /><SPAN>The repository path is correctly set and points to my former repository:</SPAN><BR /><SPAN># ls /opt/alfresco-4.2.f/alf_data_repo</SPAN><BR /><SPAN>contentstore&nbsp; contentstore.deleted&nbsp; keystore&nbsp; lucene-indexes&nbsp; oouser&nbsp; postgresql</SPAN><BR /><BR /><SPAN>I already tried to reset the lucene indexes as described in your provided links, with no success.</SPAN><BR /><SPAN>Please note that if i try to start my old alfresco 4.2.e pointing to the repo directory, it works correctly.</SPAN><BR /><SPAN>Thank you</SPAN></BODY></HTML> Sun, 23 Mar 2014 15:04:00 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311958#M265088 gianfi 2014-03-23T15:04:00Z Re: Alfresco broken after upgrade to 4.2.f https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311959#M265089 <HTML><HEAD></HEAD><BODY><SPAN>It seems&nbsp; a system node(with path system://system/system:descriptor-current )'s property "versionProperties"s content&nbsp; does not exist in your content store.</SPAN><BR /><SPAN>You can modify repository.properties and set </SPAN><PRE class="language-none line-numbers"><CODE>system.bootstrap.config_check.strict =false <SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>,this will skip content missing check.</SPAN><BR /><SPAN>Remember to&nbsp; restart alfresco after modify repository.properties.</SPAN></BODY></HTML> Mon, 24 Mar 2014 00:34:00 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311959#M265089 kaynezhang 2014-03-24T00:34:00Z Re: Alfresco broken after upgrade to 4.2.f https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311960#M265090 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><SPAN>if I'm not wrong you should follow the upgrade guidelines even if you're migrating towards a minor release.</SPAN><BR /><SPAN>This means you should refer to here </SPAN><A href="http://docs.alfresco.com/4.2/topic/com.alfresco.enterprise.doc/concepts/ch-upgrade.html" rel="nofollow noopener noreferrer">http://docs.alfresco.com/4.2/topic/com.alfresco.enterprise.doc/concepts/ch-upgrade.html</A><BR /><SPAN>It seems you are trying to make your new 4.2.f installation to point to the old 4.2.e alf_data without restoring the 4.2.f database with the exported 4.2.e one.</SPAN><BR /><SPAN>Here </SPAN><A href="http://docs.alfresco.com/4.2/topic/com.alfresco.enterprise.doc/concepts/backup-intro.html" rel="nofollow noopener noreferrer">http://docs.alfresco.com/4.2/topic/com.alfresco.enterprise.doc/concepts/backup-intro.html</A><SPAN> it is stated: &lt;cite&gt;To restore the backup successfully, the directory and database must be backed up as a single unit. When you restore an Alfresco backup, you must restore both the dir.root directory (only the above mentioned directories) and the Alfresco database from the same backup set. Otherwise, the repository will be corrupted.&lt;/cite&gt;</SPAN><BR /><SPAN>You could always rebuild the indexes setting the index.recovery.mode=FULL when restating Alfresco.</SPAN><BR /><BR /><SPAN>Hope this helps.</SPAN><BR /><SPAN>Regards,</SPAN><BR /><SPAN>Andrea</SPAN></BODY></HTML> Tue, 25 Mar 2014 08:43:52 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-broken-after-upgrade-to-4-2-f/m-p/311960#M265090 abarisone 2014-03-25T08:43:52Z