com.atlassian.crowd.migration.ImportException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Crowd 2.0.X started to consider that a Role is a Group type. Consequently, if a Group and a Role have the same name, during an XML restore, Crowd is reporting the following error: {code} com.atlassian.crowd.migration.ImportException: Could not validate the XML backup for import. See logs for more details. at com.atlassian.crowd.migration.XmlMigrationManagerImpl.importXml(XmlMigrationManagerImpl.java:176) at com.atlassian.crowd.console.action.setup.Import.doUpdate(Import.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358) at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192) {code} Instead of failing the restore process and showing the error directly in the UI, Crowd should: 1-) Inform the Admin about the changes with the Role elements. 2-) Inform that having Groups and Roles with the same name in the XML file is a problem in 2.0.X 3-) Ask the Admin if the Roles can be removed (only the ones that have the name matching a group name) 4-) Otherwise, cancel the restore process (without damaging the current instance)
    via by Renan Battaglin,
  • Crowd 2.0.X started to consider that a Role is a Group type. Consequently, if a Group and a Role have the same name, during an XML restore, Crowd is reporting the following error: {code} com.atlassian.crowd.migration.ImportException: Could not validate the XML backup for import. See logs for more details. at com.atlassian.crowd.migration.XmlMigrationManagerImpl.importXml(XmlMigrationManagerImpl.java:176) at com.atlassian.crowd.console.action.setup.Import.doUpdate(Import.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358) at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192) {code} Instead of failing the restore process and showing the error directly in the UI, Crowd should: 1-) Inform the Admin about the changes with the Role elements. 2-) Inform that having Groups and Roles with the same name in the XML file is a problem in 2.0.X 3-) Ask the Admin if the Roles can be removed (only the ones that have the name matching a group name) 4-) Otherwise, cancel the restore process (without damaging the current instance)
    via by Renan Battaglin,
    • com.atlassian.crowd.migration.ImportException: Could not validate the XML backup for import. See logs for more details. at com.atlassian.crowd.migration.XmlMigrationManagerImpl.importXml(XmlMigrationManagerImpl.java:176) at com.atlassian.crowd.console.action.setup.Import.doUpdate(Import.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358) at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
    No Bugmate found.