LevelBlue Knowledge Base » Knowledgebase » Marshal Reporting Console

Enabling Strong TLS for .NET

Charles — Thu, 16 Apr 2026 22:53:51 GMT

This article applies to:

MailMarshal SPE 4.X - Systems with TLS 1.0 disabled
Marshal Reporting Console - email TLS

Question:

How do I enable use of TLS 1.1 and 1.2 by .NET components in SPE 4.X?
How do I fix TLS related errors connecting from SPE to the SEG Array Manager?
How do I update the TLS version used for email connectivity in MRC?

Procedure:

To allow use of "Strong" TLS (1.1 and 1.2) by .NET, you must enable system settings and .NET specific settings on affected systems.

For SPE this is the Marshal Interface Agent server.
For MRC this is the server where the software is installed.

This article covers .NET specific settings.

Update the following Registry entries (see also the attached Powershell script):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001

Notes:

SPE 5.X and above uses newer versions of .NET and does not require these settings.
The SchUseStrongCrypto setting allows .NET to use TLS 1.1 and TLS 1.2.
The SystemDefaultTlsVersions setting allows .NET to use the OS configuration.
For further information see Microsoft documentation.
These settings apply immediately. System or service restart is not required.

Supported Operating Systems and Prerequisite Versions

Charles — Thu, 16 Apr 2026 20:46:27 GMT

This article applies to:

MailMarshal (SEG) 10.0 and above
- MailMarshal Web Components (SQM)
WebMarshal 7.6
Marshal Reporting Console 2.6 (for SEG, ECM, and WebMarshal reports)

(For ECM/MailMarshal Exchange, see Q14131. For Service Provider Edition [SPE], see Q11588.)

Question:

What are the supported operating systems for MailMarshal and WebMarshal?
What version of SQL Server can be used with MailMarshal and WebMarshal?
What versions of SQL, IIS and ASP.NET are required and supported?

Information:

This article shows supported versions of operating systems and supporting software.

Notes:

OS and SQL versions earlier than those listed are not supported.

OS and SQL versions that are out of support from Microsoft are not supported.

The information reflects the latest versions of the named products. For details of previous versions, see the documentation for each version.

The information reflects server requirements. For details of requirements for all user interfaces, see the documentation for each product version.

VMWare deployments of the supported operating systems are also supported. See LevelBlue Knowledgebase article Q11828.

Key:

Symbol	Meaning
RTM	Release to Manufacturing, no service pack.
SPn KBnnn	Minimum required service pack or Microsoft Update. Later service packs are supported.
Qxxxxxx	Tested, Supported. See the KB article listed for known issues and workarounds.
	Not currently supported, obsolete, or known issues.
	Not specifically tested. Not yet supported. LevelBlue plans to test and provide support in a later product release. For details of the policy on new OS and SP versions, see Q13687.
(blank)	Not applicable to this product.

Operating Systems and Prerequisites

The table below lists minimum compatible operating system versions and service packs. The products have been tested with the minimum compatible service pack (and in some cases with later service packs).

Note on Service Packs and Operating System updates: If product functionality is affected by Service Packs or Microsoft updates, LevelBlue will work with customers to restore functionality. If a full resolution requires product development, it may not be available immediately.

The listed products do not support RISC architectures. x64 or x86 is the supported architecture.

Server Operating Systems

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Windows Server 2025	RTM	RTM	Q21228 (Limited testing performed)	RTM
Windows Server 2022	RTM	RTM	RTM	RTM
Windows Server 2019	RTM (Also with any SEG 8.X)	RTM	RTM	RTM
Windows Server 2016	RTM	RTM	RTM	RTM
Windows Server 2012 R2 See also SQL Server service pack requirements			KB2919355
Windows Server 2012 See also SQL Server service pack requirements	(10.0.6 is the last release that allows installation on Windows 2012)		RTM
Windows Server Core edition (any release)

Workstation Operating Systems
(for server installation)

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Windows 10 or 11 (32 and 64 bit) See also SQL Server service pack requirements	RTM (64 bit required. Permitted but not recommended)	RTM (Permitted but not recommended)		RTM (Permitted but not recommended)

Prerequisites

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Web Browser	The Management Console works with Microsoft Edge, Mozilla Firefox, Google Chrome and Safari. Internet Explorer is explicitly not supported.	SQM works with current versions of major browsers, such as Edge, Mozilla Firefox, Google Chrome and Safari.	MRC works with current versions of major browsers, such as Edge, Mozilla Firefox, Google Chrome and Safari.	Any browser can be used as client.
.NET Framework (minimum - later 4.X is also supported)	4.6.1 MailMarshal also automatically installs a version of the newer .NET technology (previously known as .NET Core) on Array Manager servers.	3.5 SP1 and 4.0	3.5 SP1 (Note that SQL 2016 requires .NET 4.6)	4.6.2

SQL Server Versions

	MailMarshal 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
SQL 2012 SQL Express 2012 (Microsoft ESU ends July 2025)	(10.0.6 is the last release that allows installation using SQL 2012)
SQL 2014 SQL Express 2014 (Microsoft ESU ends July 2027)	*(CAUTION: Upgrade from earlier versions fails under SQL 2014)*	SP3	SP3
SQL 2016 SQL Express 2016	*(CAUTION: Upgrade from earlier versions fails under SQL 2016)*	SP3	SP3
SQL 2017 SQL Express 2017	RTM		RTM
SQL 2019 SQL Express 2019	RTM		RTM
SQL 2022 SQL Express 2022	RTM	Can upgrade from SQL 2016 Q21228	RTM
Azure SQL Server	Supported where MailMarshal is deployed on Azure

Notes on MRC Installation

MRC 2.6 cannot be installed with SQL versions later than 2016 for the reporting database. However, after installation using the bundled SQL 2016 Express, the SQL Express instances can be upgraded. See Q21228.
MRC can report on data in MailMarshal or WebMarshal databases hosted on later SQL versions.

Supported Operating Systems and Prerequisite Versions

Charles — Thu, 16 Apr 2026 20:46:27 GMT

This article applies to:

MailMarshal (SEG) 10.0 and above
- MailMarshal Web Components (SQM)
WebMarshal 7.6
Marshal Reporting Console 2.6 (for SEG, ECM, and WebMarshal reports)

(For ECM/MailMarshal Exchange, see Q14131. For Service Provider Edition [SPE], see Q11588.)

Question:

What are the supported operating systems for MailMarshal and WebMarshal?
What version of SQL Server can be used with MailMarshal and WebMarshal?
What versions of SQL, IIS and ASP.NET are required and supported?

Information:

This article shows supported versions of operating systems and supporting software.

Notes:

OS and SQL versions earlier than those listed are not supported.

OS and SQL versions that are out of support from Microsoft are not supported.

The information reflects the latest versions of the named products. For details of previous versions, see the documentation for each version.

The information reflects server requirements. For details of requirements for all user interfaces, see the documentation for each product version.

VMWare deployments of the supported operating systems are also supported. See LevelBlue Knowledgebase article Q11828.

Key:

Symbol	Meaning
RTM	Release to Manufacturing, no service pack.
SPn KBnnn	Minimum required service pack or Microsoft Update. Later service packs are supported.
Qxxxxxx	Tested, Supported. See the KB article listed for known issues and workarounds.
	Not currently supported, obsolete, or known issues.
	Not specifically tested. Not yet supported. LevelBlue plans to test and provide support in a later product release. For details of the policy on new OS and SP versions, see Q13687.
(blank)	Not applicable to this product.

Operating Systems and Prerequisites

Note on Service Packs and Operating System updates: If product functionality is affected by Service Packs or Microsoft updates, LevelBlue will work with customers to restore functionality. If a full resolution requires product development, it may not be available immediately.

The listed products do not support RISC architectures. x64 or x86 is the supported architecture.

Server Operating Systems

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Windows Server 2025	RTM	RTM	Q21228 (Limited testing performed)	RTM
Windows Server 2022	RTM	RTM	RTM	RTM
Windows Server 2019	RTM (Also with any SEG 8.X)	RTM	RTM	RTM
Windows Server 2016	RTM	RTM	RTM	RTM
Windows Server 2012 R2 See also SQL Server service pack requirements			KB2919355
Windows Server 2012 See also SQL Server service pack requirements	(10.0.6 is the last release that allows installation on Windows 2012)		RTM
Windows Server Core edition (any release)

