Concord Pro issues after migration - Re-index

Created: March 25, 2021 | Updated: June 7, 2022

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).  It's OK to just stop IIS with the "Stop" action in the "Actions" panel at the right.  Or you can use "IISreset [computername] /STOP  from a Command line.
  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:
https://www.altium.com/documentation/altium-designer/altium-concord-pro-info-for-it-departments#!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?
0
0
Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: