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

KB439522: “Incorrect server name.” error message displayed when attempting to connect to project source using integrated authentication (Kerberos) in MicroStrategy Developer 10.4


Willian Tomazini

Senior Cloud Support Engineer I • MicroStrategy


This article describes how to troubleshoot the “Incorrect server name.” error in MicroStrategy Developer 10.4 that can occur when Integrated Authentication is used.

PREREQUISITES
Make sure the intelligence server has already been configured for Kerberos authentication according to the steps from KB19110:
https://community.strategy.com/article/KB19110-How-to-configure-MicroStrategy-Intelligence-Server
SYMPTOM
When attempting to connect to a 3-tier project source using integrated authentication (Kerberos) in Strategy Developer 10.4, the error message below is displayed, even if the Server name field is filled properly:

ka044000000kOb0AAE_0EM44000000QGcZ.png

CAUSE
This is working as designed in Strategy Developer 10.4. The issue occurs because the server name provided is invalid or is not recognized in the network.
ACTION
Below there are a few settings that can be critical for integrated authentication to work properly:
 

  1. Open Strategy Developer; 
  2. Right click the desired project source and select “Modify Project Source”;​

 

ka044000000kOb0AAE_0EM44000000QGct.png

       3.​ Click on the “Advanced” tab and make sure “Use Integrated Authentication” option is selected;

ka044000000kOb0AAE_0EM44000000QGcy.png

       4. Click on the “Connection” tab and make sure the “Server name” field is filled properly. In the example, assume the intelligence server’s hostname is “iservername” and the AD domain is “mydomain.com”. Also, verify that the “Port number” field value matches with intelligence server’s port number.

If the steps above were reproduced and the same error still occurs, it’s possible that the intelligence server’s hostname is not recognized in the network. To fix it, follow the instructions below for Windows hosts file configuration:
 

  1. In Windows Explorer, access C:\Windows\System32\drivers\etc
  2. Use a text editor to open the hosts file;
  3. Include a new row following the syntax “ipaddress       hostname          hostname.domain”, like the example below:  


192.168.1.99       iservername       iservername.mydomain.com

where “192.168.1.99” is the intelligence server’s IP address, “iservername” is the intelligence server’s hostname and “iservername.mydomain.com” is the intelligence server’s hostname under the AD domain;
 
       4. Save the file;
       5. If you can’t save the file in the same directory, save it in another folder and then move the new hosts file back to the etc folder, replacing the original one.
 
These steps make the intelligence server`s hostname recognizable and the integrated authentication works correctly.

ka044000000kOb0AAE_0EM44000000QGdD.png
ka044000000kOb0AAE_0EM44000000QGdI.png

 
 
KB439522


Comment

0 comments

Details

Knowledge Article

Published:

January 24, 2018

Last Updated:

January 1, 2019