Workstation Operating Systems
(for server installation)

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Windows 10 or 11 (32 and 64 bit) See also SQL Server service pack requirements	RTM (64 bit required. Permitted but not recommended)	RTM (Permitted but not recommended)		RTM (Permitted but not recommended)

Prerequisites

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Web Browser	The Management Console works with Microsoft Edge, Mozilla Firefox, Google Chrome and Safari. Internet Explorer is explicitly not supported.	SQM works with current versions of major browsers, such as Edge, Mozilla Firefox, Google Chrome and Safari.	MRC works with current versions of major browsers, such as Edge, Mozilla Firefox, Google Chrome and Safari.	Any browser can be used as client.
.NET Framework (minimum - later 4.X is also supported)	4.6.1 MailMarshal also automatically installs a version of the newer .NET technology (previously known as .NET Core) on Array Manager servers.	3.5 SP1 and 4.0	3.5 SP1 (Note that SQL 2016 requires .NET 4.6)	4.6.2

SQL Server Versions

	MailMarshal 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
SQL 2012 SQL Express 2012 (Microsoft ESU ends July 2025)	(10.0.6 is the last release that allows installation using SQL 2012)
SQL 2014 SQL Express 2014 (Microsoft ESU ends July 2027)	*(CAUTION: Upgrade from earlier versions fails under SQL 2014)*	SP3	SP3
SQL 2016 SQL Express 2016	*(CAUTION: Upgrade from earlier versions fails under SQL 2016)*	SP3	SP3
SQL 2017 SQL Express 2017	RTM		RTM
SQL 2019 SQL Express 2019	RTM		RTM
SQL 2022 SQL Express 2022	RTM	Can upgrade from SQL 2016 Q21228	RTM
Azure SQL Server	Supported where MailMarshal is deployed on Azure

Notes on MRC Installation

MRC 2.6 cannot be installed with SQL versions later than 2016 for the reporting database. However, after installation using the bundled SQL 2016 Express, the SQL Express instances can be upgraded. See Q21228.
MRC can report on data in MailMarshal or WebMarshal databases hosted on later SQL versions.

Supported Operating Systems and Prerequisite Versions

Charles — Thu, 16 Apr 2026 20:46:27 GMT

This article applies to:

MailMarshal (SEG) 10.0 and above
- MailMarshal Web Components (SQM)
WebMarshal 7.6
Marshal Reporting Console 2.6 (for SEG, ECM, and WebMarshal reports)

(For ECM/MailMarshal Exchange, see Q14131. For Service Provider Edition [SPE], see Q11588.)

Question:

What are the supported operating systems for MailMarshal and WebMarshal?
What version of SQL Server can be used with MailMarshal and WebMarshal?
What versions of SQL, IIS and ASP.NET are required and supported?

Information:

This article shows supported versions of operating systems and supporting software.

Notes:

OS and SQL versions earlier than those listed are not supported.

OS and SQL versions that are out of support from Microsoft are not supported.

The information reflects the latest versions of the named products. For details of previous versions, see the documentation for each version.

The information reflects server requirements. For details of requirements for all user interfaces, see the documentation for each product version.

VMWare deployments of the supported operating systems are also supported. See LevelBlue Knowledgebase article Q11828.

Key:

Symbol	Meaning
RTM	Release to Manufacturing, no service pack.
SPn KBnnn	Minimum required service pack or Microsoft Update. Later service packs are supported.
Qxxxxxx	Tested, Supported. See the KB article listed for known issues and workarounds.
	Not currently supported, obsolete, or known issues.
	Not specifically tested. Not yet supported. LevelBlue plans to test and provide support in a later product release. For details of the policy on new OS and SP versions, see Q13687.
(blank)	Not applicable to this product.

Operating Systems and Prerequisites

Note on Service Packs and Operating System updates: If product functionality is affected by Service Packs or Microsoft updates, LevelBlue will work with customers to restore functionality. If a full resolution requires product development, it may not be available immediately.

The listed products do not support RISC architectures. x64 or x86 is the supported architecture.

Server Operating Systems

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Windows Server 2025	RTM	RTM	Q21228 (Limited testing performed)	RTM
Windows Server 2022	RTM	RTM	RTM	RTM
Windows Server 2019	RTM (Also with any SEG 8.X)	RTM	RTM	RTM
Windows Server 2016	RTM	RTM	RTM	RTM
Windows Server 2012 R2 See also SQL Server service pack requirements			KB2919355
Windows Server 2012 See also SQL Server service pack requirements	(10.0.6 is the last release that allows installation on Windows 2012)		RTM
Windows Server Core edition (any release)

Workstation Operating Systems
(for server installation)

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Windows 10 or 11 (32 and 64 bit) See also SQL Server service pack requirements	RTM (64 bit required. Permitted but not recommended)	RTM (Permitted but not recommended)		RTM (Permitted but not recommended)

Prerequisites

	MailMarshal 11.3	MailMarshal Web Components 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
Web Browser	The Management Console works with Microsoft Edge, Mozilla Firefox, Google Chrome and Safari. Internet Explorer is explicitly not supported.	SQM works with current versions of major browsers, such as Edge, Mozilla Firefox, Google Chrome and Safari.	MRC works with current versions of major browsers, such as Edge, Mozilla Firefox, Google Chrome and Safari.	Any browser can be used as client.
.NET Framework (minimum - later 4.X is also supported)	4.6.1 MailMarshal also automatically installs a version of the newer .NET technology (previously known as .NET Core) on Array Manager servers.	3.5 SP1 and 4.0	3.5 SP1 (Note that SQL 2016 requires .NET 4.6)	4.6.2

SQL Server Versions

	MailMarshal 11.3	Marshal Reporting Console 2.6	WebMarshal 7.6
SQL 2012 SQL Express 2012 (Microsoft ESU ends July 2025)	(10.0.6 is the last release that allows installation using SQL 2012)
SQL 2014 SQL Express 2014 (Microsoft ESU ends July 2027)	*(CAUTION: Upgrade from earlier versions fails under SQL 2014)*	SP3	SP3
SQL 2016 SQL Express 2016	*(CAUTION: Upgrade from earlier versions fails under SQL 2016)*	SP3	SP3
SQL 2017 SQL Express 2017	RTM		RTM
SQL 2019 SQL Express 2019	RTM		RTM
SQL 2022 SQL Express 2022	RTM	Can upgrade from SQL 2016 Q21228	RTM
Azure SQL Server	Supported where MailMarshal is deployed on Azure

Notes on MRC Installation

MRC 2.6 cannot be installed with SQL versions later than 2016 for the reporting database. However, after installation using the bundled SQL 2016 Express, the SQL Express instances can be upgraded. See Q21228.
MRC can report on data in MailMarshal or WebMarshal databases hosted on later SQL versions.

Upgrading SQL Reporting Services to SQL 2022

Charles — Thu, 16 Apr 2026 20:42:45 GMT

This article applies to:

Marshal Reporting Console
SQL Server and SSRS 2022

Question:

Can I install MRC with SQL 2022?
Can I upgrade the MRC SQL and SQL Reporting Services instances to SQL 2022?

Procedure:

MRC 2.6 cannot be directly installed with SSRS 2022. However it is possible to upgrade the standalone MRC instances to SQL 2022 and SSRS 2022.

This procedure assumes you have installed MRC using the bundled SQL Express 2016 Advanced installer, and tested operation.

This procedure can also be used for a new installation on Windows 2025 (SQL Express 2016 must be manually installed first - see the notes section below).

