Contact Us
Contact our corporate or local offices directly.
Created: March 25, 2021 | Updated: August 12, 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:- Stop all IIS application pools associated to Altium Concord Pro (CP). This can be done by opening the Internet Information Services Manager (IIS).
- Stop the Elasticsearch (AltiumElasticSearch) service. This is performed from the Windows Services panel - accessed from Window's Administrative Tools window. (for CP)
- 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. - Restart the Elasticsearch (AltiumElasticSearch) service.
- Restart the IIS application pools associated with CP.
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?