KB: Resolve issues that were induced after on-premise server updates and data migrations
Created: 十一月 27, 2024 | Updated: 十一月 27, 2024
Altium On-Prem Enterprise Server
After updating an On-Prem server 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: (We recommend performing a backup before starting.)
- Stop all IIS application pools associated to the On-Prem server. 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.
- Stop the Elasticsearch (AltiumElasticSearch) service. This is performed from the Windows Services panel - accessed from Window's Administrative Tools window. (for Concord Pro (CP) or later versions
- 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.
On finding the SearchData folder empty, the On-Prem server will re-index its content once it starts.
For more detail, please see this documentation:
https://www.altium.com/documentation/enterprise-server/details-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.