Install SQL 2016 Service Pack 3 for the MRC_SQLEXPRESS instance. A computer restart will be required after installation.
From the Start menu, open Reporting Services Configuration Manager.
- Note the Report Server Database Name (by default, ReportServer$MRC_SQLEXPRESS). If you have used custom credentials, note the settings.
- From the Encryption Keys page, back up the key to a file.
- Exit the Reporting Services Configuration Manager.
Install Microsoft SQL Server 2022 Reporting Services.
- Choose the free edition Express.
- On the Setup Complete screen, click Configure report server.
In the Report Server Configuration Manager:
- On the WebService URL page, click Apply to accept the default values.
- On the Database page, click Change Database. In the wizard,
  - Select Choose an existing report server database.
  - On the Database Server page, the Server Name is the local computer name with MRC_SQLEXPRESS. Do not choose "Encrypt".
  - On the Database page, select the database you noted in step 2.
  - On the Credentials page, if you have not used the default service credentials, enter the credentials you noted in step 2.
  - Complete the wizard, click Finish, and exit the wizard.
  - On the Encryption Keys page, restore the key from your backup. You will be asked for confirmation to remove other registered servers. Click OK to this question.
  - Exit the Reporting Services Configuration Manager.
Upgrade to SQL Server 2022 Express.
- On the Welcome screen, choose the Custom option.
- On the Installation Center screen, choose Upgrade.
- On the Select Instance screen, select MRC_SQLEXPRESS.
- On the Reporting Services Migration screen, check the box Uninstall Reporting Services.
- Complete the upgrade process.

Notes:

On Windows Server 2025 the MRC installer cannot be used to install SQL Express. However you can manually install SQL Express 2016 SP3 Advanced before installing MRC, and choose to use the existing installation.
- Do not select installation of "R Services"
- Remember to select "Mixed Mode" authentication.
- You must also enable TCP connections to the SQL instance, using SQL Configuration Manager.
In some cases (where a current release of MailMarshal Array Manager is installed on the same server), the installation of SQL 2022 may report an error on installation of MSOLEDBSQL.

You can safely ignore this error and continue. MailMarshal has already installed a compatible version of MSOLDDBSQL.
If the error appears in the rules check and you cannot continue:
- Stop the MailMarshal Array Manager.
- Uninstall the offending version of MSOLEDBSQL.
- Upgrade SQL
- Re-install the version of MSOLEDBSQL. All versions are available for download from Microsoft.
- Start the Array Manager.

Upgrading SQL Reporting Services to SQL 2022

Charles — Thu, 16 Apr 2026 20:42:45 GMT

This article applies to:

Marshal Reporting Console
SQL Server and SSRS 2022

Question:

Can I install MRC with SQL 2022?
Can I upgrade the MRC SQL and SQL Reporting Services instances to SQL 2022?

Procedure:

MRC 2.6 cannot be directly installed with SSRS 2022. However it is possible to upgrade the standalone MRC instances to SQL 2022 and SSRS 2022.

This procedure assumes you have installed MRC using the bundled SQL Express 2016 Advanced installer, and tested operation.

This procedure can also be used for a new installation on Windows 2025 (SQL Express 2016 must be manually installed first - see the notes section below).

Install SQL 2016 Service Pack 3 for the MRC_SQLEXPRESS instance. A computer restart will be required after installation.
From the Start menu, open Reporting Services Configuration Manager.
- Note the Report Server Database Name (by default, ReportServer$MRC_SQLEXPRESS). If you have used custom credentials, note the settings.
- From the Encryption Keys page, back up the key to a file.
- Exit the Reporting Services Configuration Manager.
Install Microsoft SQL Server 2022 Reporting Services.
- Choose the free edition Express.
- On the Setup Complete screen, click Configure report server.
In the Report Server Configuration Manager:
- On the WebService URL page, click Apply to accept the default values.
- On the Database page, click Change Database. In the wizard,
  - Select Choose an existing report server database.
  - On the Database Server page, the Server Name is the local computer name with MRC_SQLEXPRESS. Do not choose "Encrypt".
  - On the Database page, select the database you noted in step 2.
  - On the Credentials page, if you have not used the default service credentials, enter the credentials you noted in step 2.
  - Complete the wizard, click Finish, and exit the wizard.
  - On the Encryption Keys page, restore the key from your backup. You will be asked for confirmation to remove other registered servers. Click OK to this question.
  - Exit the Reporting Services Configuration Manager.
Upgrade to SQL Server 2022 Express.
- On the Welcome screen, choose the Custom option.
- On the Installation Center screen, choose Upgrade.
- On the Select Instance screen, select MRC_SQLEXPRESS.
- On the Reporting Services Migration screen, check the box Uninstall Reporting Services.
- Complete the upgrade process.

Notes:

On Windows Server 2025 the MRC installer cannot be used to install SQL Express. However you can manually install SQL Express 2016 SP3 Advanced before installing MRC, and choose to use the existing installation.
- Do not select installation of "R Services"
- Remember to select "Mixed Mode" authentication.
- You must also enable TCP connections to the SQL instance, using SQL Configuration Manager.
In some cases (where a current release of MailMarshal Array Manager is installed on the same server), the installation of SQL 2022 may report an error on installation of MSOLEDBSQL.

You can safely ignore this error and continue. MailMarshal has already installed a compatible version of MSOLDDBSQL.
If the error appears in the rules check and you cannot continue:
- Stop the MailMarshal Array Manager.
- Uninstall the offending version of MSOLEDBSQL.
- Upgrade SQL
- Re-install the version of MSOLEDBSQL. All versions are available for download from Microsoft.
- Start the Array Manager.

Upgrading SQL Reporting Services to SQL 2022

Charles — Thu, 16 Apr 2026 20:42:45 GMT

This article applies to:

Marshal Reporting Console
SQL Server and SSRS 2022

Question:

Can I install MRC with SQL 2022?
Can I upgrade the MRC SQL and SQL Reporting Services instances to SQL 2022?

Procedure:

MRC 2.6 cannot be directly installed with SSRS 2022. However it is possible to upgrade the standalone MRC instances to SQL 2022 and SSRS 2022.

This procedure assumes you have installed MRC using the bundled SQL Express 2016 Advanced installer, and tested operation.

This procedure can also be used for a new installation on Windows 2025 (SQL Express 2016 must be manually installed first - see the notes section below).

Install SQL 2016 Service Pack 3 for the MRC_SQLEXPRESS instance. A computer restart will be required after installation.
From the Start menu, open Reporting Services Configuration Manager.
- Note the Report Server Database Name (by default, ReportServer$MRC_SQLEXPRESS). If you have used custom credentials, note the settings.
- From the Encryption Keys page, back up the key to a file.
- Exit the Reporting Services Configuration Manager.
Install Microsoft SQL Server 2022 Reporting Services.
- Choose the free edition Express.
- On the Setup Complete screen, click Configure report server.
In the Report Server Configuration Manager:
- On the WebService URL page, click Apply to accept the default values.
- On the Database page, click Change Database. In the wizard,
  - Select Choose an existing report server database.
  - On the Database Server page, the Server Name is the local computer name with MRC_SQLEXPRESS. Do not choose "Encrypt".
  - On the Database page, select the database you noted in step 2.
  - On the Credentials page, if you have not used the default service credentials, enter the credentials you noted in step 2.
  - Complete the wizard, click Finish, and exit the wizard.
  - On the Encryption Keys page, restore the key from your backup. You will be asked for confirmation to remove other registered servers. Click OK to this question.
  - Exit the Reporting Services Configuration Manager.
Upgrade to SQL Server 2022 Express.
- On the Welcome screen, choose the Custom option.
- On the Installation Center screen, choose Upgrade.
- On the Select Instance screen, select MRC_SQLEXPRESS.
- On the Reporting Services Migration screen, check the box Uninstall Reporting Services.
- Complete the upgrade process.

Notes:

On Windows Server 2025 the MRC installer cannot be used to install SQL Express. However you can manually install SQL Express 2016 SP3 Advanced before installing MRC, and choose to use the existing installation.
- Do not select installation of "R Services"
- Remember to select "Mixed Mode" authentication.
- You must also enable TCP connections to the SQL instance, using SQL Configuration Manager.
In some cases (where a current release of MailMarshal Array Manager is installed on the same server), the installation of SQL 2022 may report an error on installation of MSOLEDBSQL.

You can safely ignore this error and continue. MailMarshal has already installed a compatible version of MSOLDDBSQL.
If the error appears in the rules check and you cannot continue:
- Stop the MailMarshal Array Manager.
- Uninstall the offending version of MSOLEDBSQL.
- Upgrade SQL
- Re-install the version of MSOLEDBSQL. All versions are available for download from Microsoft.
- Start the Array Manager.

