Altium On-Prem Enterprise Server
Our Knowledge Base is developed from our users questions. Find answers and step-by-step instructions. Chances are we’ve seen your question before.
KB: Backup when FIPS is enabled
We're trying to migrate our Concord Pro server installation to a new server, and that new server has a FIPS mode requirement. I cannot perform nightly backups or do any restores on this server with FIPS mode enabled, and I can't disable it. Running the backup results in "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms."
KB: Can't delete empty folder
Can't delete empty folder from managed content server
KB: Cannot sign in to server after installation
Users may encounter sign-in errors after installing Altium Infrastructure Server (AIS) due to conflicts between Firebird (used by AIS) and existing SQL-based applications on the same machine. These conflicts can result in various error messages, including issues with database access and dynamic SQL errors. This article outlines the root cause, recommended solutions, and step-by-step instructions to resolve the issue, including alternative licensing options and community-sourced workarounds.
KB: Cannot use a private license as the seat is occupied
If all seats of private license are occupied inadvertently, an adminstrator can still log into the server machine directly where the on-premise server product is installed (Vault/Nexus Server/Concord Pro/AIS/AES) either locally or via remote desktop to release the seat through a web interface
KB: Failed to Publish to PLM Due to "Error Retrieving Part by Number"
During the project publish process to PLM, users may encounter the error message: "Failed to publish. Error retrieving part by number." This issue typically arises when one or more BOM component items have invalid PLM Part Numbers, which are essential for synchronizing and creating BOM items in PLM. The error prevents successful retrieval of BOM Items during the publish operation. This article outlines the root cause and provides a step-by-step resolution to identify and correct the problematic components, ensuring a successful PLM publish.
KB: IIS URL Rewrite Rule to Force HTTP to HTTPS for Altium Server Connection
This article explains how to configure IIS URL Rewrite to automatically redirect HTTP requests to HTTPS for Altium On-Prem Enterprise Server without interfering with its internal services. The solution improves security and usability by ensuring all client connections use HTTPS on port 9785, while maintaining Altium’s operational integrity.
KB: Include Custom Text on the Home Page of Altium Enterprise Server
Some organizations require custom consent language or informational text to be displayed on the login page of their Altium Enterprise Server. This article outlines two methods for embedding such custom text into the login interface by modifying the LoginNexusServer.cshtml file. The second method is recommended for better visibility and layout control.
KB: Invalid Username or Password Error When Refreshing Private Server License
When attempting to refresh a license in the Server Browser interface of Altium Infrastructure Server (AIS), users may encounter the error message "Invalid Username/Password combination", even when logged in with administrative privileges. This issue typically arises due to incorrect AltiumLive credentials configured in the server settings. To resolve it, users must update the credentials with valid AltiumLive admin account details or manually add the license if online access is restricted.
KB: Multiple Server CAL checkout
Signing into Concord Pro or NEXUS Server, duplicate checkouts per user are happening.
KB: Preserving Lifecycle State during Component Synchronization
When synchronizing components from PLM Systems to Altium On-Prem Enterprise Server or Altium 365 Workspace (Enterprise Level), the lifecycle state of components can revert to "Draft" state after synchronization. This is problematic when dealing with bulk component synchronization, especially when many components are already in "Released" or "Approved" states, and you want to preserve the original lifecycle state of the components instead of changing it to "Draft".
KB: Resolve issues that were induced after on-premise server update and data migration
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.
KB: Resolving "Too many request sent" Error in Web Viewer
Users may encounter a "Too many requests sent." error when opening projects in the Altium On-Prem Enterprise Server Web Viewer. This error typically affects all projects, suggesting a server-side rather than project-specific issues. This article provides steps to identify and resolve the underlying issue.
KB: Resolving HTTP Error 500.30 ASP.NET Core app failed to start
This article addresses a common startup error encountered when launching the Altium Enterprise Server browser interface, typically caused by .NET runtime incompatibility. The error message includes a mismatch in content types and may reference an HTTP Error 500.30. Such issues often arise after Windows updates or server-side changes to the .NET runtime. The article outlines how to verify .NET compatibility, inspect system logs, reboot the server, and resolve Health Monitor errors to restore server functionality.
KB: Safeguard against unexpected errors/glitches during on-premise server upgrade
To prevent unexpected errors or glitches during an On-Prem Server upgrade, creating a Backup of the current Production Server is essential. This ensures that if any issues arise, you have a restore point.
KB: Secured port number usage for the Server Email Notifications
Altium Enterprise Server sends email notifications for various tasks and alerts. However, if these notifications are being sent using the unsecured HTTP port (9780) instead of the HTTPS port, it may pose a security risk. This article summarizes how to configure the server to use the secured HTTPS port for email notifications.
KB: Server License Not Set or All CALs in use
If you didn't get a chance to refresh the license for your on-site managed content server before it expired, you may see this error message when trying to sign in from a remote web browser. You can also use the method described in this article to log into your server when all the Client Access Licenses (CALs) are already in use.
KB: Set permissions on lifecycle change-of-state
Right now, all of our users are able to change the lifecycle state of components (i.e. draft, released, etc.) but we want to give only certain people permission. Is there a way to limit which users can change to which state?
KB: SVN discontinuation with AES 7.2.1
Starting with Altium On-Prem Enterprise Server (AES) 7.2.1, Subversion (SVN) repositories are no longer supported. This change affects users upgrading previous versions with SVN support enabled. This article outlines the steps to prepare for an upgrade and answers questions that may arise due to this change.
KB: Trouble accessing web viewer or on-prem server after a server name change
Customers may find that they cannot access specific services after a server update/server change. This can often be due to an improperly configured localvault.ini file, or site bindings. The solution details common symptoms, and the main things that need to be configured properly for proper AES operation. The solution is basically the KB article written out.
KB: Troubleshoot LDAP syncing
We are having issues with LDAP syncing with our Altium Server. It was working prior and we are now receiving: "There was no endpoint listening at http://localhost:9791/LdapSyncStatus that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details."