Installing Aligned Elements Web Server
  • Elements SPA Installation
  • Preparing the Windows Server
    • Before you get started
    • Install and Configure SQL Server for Aligned Elements
    • Install .NET 4.8
    • Install/Activate the IIS
    • Enable ASP.NET 4.5/4.6/4.7
    • Optional: IIS Always running part 1
    • Installing Web Platform Installer and Web deploy
    • Install URL Rewrite Module
    • Install IIS Crypto to disable Weak Ciphers and Protocols
  • Deploying the Aligned Elements Web Solution
    • Install the Aligned Elements Web Server Package
    • Setting HTTP Strict Transport Security (HSTS)
    • Optional: Open Ports in the Network on Azure hosted Virtual Machines
    • Optional: Get a SSL certificate from Let’s Encrypt
    • Binding your SSL certificate to the Aligned Elements web site
    • Creating the „Temp“ and „Files“ directories
    • Remove stdole.dll from bin directory
    • Move ElementsSPA.xml from the "App_Data" folder to the "bin" folder
    • Add the Aligned Elements License Files
    • Set the necessary security permissions for directories
    • Optional: IIS Always running part 2
    • Install necessary Unicode Font
    • Install and Configure File Server Resource Manager
  • Configure Application Options in web.config
    • Configure Application Options in web.config
    • Set the Server and connection string
    • Always Require SSL
    • Referring to the Project Templates
    • Email Configuration
    • Word Add-in Configuration and deployment
      • Distribute an Add-in using the Office 365 admin center
      • Distribute the Add-in using sideloading for Windows
      • Distribute the Add-in using sideloading for Mac
    • Optional: Integration of the Aligned Elements Automation Tool
      • Importing Dashboards with Rename using the Automation Script
    • Optional: Enabling Active Directory Integration
  • Optional: Configuration of AI Features
  • Create an Initial User
    • Option 1: Aligned Elements Projects already exist
    • Option 2: New Web server, no Aligned Elements Projects exist
  • Upgrading the Aligned Elements Web Server
    • Upgrading a Server
  • Troubleshooting
    • Generic Server Error
    • Missing version of stdole.dll
    • Missing Dependencies for Txic.dll
    • Error shown: Could not load file or assembly “System.Net.Http”
    • 500 Internal Server Error
    • Error when trying to start application
    • The server is not starting after upgrading to v2.5 SP 4 Part 1
    • The server is not starting after upgrading to v2.5 SP 4 Part II
    • Load a project works but when clicking on a design Item, you are re-directed to the login
    • The application cannot connect to the license server
    • The urls in email notifications are incorrect/missing port information
    • Missing Font
    • Mismatch of server name between Windows-client and Web.
  • Cannot upload Templates
  • Running 'ElementsSPAPackage.deploy.cmd' closes the Command-Prompt window
  • Web.config Settings
    • Settings of the Web.config
Powered by GitBook
On this page

Was this helpful?

  1. Configure Application Options in web.config

Set the Server and connection string

PreviousConfigure Application Options in web.configNextAlways Require SSL

Last updated 12 months ago

Was this helpful?

The web.config appSetting entry serverString contains the database server instance name, so this needs to be adapted in the web-config.

(If the version of Aligned Elements being installed is older than V3.0, the same database server instance name also has to be updated in the connectionStrings section for ElementsSessions).

Note: If the Aligned Elements windows-client is also used in the organisation, the SQL server name must match the SQL Server name used in the Aligned Elements windows client. This can be hard if a named instance is used for the sql server database. It is recommended to use a default instance instead (i.e. without \SQLEXPRESS). An alternative is to manually set static ports for a named instance (see https://community.spiceworks.com/how_to/124598-find-the-port-sql-server-is-using-and-change-a-dynamic-port-to-static ) and omit the instance name when connecting.