Problem connecting to Report Server

Charles — Sun, 15 Mar 2026 20:00:10 GMT

This article applies to:

Marshal Reporting Console
Configuration of SSRS URL

Symptoms:

MRC Configuration Wizard attempting to connect to SQL Reporting Server
Setting the URL for SQL Server Reporting Services (SSRS)
Error message: Problem connecting to Report Server - The service might not be running or you might not have access to the URL

Causes:

Each of the following unrelated issues could raise this error message:

Website URL incorrectly entered, site stopped, or site requires login: Verify that the SQL Reporting Server website is running at the expected URL and does not require authentication.
Proxy Settings: System proxy settings for the logged on user on the MRC server may be forcing the connection through a proxy that requires authentication.
Secure Connections: SQL Server Reporting Services (SSRS) report server configuration may be configured to require secure connections. If SSL Certificates are available on the server, by default SSRS requires SSL (HTTPS connection). However, SSL is not supported by MRC.

Resolution:

To resolve the issues:

Proxy settings:

On the MRC server, edit system proxy settings (using the Network & Internet > Proxy Control panel).
Set direct access, or add the SQL Reporting Server (by name) to the exclusions.

Secure Connections:

Configure SSRS to allow HTTP connections.

Edit the RSReportServer.config file. The following key and value should be present:

<Add Key="SecureConnectionLevel" Value="0" />
If the value is not 0, change it to 0.
Save the file and then restart the SQL Server Reporting Services service for the instance.

Notes:

If your network enforces proxy settings through a domain policy or auto-configuration, you may need to exclude the MRC server from the policy.
If you need to edit RSReportServer.config, LevelBlue recommends that you use an XML editing program that validates the XML code. You can use XML Notepad (a free tool from Microsoft).
- Download XML Notepad
For more information about RSReportServer.config, see this Microsoft Technet entry.

Browser security settings affect Reporting Console function

Charles — Sun, 15 Mar 2026 19:57:58 GMT

This article applies to:

Marshal Reporting Console

Symptoms:

Error messages indicating scripting is not supported
Buttons or other page controls do not work

Causes:

Marshal Reporting Console uses active scripting (JavaScript) for browser-based controls
Internet Explorer (or whatever browser is in use) on the workstation is configured to disallow active scripting
Browsing from a Windows Server with IE Enhanced Security Configuration enabled can disable scripting

Resolution:

To ensure that you can use the Marshal Reporting Console website, set your browser to allow active scripting.

Browse from a workstation, not the server. By default Windows Server enables IE Enhanced Security Configuration, which can affect use of active scripting.
Ensure that the MRC site is in a security zone that allows active scripting, such as the default Local Intranet security zone.
By default, the Local Intranet zone consists of local domain names in addition to any domains that are specified to bypass the proxy server. For more information about configuring the Local Intranet zone, see the Microsoft document Setting Up Security Zones.

To set the security level for the Local Intranet zone:

On the Tools menu of Internet Explorer, select Security Options.
Click the Security tab.
Select Local intranet.
To apply the defaults, click Default Level.

Setting up automatic logon to MailMarshal Console or MRC

Charles — Sun, 15 Mar 2026 19:52:14 GMT

This article applies to:

MailMarshal Management Console (Windows Authentication)
Marshal Reporting Console

Question:

How can users be logged on automatically to Marshal websites?

Background:

When you set up Marshal user interfaces with Windows Authentication, you may want allowed Windows users to be logged on automatically using their Windows account. By default this should occur. However, in some cases users may be prompted to re-enter the information.

Procedure:

To ensure that users are logged in automatically (on Windows systems), configure security settings on each client system.

From the Windows Control Panel, select Internet Options.
Click the Security tab.
Select Local intranet.
Click Sites, and add the base URLs of the servers to the list of sites.
To apply the defaults permissions for the zone, click Default Level.
Alternatively, if you want to customize other settings, click Custom Level. Scroll to the end of the list of settings and select Automatic logon only in Intranet zone.
Click OK to apply the settings and exit the options window(s).
Chrome uses this setting by default.
For Edge, navigate to Settings > Profiles > Profile preferences and ensure the "Allow single Sign-on" switch is enabled.

Notes:

You can also deploy this setting to all users by configuring Windows group policy.
By default, the Local Intranet zone consists of local domain names in addition to any domains that are specified to bypass the proxy server.
You can also pass Windows credentials automatically to other zones. However, you should be aware of the security implications of passing this information over the Internet. Also, some proxy servers do not successfully pass this information.
For Firefox, add sites or domains to the about:config setting network.automatic-ntlm-auth.trusted-uris

Additions to Release Notes for Marshal Reporting Console 2.6

Charles — Wed, 04 Mar 2026 19:37:41 GMT

This article applies to:

Marshal Reporting Console 2.6

Question:

What are the Release Notes for Marshal Reporting Console 2.6?

Information:

The Release Notes included with Marshal Reporting Console 2.6 are accurate as of the date of publication. The latest release of Marshal Reporting Console is 2.6.0.1469, released September 13, 2018.

This article provides any additional information generated after that date.

Supported Operating Systems and SQL versions

MRC 2.6 can be installed on all Windows Server operating systems up to Server 2025.

The latest SQL Server version supported for installation remains at SQL 2016 with SSRS, or 2016 Express Advanced.
After installing MRC with SQL 2016 Express Advanced, you can upgrade to SQL 2022.
On Windows Server 2025, you must first install SQL Express Advanced 2016 SP3 using the installer available from Microsoft.
See LevelBlue Knowledgebase article Q21228.

MRC 2.6 cannot be installed on Windows 10 (contrary to any earlier statement). LevelBlue strongly advises against installing MRC on a workstation operating system due to resource allocation factors.

MRC 2.6 can be installed on Windows Server 2008 R2. However, the included SQL Express 2016 cannot be installed on Windows 2008 R2.

The minimum Operating System requirement for a new installation of MRC 2.6 with SQL Express 2016 is Windows Server 2012.
If you must perform a new installation of MRC 2.6 on Windows 2008 R2, pre-install and use SQL Express Advanced Edition 2014 or earlier.

How to use the Support Tool for SEG, ECM, WebMarshal or MRC

Charles Creegan — Mon, 13 Oct 2025 01:44:36 GMT

This article applies to:

MailMarshal (SEG)
MailMarshal ECM (MailMarshal Exchange)
WebMarshal
Marshal Reporting Console

Question:

How do I use the Support Tool?

Information:

The Marshal support tool has been developed to help the LevelBlue Technical Support team gather information about installed software and configuration. The tool produces a single .zip file that contains essential information to help the support team debug specific issues.

The tool can gather information about supported versions of the following products:

MailMarshal SEG (MailMarshal SMTP)
MailMarshal ECM (MailMarshal Exchange)
WebMarshal
Marshal Reporting Console
Marshal virus scanners (Bitdefender for Marshal, McAfee for Marshal, and Sophos for Marshal)
Web Components
IIS

Note: For the MailMarshal SPE (Service Provider Edition) Support Tool, see Q15019.

Installation

In most cases you will find a copy of the tool in the install folder of the base product (MailMarshal,ECM, or WebMarshal).

Otherwise, download the support tool from https://www.marshal.com/supporttool/download (right click, save as. You may see a security warning). The tool will also attempt to update itself automatically, as noted below.

The current version of the tool (1.14 and above) is packaged with .NET runtimes and does not have any software prerequisites.

Using the tool

Repeat the following steps on each server of interest, as directed by Technical Support.

If necessary, downloaad or copy the tool to the server.
Double click to run the tool.
- Note: On startup, the tool checks for updates to functionality. This feature requires access to the URL http://www.marshal.com/supporttool/download
- If the tool cannot connect, it raises a warning.
- If necessary, retrieve the latest version manually as described above.
The main window of the tool appears as shown below. The fields and selections differ depending on the installed software.
Select the items to include, as directed. Clear the selections for items you do not want to include. See below for explanations of each selection.
Choose an output directory.
Enter a support case number.
, Click GO to run the tool. The tool gathers data into a folder, and then creates a single compressed file.
- NOTE: This tool can require significant disk space, particularly if you include multiple dump files. In rare cases it could consume all available space. If not enough space is present, the tool raises a warning: Not enough free space available to package into zip file.
The status bar at the bottom of the window shows the progress. You can cancel the process if necessary.
When the tool is finished, click Close to exit.
Upload the file to LevelBlue as directed by Technical Support.
- Note: Wait for the tool to create the zip file. (The tool creates a temporary folder and then zips the content. Do not zip the folder manually - it will not contain all required items.)

