EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB487900: "Database password encryption / decryption failed" error when upgrading Metadata


Mikolaj Wus

Lead, Cloud Support • MicroStrategy


This article describes why administrators may be getting "Database password encryption / decryption failed" error when upgrading Metadata, and how to work around this problem.

Symptom

When attempting to upgrade metadata to a newer version via Configuration Wizard, the upgrade fails with the following or similar errors being logged in the MDUPD log file:

[SERVER:CastorServer][PID:8548][THR:13612][MD Update][Error][UID:][SID:][OID:0][CDSSMDUpdate.cpp:18205] MDUpdate: Failed to re-encrypt for NCS encryption level failed of error:'-2147216625'.
[SERVER:CastorServer][PID:8548][THR:13612][MD Update][Error][UID:][SID:][OID:0][CDSSMDUpdate.cpp:7977] MDUpdate: Failed to perform AES GCM re-encryption in configuration level with error code '-2147216625'.
[SERVER:CastorServer][PID:8548][THR:13612][MD Update][Info][UID:][SID:][OID:0][CDSSMDUpdate.cpp:2352] UNEXPECTED ERROR: (0x8004130F) Database password encryption / decryption failed.

Cause

This issue may occur due to the presence of devices within the metadata that were created in a previous version of Strategy using legacy encryption algorithms (specifically RC4). The two types of devices that may be contributing to this problem are:

  • FTP Devices with stored credentials
  • Email Devices with Smart Host credentials

Workaround

Upon verification of the presence of Devices of the specified types within the metadata, the solution involves utilizing a recent version of Developer to edit these Devices and explicitly re-enter their FTP or Smart Host passwords, thereby overwriting the legacy passwords. With that, there would be no need to delete these Devices, rather, merely editing the Device and re-entering the password to make the Device be preserved using a current encryption algorithm. After implementing these steps, the metadata upgrade can be successfully executed using the Configuration Wizard. 


Comment

0 comments

Details

Knowledge Article

Published:

March 20, 2025

Last Updated:

March 20, 2025