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

KB442102: Data Load failed due to "An error occurred and user could not be loaded" with MicroStrategy Enterprise Manager 10.x


Mari Sugimura

Senior Cloud Support Engineer III • MicroStrategy


This article explains two more workarounds for data load issue that is discussed in KB300792, which is confirmed as valid when Enterprise Manager warehouse is in Oracle.

Description


Enterprise Manager Data Load failed due to the following error:
 


<log4j:event logger="MAEntMgr" timestamp="1533794442377" level="ERROR" thread="pool-1-thread-1"> 
<log4j:message><![CDATA[Configuration Object Migration Command of USER caused an interruption]]></log4j:message> 
<log4j:throwable><![CDATA[com.Strategy.maem.exceptions.EMException: Configuration Object Migration Command of USER caused an interruption 
at com.Strategy.maem.dataload.migration.ConfigurationObjectsMigrationCommand.executeCommand(Unknown Source) 
at com.Strategy.maem.dispatcher.command.BaseCommand.execute(Unknown Source) 
at com.Strategy.maem.dispatcher.command.BaseCommand.run(Unknown Source) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at java.lang.Thread.run(Thread.java:745) 
]]></log4j:throwable> 
</log4j:event>

 

Why is this happening?

While the root cause of this issue is explained in KB300792: Enterprise Manager 10.x data load fails with error "An error ocurred and EVENT could not be loaded", additional workaround confirmed.

Solution


There are two potential workarounds to this error.
 

Workaround 1

Add "EnableDescribeParam=1;" in "Additional connection string parameters" of Database Connections as shown below:

ka04W000001IrO1QAK_0EM44000000R0YE.png

Workaround 2

Configure Enterprise Manager Data Loader Service in a different machine. 
 
KB442102


Comment

0 comments

Details

Knowledge Article

Published:

October 4, 2018

Last Updated:

September 20, 2019