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

KB274055: "Server: xxx is already monitoring metadata with GUID:xxx" Error appears while adding the environment to MicroStrategy Enterprise Manager


Community Admin

• Strategy


The following knowledge base article describes the cause of the error "Server: xxx is already monitoring metadata with GUID:xxx" in MicroStrategy Enterprise Manager. A workaround is provided.

SUMMARY:
This issue has been classified as a working design. The impact is limited to Strategy Enterprise Manager product where multiple environments are running a duplication of the Metadata.
 
SYMPTOMS:
When attempting to add a second environment to Strategy Enterprise Manager, an error message may appear as shown below.

ka04W00000148swQAA_0EM440000002SZV.jpeg


Error while adding the environment. 
'com.Strategy.maem.exceptions.EMException: Server: xxx is already 
monitoring metadata with GUID: xxx

 
CAUSE:
The Metadata was duplicated from the Database side and contains the same Metadata GUID as the Environment already added.
 
Verify that the MD GUIDs are the same by following the SQL
 

select PROP_VAL from DSSMDOBJPROP where OBJECT_TYPE = 36 and 
PROP_ID=1 and VALUE_SEQ=1 and PROPSET_ID='03EC6B029B7D4FC260A147C8110965A3'

 
If they are not the same, contact Strategy Technical support for assistance.
 
ACTION:
Refer to KB44209  to create a new metadata repository and then, duplicate the projects there instead of restoring metadata tables from a database backup file created by your Database Administrator. A value in PROP_VAL column for the new repository becomes unique, with which, the error message no longer appears when adding the environment.
Note: Previously recorded statistics data will no longer have the PROP_VAL matching with the one created in a new repository, meaning, records collected from the same projects may be seen as coming from two different repositories. 
 
WORKAROUND: 
Create another Enterprise Manager environment and keep the environment exclusive.


Comment

0 comments

Details

Knowledge Article

Published:

June 27, 2017

Last Updated:

November 13, 2017