Frequently asked questions

...

MSI Installer on Windows refuses to install MessageHandler

Execute the MSI installation from the command line. This way the installation process produces a logfile, which may (on may not) contain valuable information. 

msiexec /i "C:\MessageHandler.msi" /L*V "C:\MessageHandler_Installer.log"

To diagnose the problem, inspect the file c:\Program Files (x86)\Open eGov MessageHandler\log\message-handler.log , while the MSI Installer still displays this error dialog:

Image Added

Note, that MessageHandler refuses to install, if you specify directories in the installations wizard,

• which do not exist! 
  Inspect the installation logfile and search for error messages like 

  No Format
  MSI (c) (7C:54) [14:32:12:501]: Note: 1: 1314 2: /Program Files/Sedexclient/interface MSI (c) (7C:54) [14:32:15:251]: Product: Open eGov MessageHandler -- Error 1314. The specified path '/Program Files/Sedexclient/interface' is unavailable.

  
  

• to which the chosen Service User Account does not have sufficient access rights. In this case the MH service will refuse to start in the installation process and the installation fails.
  To diagnose this situation, inspect the file c:\Program Files (x86)\Open eGov MessageHandler\log\message-handler.log , while the MSI Installer still displays this error dialog:
  Image Removed
  

Alternatively: Execute the MSI installation from the command line. This way the installation process produces a logfile, which may (on may not) contain valuable information. 

msiexec /i "C:\MessageHandler.msi" /L*V "C:\MessageHandler_Installer.log"

MSI Installer fails to uninstall MessageHandler

...

• Installieren Sie pro gewünschte MessageHandler Instanz einen sedex Client. Die Installation und Konfiguration mehrerer sedex Clients ist hier nicht beschrieben. Fahren Sie erst weiter, wenn jede der sedex Client Instanzen korrekt funktioniert.
• Sie brauchen pro MessageHandler Instanz ein separates Installationsverzeichnis (z.B. c:\mh-SEDEXID, wo SEDEXID die sedex ID des entsprechenden eSchKG Teilnehmers ist) und separate Arbeitsverzeichnisse.
• Passen Sie die Variablen wrapper.ntservice.name, wrapper.ntservice.displayname, wrapper.ntservice.description in der Datei conf/wrapper.conf jeder Instanz entsprechend Ihren Bedürfnissen an.
• Passen Sie den Port der Webservice Schnittstelle von Messagehandler in jeder Instanz an (Attribut /config/messageHandler/webserviceInterface/@port in der Datei conf/config.xml). Jede Instanz braucht einen eigenen Port, sonst kann der Messagehandler den Webservice nicht starten..

How to upgrade a MH installation on Windows

If you installed MH using the MSI installer, be aware, that the installer always performs a completely new installation. It is not conceive to perform an upgrade! So back-up your MH configuration before installing the new version.

To upgrade:

• Stop the MH service.
• Backup at least the directories listed below. Recommended: backup the whole server before proceeding.
• Uninstall the older version.
• Install the new version. During the installation process, you must list the same directories that the previous installation referenced (sedex directory, etc.)

The MH configuration file config.xml lists all the directories and files to back up. The XML elements referencing the directories to back up are:

• /config/messageHandler/workingDir
• /config/messageHandler/statusDatabase

How to upgrade a MH installation on Linux

Since the installation of the Linux distribution is not carried out with a installer, an upgrade can be done fairly easy.

Suppose, you have installed MH under ${INSTALL_DIR}. To upgrade:

• Unpack the distro unter ${DISTRO_DIR}
• Stop the MH service.

• Remove the current version of MH with

  Code Block
  language bash theme Emacs
  rm ${INSTALL_DIR}/lib/*

  
  

• Install the new version with 

  Code Block
  language bash theme Emacs
  cp ${DISTRO_DIR}/lib/* ${INSTALL_DIR}/lib/*

  
  

• Start the MH service

MessageHandler logs an ERROR on startup

...

Reason: your Java installation does not have the Unlimited Strength Jurisdiction Policy Files installed. 

Is MessageHandler affected by "Log4Shell" vulnerability?

Although MessageHandler uses the log4j software library, MessageHandler is not affected by the vulnerability. The reason is that MessageHandler uses an older version of log4j, which is not vulnerable.

Please note that the sedex client, with which MessageHandler work together, is also not vulnerable in versions > 5.0.