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

KB18398: ‘Error saving DBMS object ‘XXXXXX’. UNEXPECTED ERROR: (0x8004111a) Cannot save, move or copy this DBMS object because it has been changed in the Metadata’ error occurs when trying to upgrade a project in MicroStrategy Developer 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article describes best practices while upgrading MicroStrategy projects in Developer

SYMPTOM:
When a user tries to upgrade a project in Strategy Developer 10.x, the following error occurs:


'Error saving DBMS object 'XXXXXX'. UNEXPECTED ERROR: (0x8004111a) Cannot save, move or copy this DBMS object because it has been changed in the Metadata.'.

 

CAUSE:
One of the causes for this error is because of concurrent Strategy project upgrades being performed through different Strategy Developer 10.x clients. When upgrading the Strategy Metadata through Strategy Developer 10.x, project objects are not the only ones affected but also those that are not in the project, such as configuration objects need to be upgraded as well. For this particular error, a database instance object is involved and when Strategy Developer 10.x tries to upgrade the object, it detects that the definition has changed due to the concurrent project upgrades being performed, and ultimately needs to be reloaded from the Strategy Metadata.
 
ACTION:
As following best practices when performing project upgrades in Strategy Developer 10.x, it is not recommended, supported, nor certified to perform concurrent Strategy project upgrades through different Strategy Developer 10.x clients, as this practice may cause a metadata inconsistency.
 
WORKAROUND:
The user can close the dialog window for this error, disconnect from the project, and afterwards re-attempt to upgrade the Strategy project.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 15, 2017

Last Updated:

June 15, 2017