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

KB442229: Error "Object with ID 'xxx' and type 31 (DB Connection) is not found in metadata" is received when upgrading metadata in MicroStrategy Configuration Wizard 10.x


Yefang Zhou

Manager, Cloud Support • MicroStrategy


SYMPTOM: 
When trying to upgrade metadata from 10.8 to 10.11 in Strategy Configuration Wizard, below error is received:

ka02R000000kV73QAE_0EM44000000RFez.png


(Item 'Integer Constant In Metric' cannot be found.Item 'GROUP BY Non-ID Attribute' cannot be found.Item 'Integer Constant In Metric' cannot be found.Item 'DSSErrorMessageSenderTask' cannot be found.Item 'DSSErrorMessageSenderTask' cannot be found.Object with ID 'FBD601D5A8B74C89A9C7175B9E03E9F8' and type 31 (DB Connection) is not found in metadata. It may have been deleted.An unrecoverable error occurred during update. See log file 'C:\Program Files (x86)\Common Files\MicroStrategy\Log\MDUPD-7-26.log' for details.)

In MDUPD.log, below error is seen:
2018-07-26 04:45:45.175 [HOST:QYH1011][SERVER:CastorServer][PID:7720][THR:6328][MD Update][Info][UID:54F3D26011D2896560009A8E67019608][SID:183BE34FE681783E7DDB36D802BC9821] UNEXPECTED ERROR: (0x8004140B) Object with ID 'FBD601D5A8B74C89A9C7175B9E03E9F8' and type 31 (DB Connection) is not found in metadata. It may have been deleted.
CAUSE:
In Metadata, there are some hidden Database Instances used for data importing. In this case, one of them has an invalid reference to the missing DB connection mentioned in the error message.
ACTION:
Contact Strategy Technical Support for further assistance. In order to track down the cause of the inconsistency, customers encountering this issue should make note of Schema-related changes, Object Migrations, or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information. 


Comment

0 comments

Details

Knowledge Article

Published:

November 13, 2018

Last Updated:

November 13, 2018