In-place DB Upgrade fails for Delegated Directories to Crowd 2.0.4

Still need help?

The Atlassian Community is here for you.

Ask the community


  • After an in-place DB upgrade, users have not been migrated over in your Delegated Directories.
  • You may see this error in the logs:
    2010-07-01 13:35:57,461 main FATAL [crowd.console.listener.UpgradeListener] Failed to initialise Crowd container
    java.lang.IllegalArgumentException: argument credential cannot be null
            at org.apache.commons.lang.Validate.notNull(
            at com.atlassian.crowd.integration.model.user.UserTemplateWithCredentialAndAttributes.<init>(
            at com.atlassian.crowd.migration.legacy.database.UserMapper.importUsersFromDatabase(
            at com.atlassian.crowd.migration.legacy.database.UserMapper.importFromDatabase(
            at com.atlassian.crowd.migration.legacy.database.DatabaseMigrator.importDatabase(
            at com.atlassian.crowd.migration.legacy.database.DatabaseMigrator$$FastClassByCGLIB$$20c39eb4.invoke(<generated>)
            at net.sf.cglib.proxy.MethodProxy.invoke(


This is caused by a bug that's been fixed. See In-place DB Upgrade fails for Delegated Directories to Crowd 2.0.4.


  1. Roll-back to the original database before the upgrade attempt.
  2. Use Crowd 2.0.5 or higher in the next upgrade attempt.

Last modified on Nov 21, 2012

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.