Error: "Table 'crowd.REMOTEGROUP' doesn't exist" After Migrating Crowd Database From Another Server
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
Problem
Crowd does not start up properly after undergo a database migration task. The following error appeared on the login page:
An error occurred when querying the database <Table 'crowd.REMOTEGROUP' doesn't exist>The following appears in the atlassian-crowd.log
/opt/crowd/logs/atlassian-crowd.log:2015-03-17 09:36:30,808 localhost-startStop-1 INFO[migration.legacy.database.DatabaseMigrationManager] Legacy Crowd version detected <216>.
/opt/crowd/logs/atlassian-crowd.log:2015-03-17 09:36:30,808 localhost-startStop-1 INFO[crowd.migration.verify.SupportedDatabaseVerifier] Checking if database can be automatically migrat
ed.
/opt/crowd/logs/atlassian-crowd.log:2015-03-17 09:36:30,808 localhost-startStop-1 INFO[crowd.migration.verify.LegacyDatabaseVerifier] Checking legacy database for data validity.
/opt/crowd/logs/atlassian-crowd.log:2015-03-17 09:36:30,936 localhost-startStop-1 ERROR[migration.legacy.database.DatabaseMigrationManager] An in-place upgrade is not possible for your
database, for the following reasons: An error occurred when querying the database <Table 'crowd.REMOTEGROUP' doesn't exist>
/opt/crowd/logs/atlassian-crowd.log:2015-03-17 09:36:30,937 localhost-startStop-1 FATAL[crowd.console.listener.StartupListener] Errors experienced during the Crowd upgrade process: [An error occurred when querying the database <Table 'crowd.REMOTEGROUP' doesn't exist>]
Diagnosis
Crowd does not have the table crowd.REMOTEGROUP since Crowd 2.0.
Cause
It seems like Crowd is trying to perform an upgrade task. It assumes that this is an upgrade process from a really old version of Crowd where the table crowd.REMOTEGROUP still exists.
Resolution
Do the following:
- Shut down Crowd
- Go to Crowd_Home_Directory
- Locate crowd.cfg.xml
Try to modify the following lines:
<buildNumber>216</buildNumber>Change the build number to your current version's build number. Cross reference from this documentation: Crowd Build and Version Numbers Reference
For example, change the above line to look like the following if the Crowd's version is Crowd 2.8.0:
<buildNumber>645</buildNumber>Restart Crowd and check if the issue persist.