Installation

A Meridian installation can range from a simple, stand-alone configuration for testing to a complex global network of vaults, optional modules, and integrated information systems. Meridian is distributed as either a full installation or an update, depending on the release.

Read the release notes included with each release before you begin. They contain specific information and instructions for the new version. Consider your required installation configuration and preparation steps.

• Stand-alone configuration: The computer acts as both server and client. Use this for evaluation purposes. All functionality is available.
• Client/server configuration: This requires at least two computers. One acts as the server, and all others act as clients. For more information, see Deployment Models.

Download release files from the Accruent website. Accruent Partners receive the download location and archive password by email. The setup programs detect previous versions and install the appropriate upgrade.

Accruent does not define your content security policy. Configure your security settings and add a corresponding HTTP header. For more information, see these resources

• OWASP - Content Security Policy
• Mozilla - Content Security Policy
• Google - CSP Evaluator Tool

Upgrade to Meridian 2025

If you upgrade to Meridian 2025 or 2025 SP from version 2023 or 2024, you may encounter an issue where email notifications fail (for example, when changing a document workflow for a subscription). In this case, the Application Event log displays the following error

An error occurred: Invalid column name 'VaultName'

Workarounds

Use one of the following methods to resolve this issue before a code patch is released

Option 1: Manually add the missing column (Recommended)

Execute this SQL command against the affected subscription database to add the required column

ALTER TABLE EmailQueue
ADD VaultName VARCHAR(MAX);

Option 2: Drop the existing table

Drop the EmailQueue table from the database. The application recreates the table with the correct schema, including the VaultName column, the next time a notification triggers.

DROP TABLE EmailQueue;