RSECW013: Primary legacy key is used inconsistently

The check of the key status across all instances shows that there are discrepancies in the primary keys between at least two instances. For example, one instance uses an individual key and another instance uses the default key, or two instances use different individual keys (apparent by the key alias shown in parentheses).

If you encounter this error, the possible solution depends on the number of distinct keys that are in use across all instances. This is the highest number shown in parentheses in the key table. If any cell contains the value Default Key, the highest number increases by one.

If this value is 3 or higher, only the following emergency recovery procedure is applicable. For more information, see the related link.

If this does not work, try the following:

RSECW014: At least one secondary legacy key found

In the initial check phase of the tool, before any change has been done, at least one instance already has a key file which contains a secondary key. This might be the result of a previous tool run which was terminated, in conjunction with an explicit or implicit deletion of the milestone, or of manual changes to the key files.

RSECW025: Server state is not "Active"

For the initial key status check on all instances and the validation of key updates, all instances that are registered to the message server are addressed via RFC. During this process, an instance has been found which is registered in a status that is different from Active, for example Starting, Stopping, or Passive.

You can see the current value in the SM51 transaction. The tool refuses to work if there are instances in the system in any of those states. The ability of those instances to process RFC calls and to execute file system operations is undefined.

RSECW029: RFC --> <instance_name>:<error_message_from_instance>

The RFC connection to the mentioned instance failed with the technical error message that is displayed as well.

RSECW054: At least one character does not match

One or more of the requested check positions for the key backup were incorrect. The generated key has been abandoned, and a new key will be generated. Repeat the procedure with the new key. Due to the importance of a key backup to assure recoverability from a key file loss, there is no option to suppress this step.

RSECW059: Incorrect key format

The value you have entered is no properly formatted key value. A 48-character sequence comprising of numerical digits and the letters A to F in uppercase or lowercase is expected. Gaps or other separators are not permitted.

RSECW060: The key you entered does not match the previously used key

In a previous step of this tool, a key has been generated or manually entered and changes were done based on the value of this key.

You are currently about to resume this process after it had been temporarily put at rest. To resume consistently, the same key value must be used.

The tool does not store the key value persistently, but can detect whether the value presented now matches the value previously used.

RSECW090: Wrong value for the secondary key

The system checked that all instances see the correct value of the secondary key in the key file. This check found a different value for at least one instance. The most likely reason is that the key distribution strategy has been incorrectly chosen as Single Instance Update, while All Instance Update would have been required.

Verify that All Instance Update is correct by affirming that the instances use individual key files. Then restart the tool and select the key distribution strategy All Instance Update.

RSECW104: Wrong value for primary key

After an activation of the new key, the system verifies that all instances see the new key as primary key. This check found a different value for at least one instance. As by the checks already done in preceding steps, this situation is not likely to happen and indicates an unrecognized update error in one of the key files, or parallel manual changes to the key files.

Try to restart the tool. If the issue does not disappear, perform the emergency recovery procedure. For more information, see Emergency Recovery Procedure.

RSECW121: Secondary key still present

The system checked that all instances see that the obsolete secondary key has been removed from the key file.

The secondary key is still present for at least one instance. As by the checks already done in the preceding steps, this situation is not likely to happen and indicates an unrecognized update error in one of the key files, or parallel manual changes to the key files. Run the SECSTORE transaction with Check Entries without limiting the selection. If no errors are found, restart the tool and repeat the step. If the error does not disappear, you may manually delete the secondary key from the key files that still contain it. Then run the tool again to verify that it now completes.