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

KB41893: "The remote server machine does not exist or is unavailable" error message occurs in MicroStrategy Narrowcast Server 9.x - 10.x DE Logs when a scheduled service is executed and duplicate subscription content is recieved by the recipients


Community Admin

• Strategy


Following a scheduled service execution in MicroStrategy Narrowcast Server 9.x - 10.x, duplicate subscription content is received by the subscribers and the following message is seen in the DE logs: "The remote server machine does not exist or is unavailable."

SYMPTOM:
Following a scheduled service execution in Strategy Narrowcast Server 9.x - 10.x, duplicate subscription content is received by the subscribers and the following message is seen in the DE logs:


Unexpected Error in FinishTerminating:[Error: 462 Desc: The remote server machine does not exist or is unavailable]. SE will continue terminating.

 

Note: In this instance a single, non-clustered, Narrowcast Machine is running the Execution Engine and Distribution Manager.
 
CAUSE:
When a Narrowcast System is running it will continually check to see if the Execution Engine is up and running by periodically pinging it. This behavior also holds true in a single non-clustered  Narrowcast System.  When an Execution Engine does not return the ping, a new execution of the same segment is begun as this would imply that the Execution Engine is down.
 
The cause for this erroneous behavior is that at times due to increased load or network traffic, the Execution Engine might take more time to reply to the ping message than the value of the governing setting 'Timeout for Negotiating Ping' setting. By default, the timeout is set to 1000 milliseconds.
 
ACTION:
If this behavior is continually seen it could indicate network or performance issues. But, to prevent this behavior from occurring , the value of the 'Timeout for Negotiation Ping' can be increased:

  • Open the Strategy Narrowcast 9.x - 10.x Administration Console.
  • Go to the 'System' menu and select 'Set Governing Settings...' under the appropriate system name:
ka04W000000OhjTQAS_0EM4400000029gP.png
  • Under the 'Distribution Manager' tab increase the 'Timeout for negotiation ping':
ka04W000000OhjTQAS_0EM4400000029gT.png

Comment

0 comments

Details

Knowledge Article

Published:

April 18, 2017

Last Updated:

April 18, 2017