The fields on the window are defined as follows:

Installed Components

Shows the related software that is installed on this computer. Select the components for which you want to include detailed information such as logs and configuration details.

Installation logs (if any) are gathered for all selected components regardless of other selections.

Items to gather

System Information

Includes a listing of the system hardware and operating system information.

Current process details

Includes a listing of processes running on the server.

Configuration details

Includes the XML or text files that define configuration of the selected software.

Marshal Registry

Includes a copy of the registry hive for all components that are present on the server.

Marshal install directory listings

Includes file and version information for files in the installation directories of all selected components.

For MailMarshal, optionally select Include Quarantine directory listing to list all messages in quarantine and archive (only if required, as the file will be much larger and take longer to generate)

Event logs

Includes Windows Event Log information. If you include the event logs, choose to include Application and/or System logs by checking the boxes.

Gather specific message

Attempts to include one or more mail message or Sent History files. Enter the first few characters of the message name (for example B89f00). This option is only available when running the tool on a MailMarshal processing node.

Log files

Includes the text log files generated by the selected components. By default the last 5 days of logs are included. Use the menus to select the range of dates to include.

Marshal Crash Dumps

Includes one or more types of diagnostic information. Shows the number of each type that are available.
Select the number of each type to include. The default is 1 of each available type. The most recent available are included.

Most recent Marshal crash dumps: Includes .mdmp files created by the selected components when recovering from an error.
Most recent WER crash dumps: Includes the Windows Error Reporting data from the recent issues.
Most recent potentially fatal messages: Includes email message files that are marked as suspect because they were being processed at the time of a crash.

Output

Output Directory: Enter the location where the compressed file should be created. The default location is the desktop. Click [...] to browse the local computer.
Support case number: Enter the case number as provided by Technical Support.

Version: The installed version of the Support tool.

Notes:

This tool simply gathers existing information from the system and logs.
- There is no need to restart any services before or after running the tool (unless specifically requested by Technical Support).
- The tool does not affect any running services and it does not require any downtime.
The tool runs as Administrator to ensure full access on servers where UAC is enabled.
Although this tool is able to gather information from MailMarshal SMTP/SEG and WebMarshal versions from version 6.0, many older versions are no longer supported. Technical Support may ask you to upgrade to a supported version as a first step to resolve any issues. For a list of supported versions of products, see LevelBlue Knowledgebase article Q10920.
The current version of the tool does not offer automatic upload. Support will provide instructions to upload to the LevelBlue Portal.

How to use the Support Tool for SEG, ECM, WebMarshal or MRC

Charles Creegan — Mon, 13 Oct 2025 01:44:36 GMT

This article applies to:

MailMarshal (SEG)
MailMarshal ECM (MailMarshal Exchange)
WebMarshal
Marshal Reporting Console

Question:

How do I use the Support Tool?

Information:

The tool can gather information about supported versions of the following products:

MailMarshal SEG (MailMarshal SMTP)
MailMarshal ECM (MailMarshal Exchange)
WebMarshal
Marshal Reporting Console
Marshal virus scanners (Bitdefender for Marshal, McAfee for Marshal, and Sophos for Marshal)
Web Components
IIS

Note: For the MailMarshal SPE (Service Provider Edition) Support Tool, see Q15019.

Installation

In most cases you will find a copy of the tool in the install folder of the base product (MailMarshal,ECM, or WebMarshal).

The current version of the tool (1.14 and above) is packaged with .NET runtimes and does not have any software prerequisites.

Using the tool

Repeat the following steps on each server of interest, as directed by Technical Support.

If necessary, downloaad or copy the tool to the server.
Double click to run the tool.
- Note: On startup, the tool checks for updates to functionality. This feature requires access to the URL http://www.marshal.com/supporttool/download
- If the tool cannot connect, it raises a warning.
- If necessary, retrieve the latest version manually as described above.
The main window of the tool appears as shown below. The fields and selections differ depending on the installed software.
Select the items to include, as directed. Clear the selections for items you do not want to include. See below for explanations of each selection.
Choose an output directory.
Enter a support case number.
, Click GO to run the tool. The tool gathers data into a folder, and then creates a single compressed file.
- NOTE: This tool can require significant disk space, particularly if you include multiple dump files. In rare cases it could consume all available space. If not enough space is present, the tool raises a warning: Not enough free space available to package into zip file.
The status bar at the bottom of the window shows the progress. You can cancel the process if necessary.
When the tool is finished, click Close to exit.
Upload the file to LevelBlue as directed by Technical Support.
- Note: Wait for the tool to create the zip file. (The tool creates a temporary folder and then zips the content. Do not zip the folder manually - it will not contain all required items.)

The fields on the window are defined as follows:

Installed Components

Shows the related software that is installed on this computer. Select the components for which you want to include detailed information such as logs and configuration details.

Installation logs (if any) are gathered for all selected components regardless of other selections.

Items to gather

System Information

Includes a listing of the system hardware and operating system information.

Current process details

Includes a listing of processes running on the server.

Configuration details

Includes the XML or text files that define configuration of the selected software.

Marshal Registry

Includes a copy of the registry hive for all components that are present on the server.

Marshal install directory listings

Includes file and version information for files in the installation directories of all selected components.

For MailMarshal, optionally select Include Quarantine directory listing to list all messages in quarantine and archive (only if required, as the file will be much larger and take longer to generate)

Event logs

Includes Windows Event Log information. If you include the event logs, choose to include Application and/or System logs by checking the boxes.

Gather specific message

Log files

Includes the text log files generated by the selected components. By default the last 5 days of logs are included. Use the menus to select the range of dates to include.

Marshal Crash Dumps

Most recent Marshal crash dumps: Includes .mdmp files created by the selected components when recovering from an error.
Most recent WER crash dumps: Includes the Windows Error Reporting data from the recent issues.
Most recent potentially fatal messages: Includes email message files that are marked as suspect because they were being processed at the time of a crash.

Output

Output Directory: Enter the location where the compressed file should be created. The default location is the desktop. Click [...] to browse the local computer.
Support case number: Enter the case number as provided by Technical Support.

Version: The installed version of the Support tool.

Notes:

This tool simply gathers existing information from the system and logs.
- There is no need to restart any services before or after running the tool (unless specifically requested by Technical Support).
- The tool does not affect any running services and it does not require any downtime.
The tool runs as Administrator to ensure full access on servers where UAC is enabled.
Although this tool is able to gather information from MailMarshal SMTP/SEG and WebMarshal versions from version 6.0, many older versions are no longer supported. Technical Support may ask you to upgrade to a supported version as a first step to resolve any issues. For a list of supported versions of products, see LevelBlue Knowledgebase article Q10920.
The current version of the tool does not offer automatic upload. Support will provide instructions to upload to the LevelBlue Portal.

What versions of Marshal Anti-Virus and reporting solutions are currently supported by LevelBlue Technical Support?

Charles — Sun, 26 Nov 2023 18:14:08 GMT

This article applies to:

Bitdefender for Marshal
Kaspersky for Marshal
McAfee for Marshal
Sophos for Marshal
Marshal Reporting Console

Question:

What versions of Anti-Virus for Marshal plug-ins are currently supported by LevelBlue Technical Support?
What versions of Marshal Reporting Console are currently supported by LevelBlue Technical Support?

Information:

The following tables show the currently supported versions, planned dates of termination of support, and support end dates for discontinued versions.

Note: In this article "supported" refers to full product support as defined in LevelBlue support policy for the Marshal Product Line.

For "discontinued" versions, LevelBlue can often provide advice to help customers resolve issues. However, LevelBlue may recommend upgrade to a later version of the software.

If a reported problem requires remedial development work, LevelBlue will usually provide a fix only for the latest product version.

Upgrades to the current versions of these products are always free of charge to customers with a current maintenance contract.

All versions earlier than those listed are discontinued.

Bitdefender for Marshal

