CodeTwo Base.title

Diagnosing CodeTwo Exchange Rules family software (older versions)


CodeTwo assistance is required with your CodeTwo Exchange Rules family software problems or advanced configuration.


Follow the steps below to collect all diagnostics:

This Knowledge Base article is designed to use with some older versions of CodeTwo software. If you are using version newer than the ones listed in the Applies to section (see the right pane) please refer to this article.

  1. First of all, take screenshots if you see error messages or anything unusual on the screen. Please make sure the error message is complete and readable - try expanding the error window so we can see the whole message on the screenshot or copy-paste the error message text.
  2. Unless you cannot access the program or your Transport Service does not work, please go to the program's main menu to turn on detailed logging. See the appropriate knowledge base article on how to do this:
  3. Perform rules execution test:
    1. Send a test message with a distinctive subject, for example "C2TEST no.1".
    2. Export the message: after sending, retrieve an email on a computer with MS Outlook, drag and drop email on your desktop, it will be saved as a .msg file. It may also be helpful if you provide the .msg copy from Sent Items folder of the sender.
    3. Repeat this procedure for every tested device/user/rule which does not work properly (remember about changing the number in the subject of test messages).
    4. Please also send one email from an account that works properly so we can compare the messages.
  4. Export your Event Viewer logs: we need System and Application branches logs in .evtx format compressed to .zip files.

Fig. 1. Exporting events from Event Viewer.

  1. Gather CodeTwo software diagnostics:
    1. Log in using your Domain Admin account directly to the Exchange Server where you have our software installed.
    2. Download the script from here and decompress it to the folder of your choice. You can review the content of the script by opening it in PowerShell ISE or any text editor such as Notepad.
    3. Go to the ems Exchange Management Shell. Navigate to the folder in which you have the diagnostic script saved and execute the script with the command .\CodeTwoDiagnostics.ps1
    4. If you get an error that the script is not digitally signed please modify your script execution policy as per this MS knowledge base article (usually RemoteSigned permissions suffice).
    5. If for any reason you cannot run our diagnostic script follow these additional steps.
  2. Compress all files (screenshots, log files, settings, .msg examples) into a single .zip file.

    If the total size of all attachments compressed is bigger than 15MB please consult this article on delivering big files to CodeTwo.

  3. Send all the above requested files and the problem description to CodeTwo.

    If you have a case open with us already, it is very important to state your case number in the subject line.

Our Clients:
UPS Israel
Oford University
Mitsubishi Motors
Toshiba TEC UK Imaging Systems Ltd
Illinois Institute of Technology
MAN Diesel
McDonalds India
Skoda Auto
Bank of Israel
China Mobile
Samsung SDI
Toyota Tsusho
Federação Portuguesa de Futebol
Credit Agricole
Toyota Boshoku
Oriflame Romania

Partners, certificates & awards