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

KB486236: In MicroStrategy Web the I-Server name gets modified when in cluster environment


Gustavo Sulbaran

Product Specialist • MicroStrategy


This article indicates the situation in which the user has configured MicroStrategy Web to have two or more I-servers in which one of them have an alias and the others do not. Later after having set this configuration the system administrator notices that the I-server alias eventually reverts back to its original hostname possibly breaking the usage of the application.

PREREQUISITE:
Before starting with this article, it is assumed the user with the issue also has:
 

  1. The web application works properly when the alias is being used.
  2. After some time, the I-Server reverts back to the HostName
  3. The expected sys_defaults_<CorrectServerAliasName>.properties was already set.
  4. The AdminServer.XML has been previously configured with the correct alias name and conn=”true”

 
ISSUE:
Assuming the user has:
 

  • 1 machine with web server
  • 3 machines with I-servers

iserver1: tec-l-1183283
iserver2: tec-l-1183284
iserver3: tec-l-1183280
and the following host files in each of them:
Web server hosts file:
xxx.xxx.xxx.xx1   iserver1alias
xxx.xxx.xxx.xx2   tec-l-1183284.xxx.com tec-l-1183284
xxx.xxx.xxx.xx3   tec-l-1183280.xxx.com tec-l-1183280
iserver1 hosts file:
xxx.xxx.xxx.xx2   tec-l-1183284.xxx.com tec-l-1183284
xxx.xxx.xxx.xx3   tec-l-1183280.xxx.com tec-l-1183280
iserver2 hosts file:
xxx.xxx.xxx.xx1   iserver1alias
xxx.xxx.xxx.xx2   tec-l-1183284.xxx.com tec-l-1183284
xxx.xxx.xxx.xx3   tec-l-1183280.xxx.com tec-l-1183280
iserver3 hosts file:
xxx.xxx.xxx.xx1   iserver1alias
xxx.xxx.xxx.xx2   tec-l-1183284.xxx.com tec-l-1183284
xxx.xxx.xxx.xx3   tec-l-1183280.xxx.com tec-l-1183280
The user properly sets the cluster in developer to be:

ka0PW0000000AsDYAU_0EMPW000002W67Z.jpeg

And following that he sets in the Web admin page the alias he was looking forward to use, in this case “iserver1alias”:

ka0PW0000000AsDYAU_0EMPW000002W69B.jpeg
ka0PW0000000AsDYAU_0EMPW000002W6An.jpeg

After some time or after a disconnection of that server the Servername of “ISERVER1ALIAS” is replaced with hostname TEC-L-1183283 automatically

ka0PW0000000AsDYAU_0EMPW000002W6E1.jpeg

ACTION:
In order to fix the above-mentioned behavior, please do the following:
 
WARNING: Until further notice the steps of this article will only work when user affinity is disabled. This is currently under investigation, please contact Strategy Technical Support for an update.
1) Go to Developer, leave I-server TEC-L-1183283 from cluster and then stop Strategy Intelligence Server on that one.
2) Add the Registry key "ServerName"="iserver1alias" on that one I-server (TEC-L-1183283)
Important: This name needs to be recognizable as a network machine. The DNS needs to recognize the entry as a machine and be able to resolve its IP address for any client machine access.
Note: Before implementing the steps below, remember to make sure that Strategy Intelligence Server is shutdown.
STEPS FOR WINDOWS:

  1. On the Strategy Intelligence Server and later machine, access the Windows registry.

Navigate to the location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Strategy\DSS Server\Castor
 

  1. Look for an entry called 'ServerName' in the above location.
  1. If the above entry is not found, create a new string value called 'ServerName' as shown below. 
ka0PW0000000AsDYAU_0EMPW000002W6Fd.jpeg
  1. Provide the required service name for the 'ServerName' entry by editing it.

Registry Modification WARNING: Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows, the user should backup the registry and/ or update an Emergency Repair Disk prior to alterations.
STEPS FOR LINUX:
 

  1. On UNIX/Linux machines, edit the MSIReg.reg file found in the home folder of the Strategy installation.
  2. Make a backup of this file before making any changes.
  1. In the MSIReg.reg file, find an entry called 'ServerName'. If this entry is not found, create a new string value called 'ServerName' and assign it to the displayed area as shown below.

"ServerName"=<MY_ISERVER_ALIAS>
 

ka0PW0000000AsDYAU_0EMPW000002W36V.jpeg

(Example img)
 

  1. Save and close the MSIReg.reg file.

3) Start the I-server on that one machine TEC-L-1183283
4) Join that machine again to the cluster in developer:
 

ka0PW0000000AsDYAU_0EMPW000002W6HF.jpeg

5) In Web admin page, Disconnect and then Connect TEC-L-1183280. Finally, the Server name of ISERVER1ALIAS remains as ISERVER1ALIAS and the alias is always used as server name in the Web Admin page.

ka0PW0000000AsDYAU_0EMPW000002W4k6.jpeg

           
 


Comment

0 comments

Details

Knowledge Article

Published:

December 15, 2023

Last Updated:

December 15, 2023