Notes:

The URL for Bitdefender signature updates changed as of March, 2022. Only version 1.2.0 can access the new update URL.

Software Version

Release Date
Support Status
Discontinued Date

1.2.0.1680
(64 bit only)

August 3, 2021
Active

1.1.2.1623
(64 bit only)

August 22, 2019
Discontinued
March 20, 2022

1.1.1.1564

November 9, 2017
Discontinued
March 20, 2022

Kaspersky for Marshal

END OF LIFE November 22, 2023: Kaspersky for Marshal is no longer sold or supported. The embedded license key has expired. This plugin cannot be initialized. Attempting to use it will cause the MailMarshal or WebMarshal product engines to stop.
Note that Sophos for Marshal is included in all subscriptions for MailMarshal and WebMarshal. For customers who desire a second virus scanner, the recommended option going forward is Bitdefender for Marshal.
- Customers with contracts for Kaspersky for Marshal extending beyond November are entitled to use Bitdefender for Marshal for the balance of the contract term. Contact your sales representative for assistance

McAfee for Marshal

Software Version

Release Date
Support Status
Discontinued Date

6.1.2.1564

November 9, 2017
Active

Note: New McAfee Engine updates will not be provided for 32 bit versions (except to support ECM). Customers MUST use a 64 bit version of MailMarshal or WebMarshal to receive the latest Engine versions that have continuing support from McAfee.

Sophos for Marshal

Software Version

Release Date
Support Status
Discontinued Date

1.1.5.1710
(64 bit only)

March 15, 2022
Active

1.1.4.1679
(64 bit only)

August 3, 2021
Discontinued
September 1, 2022

1.1.3.1637
(64 bit only)

November 3, 2020
Discontinued
September 1, 2022

1.1.2.1564

November 9, 2017
Discontinued
March 22, 2022

Note: Release 1.1.5 includes significant updates for stability and performance. Customers are very strongly urged to upgrade.

Marshal Reporting Console

(previously known as MailMarshal Reporting Console)

Software Version

Release Date
Support Status
Discontinued Date

2.6.0.1469

September 13, 2018
Active

2.5.4.1263

December 5, 2013
Discontinued
September 1, 2022

Note:

Counterspy for Marshal and PestPatrol for Marshal have been discontinued. Signature updates for these scanners are no longer available.

What versions of Marshal Security products are currently supported by LevelBlue Technical Support?

Charles Creegan — Sun, 26 Nov 2023 18:02:27 GMT

This article applies to:

MailMarshal (SEG)
MailMarshal ECM/MailMarshal Exchange
MailMarshal SPE
MailMarshal SES
Marshal Reporting Console
WebMarshal
Bitdefender for Marshal
McAfee for Marshal
Sophos for Marshal
Other Products
- MailMarshal Appliance e10000
- MailMarshal Management Pack for MOM
- MailMarshal Management Pack for SCOM
- Marshal EndPoint Security
- Security Reporting Center
- Firewall Suite
- imMarshal for MSN
- Counterspy for Marshal
- Kaspersky for Marshal
- PestPatrol for Marshal

Question:

What versions of Content Security (Marshal) products are currently supported by LevelBlue Technical Support?

Information:

For full details about supported versions of current products, see the articles linked below:

Premises Email Security

Article Q20961 covers the following products:
- MailMarshal (SEG)
- MailMarshal ECM/MailMarshal Exchange
- Secure Email Server (SES)

Web Content Security

Article Q20962 covers WebMarshal.

Service Provider Email Security

Article Q20963 covers MailMarshal SPE.

Anti-Virus and Reporting

Article Q20964 covers the following products:
- Bitdefender for Marshal
- McAfee for Marshal
- Sophos for Marshal
- Marshal Reporting Console

Deprecated and Discontinued Products

e10000 (MailMarshal Node Appliance): End of support: March 31, 2011
EndPoint Security: End of support: May 1, 2013
MailMarshal Management Pack for MOM: End of support: May 1, 2013
MailMarshal Management Pack for SCOM: End of support: May 1, 2013
Security Reporting Center (Windows Version): End of support: December 31, 2009
Security Reporting Center (Solaris Version): Withdrawn
Firewall Suite: Withdrawn
imMarshal for MSN: Withdrawn
Counterspy for Marshal: End of support: January 1, 2014
Kaspersky for Marshal: End of support: November 22, 2023
PestPatrol for Marshal: End of support: January 1, 2014

This article was previously published as:: NETIQKB33882

Best practices to secure product related websites

Charles — Tue, 28 Feb 2023 21:47:03 GMT

This article applies to:

MailMarshal (SEG)
MailMarshal ECM/MailMarshal Exchange
SEG Service Provider Edition/MailMarshal SPE
Marshal Reporting Console
All web sites created by the products

Question:

What are the recommended practices for secure (HTTPS) access to product websites?

Information:

LevelBlue recommends that SSLv2 and SSLv3 should be disabled on all web servers that provide service for the named products (such as SQM/End user spam and quarantine management, remote consoles, and reporting consoles), if the sites are secured with HTTPS. These protocol versions are older and have known vulnerabilities. For example, CVE-2014-3566 ("Poodle") is a vulnerability in the SSLv3 protocol that potentially allows an attacker to view the plain text of encrypted material.

Some regulatory frameworks and companies are recommending and even requiring that TLSv1.0 and TLSv1.1 be disabled as well.

Notes:

For technical details of how to disable SSLv2 and SSLv3 on Windows servers, refer to Microsoft documentation.

See Microsoft Knowledge Base article 245030.
A more detailed explanation can be found in this TechNet blog post.
A free third party tool that might be of use to simplify the process, for any version of TLS/SSL, is IISCrypto from Nartac Software.

Implementation is not part of the Windows Platform FIPS validated cryptographic algorithms

Charles — Tue, 25 Oct 2022 23:45:05 GMT

This article applies to:

Marshal Reporting Console 2.6
SQL Server Reporting Services (SSRS)
FIPS-compliant algorithms

Symptoms:

Installing MRC or running scheduled reports
GUI warning or event log entry: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms

Causes:

Where SQL Server SSRS is run in FIPS-compliant mode, there is a known issue with cryptography selections. The MD5 algorithm may be used, and it is not FIPS-compliant.

Resolution:

To resolve this issue, modify the web.config file for the SSRS instance.

Locate the web.config file, by default in <system-drive>\Program Files\Microsoft SQL Server\MSRS<version>.<instance>\Reporting Services\ReportManager\
Make a backup copy of the file.
In the system.web section add the following line:
<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
Make the same change to the web.config file for the ReportServer, by default in <system-drive>\Program Files\Microsoft SQL Server\MSRS<version>.<instance>\Reporting Services\ReportServer\
Restart the SQL SSRS instance.

Notes:

For more information see the related links below.

Some services do not start in a timely fashion

SPE Team — Mon, 04 May 2020 22:04:25 GMT

This article applies to:

Marshal Reporting Console
MailMarshal SPE 3.0 and above

Symptoms:

MailMarshal SPE Agent services do not start
MRC Executor or Scheduler services do not start
Service logs do not contain any entries
Error dialog text: 1053 - service did not start in a timely fashion
Log entries similar to the following in the installation log:

15:01:30 Checking if Service Exists: SPEStatusAgent
15:02:01 Failed to start service (1): The service did not respond to the start or control request in a timely fashion.

Causes:

The services executables are authenticode signed. The signing certificate is validated on startup.

This process requires access to a Certificate Revocation List (generally via HTTP), but the servers affected do not have access to this URL.
This is a known issue affecting .NET services, when strict security is enforced in a domain.

Other critical Windows services have not yet started

Resolution:

For the CRL problem, several options are available to resolve this issue. Options are listed below in order from most to least secure.

Allow access from the server(s) to the CRL (crl.verisign.com or crl.trustwave.com depending on product version)
- This is the most secure option, because any applications that do CRL checking will properly validate their certificate.
Create a configuration file to disable CRL checking for the affected Agents. For information, see Microsoft Knowledge Base article .NET configuration information for the generatePublisherEvidence element.

Locate the .config file for each service
Within the Configuration section, BELOW the end of the "configSections" section, add the following lines:
<runtime>
<generatepublisherevidence enabled="false">
</generatepublisherevidence>
</runtime>

