KB: Cannot sign in to server after installation

Solution Details

Common Sign-In Errors After Installation

Users may see one or more of the following errors when attempting to sign in to the server:

• Error: Something went wrong. The underlying provider failed on open
• Error: The type initializer for ‘ExtentPlaceholderCreator’ threw an exception
• Error: Something went wrong. Dynamic SQL Error SQL error code = -204 Table unknown IDS_USER At line 92, column 4

These errors typically indicate a conflict between AIS and other SQL-based software installed on the same machine.

Why Conflicts Occur

Altium Infrastructure Server uses Firebird, a SQL-based database engine. If another SQL-based application (e.g., Microsoft SQL Server, Veeam) is already installed on the same machine, it may interfere with Firebird’s operation. This can prevent AIS from initializing its database correctly, leading to sign-in failures and other errors.

What to Do

To resolve or avoid these issues, consider the following options:

• Install AIS on a clean machine with no SQL-based software installed.
• Use the legacy Private License Server if server must run on a machine with SQL installed.
• Try reinstalling AIS after removing conflicting SQL software.
• Edit configuration files to resolve specific SQL-related exceptions.
• Switch to On-Demand Licensing to eliminate the need for a local license server.

How to Do It

Step 1: Verify License Installation

a. Ensure both licenses included in the installation package are installed.
b. Refer to: KB: Cannot Connect to Altium Infrastructure Server (AIS) to Use Private License

Step 2: Attempt Local Sign-In

a. On the server machine (via console or Remote Desktop), open a browser.
b. Navigate to: http://localhost:9780
c. Attempt to sign in.

Step 3: Check for SQL Conflicts

a. Determine if any SQL-based applications (e.g., Microsoft SQL Server, Veeam) are installed.
b. If so, consider:

• • Uninstalling the SQL application.
  • Installing AIS.
  • Reinstalling the SQL application.

Note: This method has worked for some users but is not guaranteed.

Step 4: Modify Configuration Files (Advanced)

a. Locate the web.config files in both the IDS and EDS directories.
b. Add the dependentAssembly section as shown here, under the <runtime> section:

<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" culture="neutral" />
      <bindingRedirect oldVersion="1.0.0.0-11.0.0.0" newVersion="10.0.0.0" />
    </dependentAssembly>

If issues persist, search the entire Altium folder for all web.config files and apply the same edit. One user reported editing 34 files to restore server functionality.

Step 5: Consider Using the Legacy Private License Server

Download from: Altium Miscellaneous Installers

Step 6: Switch to On-Demand Licensing (Recommended)

Benefits:

• No need for on-site license server.
• Licenses accessible from anywhere with internet.
• Offline use supported via license roaming.
• Lower annual cost compared to private server licenses.

Contact your account manager to convert your license type. Conversion typically takes one business day or less.

More info:

• Altium Designer License Management – On-Demand Licensing
• System Preferences – Information Gathered

Additional Notes

• AIS system requirements are minimal, making it feasible to install on a different machine.  See: Altium Infrastructure Server – System Requirements
• Community discussion on SQL conflicts: Altium Infrastructure Server vs Microsoft SQL Server 2012 (Geek And I blog post)