AnsweredAssumed Answered

Some Post-Upgrade Issues 4.2.c to 5.2.0

Question asked by phloyd on Jun 21, 2017
Latest reply on Jun 22, 2017 by cesarista

I've migrated all of my content and data from my 4.2.c production server over to my 5.2.0 testing server.

The migration went pretty smoothly and I can see the content, logins seem to work correctly, all the users are there, etc.

However, there are some nagging issues that the logs are reporting and I'm not sure how to solve them. So I will post them here in the hopes that somebody else might have some answers.


Issue #1: Active Directory Sync not working? I made sure to copy all the settings for ldap from the old global properties file to the new one.


2017-06-21 00:00:00,121 INFO [] [DefaultScheduler_Worker-4] Synchronizing users and groups with user registry 'ldap1'
2017-06-21 00:00:00,123 WARN [] [DefaultScheduler_Worker-4] Full synchronization with user registry 'ldap1'
2017-06-21 00:00:00,131 WARN [] [DefaultScheduler_Worker-4] Some users and groups previously created by synchronization with this user
registry may be removed.
2017-06-21 00:00:00,184 INFO [] [DefaultScheduler_Worker-4] Retrieving all groups from user registry 'ldap1'
2017-06-21 00:00:00,241 ERROR [] [DefaultScheduler_Worker-4] Synchronization aborted due to error
org.alfresco.error.AlfrescoRuntimeException: 05213109 Error during LDAP Search. Reason:domain:389


Issue #2: Unable to update tag scopes. I'm not really sure what this one means. The error appears in the logs exactly every two hours.


2017-06-21 00:55:45,151 ERROR [org.quartz.core.JobRunShell] [DefaultScheduler_Worker-9] Job DEFAULT.
taggingStartupJobDetail threw an unhandled Exception: java.lang.RuntimeException: Unable to update the tag scopes.
at org.alfresco.repo.tagging.UpdateTagScopesActionExecuter.executeImpl(

Caused by: org.alfresco.error.AlfrescoRuntimeException: 05213420 Node type is not recognised: {http:


If anyone has insight or ideas on these issues, your input is greatly appreciated.