Increase the service startup timeout and/or decrease the timeout on the CRL checking.
- The service will start, after the timeouts elapse. The CRL check timeout can be up to 60 seconds, and the default service startup timeout is 30 seconds.
- For information about changing these timeouts (ServicesPipeTimeout), see this Microsoft article.

For other cases where CRL access has been confirmed

Change the service startup type to "Automatic (Delayed Start)"

MailMarshal (SEG/ECM), WebMarshal, and Latest Windows or SQL Versions

Charles Creegan — Fri, 01 May 2020 00:00:00 GMT

This article applies to:

MailMarshal (SEG)
MailMarshal SEG Service Provider Edition
MailMarshal ECM/MailMarshal Exchange
WebMarshal
Marshal Reporting Console
Microsoft Windows
Microsoft SQL Server

Question:

Will MailMarshal SEG, ECM, or WebMarshal work with a new Windows version?
Will MailMarshal SEG, ECM, or WebMarshal work with a new Windows service pack?
Will MailMarshal SEG, ECM, WebMarshal, or Marshal Reporting Console work with a new SQL Server service pack?

Information:

Windows versions:

LevelBlue tests each SEG, ECM, and WebMarshal release with specific Windows versions.

The product installer will notify you if you are installing the product on a Windows version that has not yet been tested (this feature is present in current supported versions).

For the latest list of tested Windows versions, see the following LevelBlue Knowledgebase articles:

Q11358 (MailMarshal SEG, WebMarshal, Marshal Reporting Console)
Q11588 (MailMarshal SEG Service Provider Edition)
Q14131 (MailMarshal ECM)

LevelBlue recommends that any production installation of these products should be on a fully tested version of Windows.

SQL Server:

LevelBlue tests software with specific versions of Microsoft SQL Server. SQL commands and features can change between version releases. Use only the tested versions.

If a minimum Service Pack is specified for SQL, be sure you have applied at least the minimum Service Pack.

Service Packs and Windows Updates:

Historically, core functionality of the products listed has rarely, if ever, been affected by Service Pack or Microsoft Update changes to Windows or SQL Server. However, LevelBlue cannot guarantee future performance.

If product functionality is affected by Service Packs or Microsoft Updates, LevelBlue will work with customers to restore functionality. If a full resolution requires product development, it might not be available immediately.

Known Issues:

This article will be updated with information about any known issues with specific new versions of Windows.

Windows 11: Validated for all components with current versions of SEG and WebMarshal.
- Note that LevelBlue recommends use of a server operating system for email/web processing, Array Manager, and SEG web components.
Windows Server 2025: Tested and supported with the latest releases of SEG and WebMarshal.
Windows Server 2022: Tested and supported with the latest releases of SEG and WebMarshal.
Windows Server 2019: Tested and supported with the latest releases of SEG and WebMarshal.
Windows Server 2016: Tested and supported with the latest releases of the named products.
SQL 2017: Validated with the latest releases of SEG and WebMarshal.
SQL 2016: Validated with the latest releases of SEG, ECM, and WebMarshal.
SQL 2014: Validated with the latest releases of SEG, ECM, and WebMarshal.

Marshal Reporting Console and SQL: The latest edition of SQL Server that was fully validated with MRC is SQL 2016. Basic testing has been accomplished with SQL 2022. For information about how to use this SQL version, see article Q21228.
- Supported SQL versions require MRC 2.6.
- Note that current versions of SQL Server may require a current Windows version.

How do I schedule or automate MailMarshal or WebMarshal reports?

Charles Creegan — Fri, 01 May 2020 00:00:00 GMT

This article applies to:

MailMarshal ECM/MailMarshal Exchange
MailMarshal (SEG)
WebMarshal

Question:

How do I schedule or automate MailMarshal or WebMarshal reports?

Procedure:

SEG/MailMarshal SMTP, ECM/MailMarshal Exchange, and WebMarshal reports can be scheduled through the Marshal Reporting Console. Marshal Reporting Console is a web-based application that provides scheduled delivery by email, FTP, or file share.

It supports current versions of SEG, ECM, and WebMarshal:

This application is installed separately. It is freely available.

Full instructions for scheduling are included in the MRC Help.

To download the installer package and installation instructions, see the MRC Download page.

Notes:

The MailMarshal and WebMarshal Reports applications (provided with old and unsupported versions in the MailMarshal web package) do not provide scheduling.

This article was previously published as:: NETIQKB34806

Supported Releases Policy for the Marshal Product Line

Charles Creegan — Fri, 01 May 2020 00:00:00 GMT

This article applies to:

MailMarshal Secure Email Gateway (SEG)
WebMarshal
MailMarshal ECM (MailMarshal Exchange)
MailMarshal Service Provider Edition
Virus Scanner plug-ins
Marshal Reporting Console

Question:

What is the supported releases policy for SEG, ECM, WebMarshal, and virus scanner plug-ins?
What is the policy on End of Support for the LevelBlue Marshal Product Line?

Information:

Definitions:

Major release: A release containing many new features or a change in architecture (for example, SEG 8.0).
Feature release: A release containing some new features and enhancements (for example, SEG 8.1.0).
Point release: A release containing maintenance updates and small enhancements to existing features (for example, SEG 8.1.3).
Supported: Full product support as defined in LevelBlue support policy for the Marshal Product Line.
- For "discontinued" versions, LevelBlue can often provide advice to help customers resolve issues. However, LevelBlue may recommend upgrade to a later version of the software.
- Upgrades to the current versions of these products are always free of charge to customers with a current maintenance contract.

Policy:

LevelBlue will support each product release for two years, or until the release of the second following feature release, whichever is shorter.

For the current feature release, normally all point releases are supported.
For a previous feature release, only the last point release is supported.
When a major release is issued, LevelBlue may support the last two feature releases of the previous major release for an extended period.

LevelBlue will publish the dates of end of support of each release at least two months in advance of the effective date. For lists of supported versions and end of support, see the related articles linked below.

Hotfixes:

If a customer encounters an issue with a point release that is older than the latest point release for that version, they will be required to upgrade to the latest point release before a hotfix is issued.

Examples:

With the release of WebMarshal 6.12.3:

LevelBlue will continue to support 6.12.1 and 6.11.2.
LevelBlue will announce end of support for 6.11.1.

With the release of WebMarshal 7.0.0:

LevelBlue will continue to support WebMarshal 6.11.2 as well as 6.12.3 until further notice.
LevelBlue will announce end of support for 6.12.1 and 6.12.2.

Notes:

Customers should plan for a yearly upgrade cycle to take advantage of new features and to ensure their software is supported.

Report navigation bar shows "page 0 of 0"

Charles Creegan — Fri, 01 May 2020 00:00:00 GMT

This article applies to:

Marshal Reporting Console 2.5

Symptoms:

When a report is first opened, the navigation bar may be disabled and show "page 0 of 0"
The problem is intermittent, but more likely to occur with large reports

Causes:

This problem is internal to the Microsoft Report Viewer. Microsoft has acknowledged this issue and stated that a fix will be included in new versions of Report Viewer.

Workaround:

To enable the navigation, refresh the report (F5) or close and re-open the report.

Resolution:

Upgrade to MRC 2.6. This version includes a new Report Viewer.

Report Viewer printing function fails

Charles Creegan — Fri, 01 May 2020 00:00:00 GMT

This article applies to:

Marshal Reporting Console 2.5
Report Viewer - printing functionality

Symptoms:

Attempting to print a report from the Report Viewer webpage
Error: Unable to load print control.

Causes:

Microsoft Cumulative security update for ActiveX (Security Bulletin MS08-052) disabled the ActiveX component used by the printing function in the Report Viewer.

Resolution:

LevelBlue recommends upgrade to MRC 2.6. This version includes updated report viewing. You may need to install a new version of SQL Express to support this installation.

To resolve this issue with earlier SQL versions, install the latest SQL Server service pack such as SQL 2005 Service Pack 2, and the updated Report Viewer redistributable package, on the Marshal Reporting Console server.

For more information and links to the fixes, see Security Bulletin MS08-052.

Cannot set impersonate user when installing MRC

Charles Creegan — Fri, 01 May 2020 00:00:00 GMT

