• Rss
  • LinkedIn
  • Youtube
  • Twitter
  • Instagram
  • English English English en
  • Deutsch Deutsch German de
Sales: +49 5251 304-800 | Support: +49 5251 304-636
NoSpamProxy
  • HOME
  • PRODUCT
    • NoSpamProxy Cloud
    • NoSpamProxy Protection
    • NoSpamProxy Encryption
    • NoSpamProxy Large Files
    • NoSpamProxy Disclaimer
  • SUPPORT
    • Knowledge Base
    • Forum
    • Training courses
    • Support Request
    • Software-Download
    • Resources
  • PARTNERS
    • Finding Resellers
    • Becoming Reseller
    • Partner Portal
  • COMPANY
    • Team
    • Testimonials
    • Career
    • Contact
  • EVENTS
    • Events
    • Webcast Training
  • BLOG
  • FREE TRIAL VERSION
    • Price request
    • Free trial version
  • English
    • Deutsch
  • Search
  • Menu Menu
info icon

The Exchange 2010 Management Console no longer starts after the mail gateway has been installed.

Known errors 9.2-11.1
< zurück
Zuletzt aktualisiert am:21.10.2022

Important: Since NoSpamProxy requires Framework 4.6.2, the workaround described below no longer works because Exchange 2010 is not compatible with Framework 4.6.2 (https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/supportability-matrix?redirectedfrom=MSDN&view=exchserver-2019).

If NoSpamProxy version 7.7 or later and Exchange 2010 are installed on the same server, the Exchange Management Console no longer works properly. The reason for this is the .NET Framework 4.0. The Exchange Management Console requires the Framework version 2.0 as the default handler, while the NoSpamProxy Management Console only works with version 4.0. To use the correct .NET Framework version by default, the NoSPamProxy setup 7.7 creates an environment variable called “COMPLUS_ApplicationMigrationRuntimeActivationConfigPath”.

This variable refers to a path where a config file with the appropriate settings is stored. When any MMC is called, the corresponding variable, and thus the configuration file, is used. This causes the known problems when opening the Exchange MMC. To be able to use the Exchange MMC again, there is only the following workaround:

The environment variable is permanently deleted and the NoSpamProxy MMC must be called via a batch file in which the corresponding environment variable is defined beforehand. The advantage is that in this case the environment variable is only used for programs that are called from the context of the batch file.

To work around the problem, do the following:

First, open Windows Explorer.

Right-click Computer and select Properties.

In this window, click Advanced System Settings. The following window opens:

Click “Environment Variables” here.

Managment Konsole Umgebungsvariablen setzen

In the “Environment Variables” window, select “COMPLUS_ApplicationMigrationRuntimeActivationConfigPath” in the “System Variables” section and then click “Edit”. Copy the path in the “Value” field to the clipboard. Then delete the complete entry. Click on OK, Apply and again on OK.

Now open Notepad. Paste the currently copied path from the clipboard into Notepad. In addition, add the following lines:

set COMPLUS_ApplicationMigrationRuntimeActivationConfigPath=
mmc.exe "C:\Program Files\Net at Work Mail Gateway\NoSpamProxy Management Console\Net at Work Mail Gateway Configuration Console.msc"

Copy the path from the clipboard behind the first line. The Notepad file should then be structured as follows:

set COMPLUS_ApplicationMigrationRuntimeActivationConfigPath=C:\ProgramData\ComPlus Activation Configurations\
mmc.exe "C:\Program Files\Net at Work Mail Gateway\NoSpamProxy Management Console\Net at Work Mail Gateway Configuration Console.msc"

Please note that the file names of the console may differ depending on the version used. Make sure to find the .msc file in the target directory.

Also, please note that the display of the batch file in this article may be distorted by automatic line breaks.

Finally, adjust the path to the Net at Work Mail Gateway Configuration Console.msc if necessary and save the Notepad content as NoSpamProxy-MMC.bat. If you call the BATCH file, the NoSpamProxy MMC should open successfully. Starting with Windows 2008 with UAC enabled, however, you must always run the batch file as administrator. The Exchange MMC should now also open without errors.

Tags:
  • 9.2-11.1
04.12.2018/by Stefan Feist

SEARCH

PRODUCT

  • All Topics
  • NoSpamProxy Cloud
  • NoSpamProxy Protection
  • NoSpamProxy Encryption
  • NospamProxy Large Files

Knowledge Base

Knowledge Base

Note: The information in this knowledge base is only relevant for NoSpamProxy up to version 13.2. All information for NoSpamProxy 14 and higher can be found in the online documentation.

CATEGORY

  • All Topics
  • News
  • Product
  • Tech & Support
  • Events
Subscribeto RSS Feed

NoSpamProxy

  • NoSpamProxy Cloud
  • NoSpamProxy Encryption
  • NoSpamProxy Large Files
  • NoSpamProxy Disclaimer
  • Price request
  • Team
  • Career
  • General terms and conditions
  • Data Protection Information for Business Partners and Applicants
  • Cybersecurity (PSIRT)

Partners

  • Becoming a reseller
  • Partners
  • Order Certificates
  • Newsletter

Categories

  • All topics
  • News
  • Support
  • Updates
  • Order certificates

Latest News

  • Info IconCritical Outlook vulnerability: No threat to NoSpamProxy customers24.03.2023 - 15:09
  • Default filter settings in NoSpamProxy 1422.03.2023 - 10:00
  • NoSpamProxy UpdateGlobal Rollout NoSpamProxy Version 14.0.515.03.2023 - 15:20
IMPRINT • EULA • Privacy Policy • © 2023 Net at Work GmbH
  • Rss
  • LinkedIn
  • Youtube
  • Twitter
  • Instagram
Reply links are not being inserted into emailsinfo iconinfo iconIntegration of the Web Portal requires a user account
Scroll to top