In-place DB Upgrade fails for Delegated Directories to Crowd 2.0.4
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
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(Validate.java:203) at com.atlassian.crowd.integration.model.user.UserTemplateWithCredentialAndAttributes.<init>(UserTemplateWithCredentialAndAttributes.java:25) at com.atlassian.crowd.migration.legacy.database.UserMapper.importUsersFromDatabase(UserMapper.java:108) at com.atlassian.crowd.migration.legacy.database.UserMapper.importFromDatabase(UserMapper.java:44) at com.atlassian.crowd.migration.legacy.database.DatabaseMigrator.importDatabase(DatabaseMigrator.java:38) at com.atlassian.crowd.migration.legacy.database.DatabaseMigrator$$FastClassByCGLIB$$20c39eb4.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
Cause
This is caused by a bug that's been fixed. See CWD-1946 - In place upgrade will fail for Delegated directories where users do not have a credential in the database.
Resolution
Roll-back to the original database before the upgrade attempt.
Use Crowd 2.0.5 or higher in the next upgrade attempt.
Was this helpful?