Search fails with error - Can't associate project project-name-here with entityId PROJECT-NAME-HERE

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

When you try to search for anything in the search box that's displayed on the top right corner of Fisheye/Crucible, this error occurs:

1 2 3 4 5 6 7 8 9 2012-02-20 10:45:50,895 INFO [btpool0-3002 ] fisheye.app TotalityFilter-logCause - Cause: Can't associate project project-name-here with entityId PROJECT-NAME-HERE java.lang.IllegalArgumentException: Can't associate project project-name-here with entityId PROJECT-NAME-HERE at com.atlassian.fisheye.user.model.RecentlyVisitedRepository.setRepository(RecentlyVisitedRepository.java:19) at com.atlassian.fisheye.user.model.RecentlyVisitedRepositoryFactory.load(RecentlyVisitedRepositoryFactory.java:22) at com.atlassian.fisheye.user.model.RecentlyVisitedRepositoryFactory.load(RecentlyVisitedRepositoryFactory.java:7) at com.atlassian.fisheye.user.DefaultRecentlyVisitedManager.loadHistory(DefaultRecentlyVisitedManager.java:107) at com.atlassian.fisheye.user.DefaultRecentlyVisitedManager.getHistory(DefaultRecentlyVisitedManager.java:130) at com.atlassian.fisheye.user.DefaultRecentlyVisitedManager.getHistory(DefaultRecentlyVisitedManager.java:115) at com.atlassian.fisheye.quicksearch.action.QuickSearchAction.getRecentOrFirstRepository(QuickSearchAction.java:448)

Cause

The quick-search metadata index became corrupted.

Resolution

  1. Shut down the Fisheye/Crucible instance;

  2. Delete the contents of the <FISHEYE_INST>/cache/globalfe directory;

  3. Restart the instance - this will force a rebuild of the quick-search metadata and content index.

If the above process fails to work, proceed with the following steps to clear out the old data from the database directly:

  1. Stop the application.

  2. Make a backup of the database.

  3. Delete the obsolete entries from the cru_recently_visited following table: DELETE * FROM cru_recently_visited WHERE cru_entity_id='<PROJECT-NAME-HERE>';

  4. Start the application.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.