Concord Pro issues after migration - Re-index

Created: 25.03.2021 | Updated: 12.08.2021

After updating Concord Pro you may experience some of these issues: The "500 Internal Server Error" error message. Component cannot be released. Health monitor may show index errors. Re-indexing likely will resolve these issues. This article tells you how.

Solution Details

To re-index server content, for example after data migration:
  1. Stop all IIS application pools associated to Altium Concord Pro (CP).  This can be done by opening the Internet Information Services Manager (IIS).
  2. Stop the Elasticsearch (AltiumElasticSearch) service. This is performed from the Windows Services panel - accessed from Window's Administrative Tools window. (for CP)
  3. Delete the content of the SearchData folder, which contains the search indexing data (:\ProgramData \Altium\ConcordProData\SearchData for CP)
    :\ProgramData \Altium\VaultServerData\SearchData for legacy Vault install.
  4. Restart the Elasticsearch (AltiumElasticSearch) service.
  5. Restart the IIS application pools associated with CP.
On finding the SearchData folder empty, Altium CP will re-index its content once it starts.
For more detail, please see this documentation:!re-indexing-server-content-after-data-migration
It may be best to perform this task when users are less likely to need access to the server since the rebuild can take some time depending on the size of the database and may affect the searching of parts and items during the rebuild.
Was this article helpful?
Обнаружили проблему в этом документе? Выделите область и нажмите Ctrl+Enter, чтобы оповестить нас.

Связаться с нами

Связаться с нашими Представительствами напрямую

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
Вы сообщаете о проблеме, связанной со следующим выделенным текстом
и/или изображением в активном документе: