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

KB442169: Data load fails for the 1st execution after Intelligence Server is restarted in MicroStrategy Enterprise Manager 10.x


Min Zheng

Senior Manager, Cloud Support • MicroStrategy


Data load fails for the 1st execution after Intelligence Server is restarted in MicroStrategy Enterprise Manager 10.x

SYMPTOM
Data load fails for the 1st execution after Intelligence Server is restarted in Strategy Enterprise Manager 10.x
It might be observed that data load would fail regularly and the 2nd data load after the failure would be completed successfully.
When the data load fails, it could be confirmed from DSSErrors log that the dataloader process crashes during the data load and is restarted automatically.
 
DSSERRORS log:


2017-10-23 09:00:47.227+09:00 [HOST:XXXXXX][SERVER:][PID:1136][THR:8992][MultiProcess][Error] Find target process dead while waiting for reply
2017-10-23 09:00:47.227+09:00 [HOST:XXXXXX][SERVER:][PID:1136][THR:7868][MultiProcess][Error] Find target process dead while waiting for reply
2017-10-23 09:00:47.227+09:00 [HOST:XXXXXX][SERVER:][PID:1136][THR:8992][Database Classes][Error] Unknown failed. Unable to connect. 
Error type: System call error. Error communicating with connection process. Find target process dead while waiting for reply. SQL Statement: SELECT REP_GUID, REP_ID FROM EM_MD.

 MAEntMgr.xml

 [Logger:MAEntMgr][Thread:Timer-1][Level:ERROR] Unable to connect to Intelligence Server: 
Incorrect server name


 
After further investigation, the failure always happens after Intelligence Server restart including manual restart or OS restart.
 
CAUSE
This is a known limitation for Strategy Enterprise Manager 10.x.
It is very similar to situation in KB441412 , where the issue happens when Intelligence Server is being started.
For this article, the issue could be observed even if Intelligence Server has been started successfully and is running when the data load is kicked off.
It is because EM server would have issue to fetch the Intelligence Server information after Intelligence Server is restarted.
As EM services would be restarted automatically after the failure, the data load afterwards would be completed without any issue.
 
ACTION
If EM server and Intelligence Server is hosted on the same machine, the action in KB441412 can be taken to ensure EM service can be started after Intelligence Server is completely running.
 
If EM server and Intelligence Server is hosted on different machines, please schedule the OS restart or service restart with certain interval as Intelligence Server restart is more time-consuming compared with EM service restart.
  KB442169


Comment

0 comments

Details

Knowledge Article

Published:

October 29, 2018

Last Updated:

November 8, 2018