Remote Update with Improved Diagnostic

21 July 2015

The Remote Update Management System (RUMS) allows to maintenance and update the CRYPTO-BOX® without shipping the dongle from the end-user to the vendor and back.


This remote update functionality is very flexible: updates can be processed easily with just a few mouse clicks. Or it can be deeply integrated into your distribution system via command line tools or even directly into the source code via API. The RUMS Application Notes explain all update options in detail.

A revised RUMS is part of the latest Professional Protection Kit (PPK) 7.0 which is available in our download section (MyMARX login and valid support contract are required for downloading).

It is especially helpful for customers extensively using Remote Update. They sometimes facing with error messages coming from their end-users like:

"The Activation Code cannot be decrypted: Transaction mark is not valid. Errorcode: 0x8000006D"

This means that the activation code was generated for another request and/or for another CRYPTO-BOX.

Typical situations which may cause this are:

  • The end-user generated the update request (transaction key) and submitted it. While this request was processed, the end-user decided to generate another one. So when he receives the activation code generated for the first request, he has a different transaction mark in the CRYPTO-BOX and this activation code can’t be executed any more.
  • Distributor by mistake sent activation code intended for end-user A to end-user B.

To help detecting and resolving above situations easily, the RUMS update utility now displays a new error message:

"This Activation Code was generated for different CRYPTO-BOX (Transaction Request). Errorcode: 0x8000008F"

when trying to execute an activation code which does not fit to the transaction request.

Please contact us for further questions on the CRYPTO-BOX or Remote Update (RUMS) functionality: [email protected] or use our support ticket system.

Back