This article applies to:

Marshal Reporting Console 2.5.x

Question:

Error: Marshal Reporting Console - Cannot set impersonate user
Why does my Domain Administrator User account not have sufficient rights to "Impersonate User" ?
Impersonate user cannot be entered on non-English Windows version

Resolution:

If you encounter this error, add the Domain Administrator User account directly to the local Administrators group on the server.

Language-specific Windows issues

If the Windows operating system version is not English, then the built-in Local Administrators group may have a different name (for instance in Spanish language Windows the group is named "Administradores").

This problem is fixed in MRC 2.6. However, you may find that access to the MRC website by these users is not allowed.
In earlier versions, to work around this problem, create a local group called "Administrators." Add the user account to both the "Administrators" group and the existing built-in Local Administrators group (such as "Administradores").

Note:

You cannot correct this problem by adding a Domain Administrators group to the Local Administrators Group. You must add the individual user.

Additional configuration to install Web Components on Windows Server 64 bit editions (including Exchange Server)

Charles Creegan — Fri, 01 May 2020 00:00:00 GMT

This article applies to:

MailMarshal (SEG) Web Components
MailMarshal ECM/MailMarshal Exchange 7.X Web Components
MailMarshal (SEG) 10.0 and above Array Manager/Management Console
Marshal Reporting Console
Microsoft SBS 2008 or 2011 (deprecated)
Microsoft Windows 2008, 64 bit editions (deprecated)
Microsoft Windows 2008 R2 and above
WSUS
- For WSUS, see also Q14353

Question:

What steps are required to install SEG Web Components on Microsoft SBS Servers?
- Note that SBS is no longer supported by Microsoft
What steps are required to install the Web Components on Windows Server 64 bit editions?
What steps are required to install the Marshal Reporting Console on Windows Server 64 bit editions?
What steps are required to install MailMarshal (SEG) 10.0 and above (Array Manager or standalone) on a Microsoft Exchange Server?
Event log error message: The Module DLL C:\Windows\system32\RpcProxy\RpcProxy.dll failed to load. The data is the error.
Error message: Could not load file or assembly 'MMInterfaceVB' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Error message: The Module DLL 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 processor architecture. The data field contains the error number.
Error message: HTTP Error 500.19 (Module: DynamicCompressionModule)

Procedure:

On supported 64 bit editions of Windows Server where certain Microsoft web components are running, additional steps are required after installation of MailMarshal (SEG) 10.0 and above Management Console, MailMarshal Web Components or Marshal Reporting Console websites. These steps ensure that the LevelBlue sites can co-exist with other applications.

Warnings:

Back up files before making changes.
Ensure that XML is correctly written. For general information about XML editing, see article Q12705.
Note that some lines below are wrapped for readability.
Note that if you edit the lines referring to the "exppw" or "cafe_exppw" module, you MUST change all of these lines. If you do not, browsing to any page will fail with HTTP error 500.
If you install service packs for Microsoft software (particularly Exchange/Outlook Web Access), re-check the entries in applicationhost.config. Service packs can overwrite changes to this file.
Depending on the software or Windows components installed, some of the below items may not apply.

To enable Web Components or Marshal Reporting Console:

Run the following command with elevated privileges (note, the below line is wrapped for clarity but should be entered as a single line):
%windir%\system32\inetsrv\appcmd.exe set config
-section:system.webServer/httpCompression /-[name='xpress']

This command disables a compression module which is used by some Microsoft software. The module may not be installed on all servers.
Open a text editor or XML editor with elevated privileges (for instance, from the Start menu right-click Notepad and select Run as Administrator).

In the file %windir%\system32\inetsrv\config\applicationhost.config:
- change the line
  <add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" />
  
  to the following
  <add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll"
  preCondition="bitness64" />
- Note that the "image" part of the entries will depend on your local installation and you should not change it
If Outlook Web Access is installed on the server, perform the following additional steps.
- Note that the "image" part of the entries will depend on your local installation and version, and you should not change it.
- Not all of these entries are present in every installation. You can ignore any entries that are not present.
In the file %windir%\system32\inetsrv\config\applicationhost.config:
- change the line
  <filter name="Exchange OWA Cookie Authentication ISAPI Filter"
  path="C:\Exchange\ClientAccess\owa\auth\owaauth.dll" enabled="true" />
  
  to the following
  <filter name="Exchange OWA Cookie Authentication ISAPI Filter"
  path="C:\Exchange\ClientAccess\owa\auth\owaauth.dll" enabled="true"
  preCondition="bitness64" />
- change the line
  <filter name="Exchange ActiveSync ISAPI Filter"
  path="C:\Exchange\ClientAccess\sync\bin\AirFilter.dll" enabled="true" />
  
  to the following
  <filter name="Exchange ActiveSync ISAPI Filter"
  path="C:\Exchange\ClientAccess\sync\bin\AirFilter.dll" enabled="true"
  preCondition="bitness64" />
- change the line
  <add name="exppw"
  image="C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll" />
  
  to the following
  <add name="exppw"
  image="C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll"
  preCondition="bitness64" />
- change the line
  <add name="cafe_exppw"
  image="C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\bin\exppw.dll" />
  
  to the following
  <add name="cafe_exppw"
  image="C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\bin\exppw.dll"
  preCondition="bitness64" />
- change the line
  <add name="kerbauth"
  image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll" />
  
  to the following
  <add name="kerbauth"
  image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll"
  preCondition="bitness64" />
- change the line
  <add name="exppw" />
  
  to the following
  <add name="exppw" preCondition="bitness64" />
If you do not want to require HTTPS (SSL), you may need to use IIS manager to disable this requirement for specific virtual websites or directories.
With the MailMarshal (SEG) 10.0 and above Management Console, the default HTTPS binding conflicts with Exchange Server websites. Change the HTTPS binding of the SEG Management Console site.

You may need to recycle application pools and/or restart IIS in order to apply these changes.

Software Version	Release Date	Support Status	Discontinued Date
1.2.0.1680 (64 bit only)	August 3, 2021	Active
1.1.2.1623 (64 bit only)	August 22, 2019	Discontinued	March 20, 2022
1.1.1.1564	November 9, 2017	Discontinued	March 20, 2022

LevelBlue Knowledge Base » Knowledgebase » Marshal Reporting Console

Enabling Strong TLS for .NET

This article applies to:

Question:

Procedure:

Notes:

Supported Operating Systems and Prerequisite Versions

This article applies to:

Question:

Information:

Key:

Operating Systems and Prerequisites

Server Operating Systems

Workstation Operating Systems(for server installation)

Prerequisites

SQL Server Versions

Notes on MRC Installation

Supported Operating Systems and Prerequisite Versions

This article applies to:

Question:

Information:

Key:

Operating Systems and Prerequisites

Server Operating Systems

Workstation Operating Systems(for server installation)

Prerequisites

SQL Server Versions

Notes on MRC Installation

Supported Operating Systems and Prerequisite Versions

This article applies to:

Question:

Information:

Key:

Operating Systems and Prerequisites

Server Operating Systems

Workstation Operating Systems(for server installation)

Prerequisites

SQL Server Versions

Notes on MRC Installation

Upgrading SQL Reporting Services to SQL 2022

This article applies to:

Question:

Procedure:

Notes:

Upgrading SQL Reporting Services to SQL 2022

This article applies to:

Question:

Procedure:

Notes:

Upgrading SQL Reporting Services to SQL 2022

This article applies to:

Question:

Procedure:

Notes:

Problem connecting to Report Server

This article applies to:

Symptoms:

Causes:

Resolution:

Proxy settings:

Secure Connections:

Notes:

Browser security settings affect Reporting Console function

This article applies to:

Symptoms:

Causes:

Resolution:

Setting up automatic logon to MailMarshal Console or MRC

This article applies to:

Question:

Background:

Procedure:

Notes:

Additions to Release Notes for Marshal Reporting Console 2.6

This article applies to:

Question:

Information:

Supported Operating Systems and SQL versions

How to use the Support Tool for SEG, ECM, WebMarshal or MRC

This article applies to:

Workstation Operating Systems
(for server installation)

Workstation Operating Systems
(for server installation)

Workstation Operating Systems
(for server installation)