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

KB38385: "MSINetServer init_tcp(): bind() failed: port 34952 is already in use!" error message appears in DSSErrors.log when attempting to start MicroStrategy Developer 9.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This technical article describes a issue in MicroStrategy Developer 9.x.

SYMPTOM:
When attempting to connect to a project source in Strategy Developer 9.x, users see the following message:


Connection failed. You are either: a) attempting to connect to a Strategy Intelligence Server and its version is older than the version of Strategy Desktop you are using. This configuration is not supported. b) using an incorrect port number in the Strategy project source. Please use the correct port number specified by the system administrator.

or

Network: Please retry task due to network request timeout. If problem persists, contact your network administrator.

The following error message is also recorded in the DSSErrors.log:

MSINetServer init_tcp(): bind() failed: port 34952 is already in use! socket() failed with error 97 Fatal error: unable to serve on any address. MsiNetServer: Invalid Socket.

 
CAUSE:
 One possible cause of this issue is that another program, for example Health Center, is using the same port as the Intelligence Server process.
ACTION:
Check in command line to see whether the same port the Intelligence Server process is using is in fact being used by another process by running the following command:

netstat -ano

If in fact there is another process, for example Health Center, using the same port, kill that process and try to start Strategy Intelligence Server again. Make sure to configure the Health Center (or any other process) to use a different port or not have both processes running at the same time.
 


Comment

0 comments

Details

Knowledge Article

Published:

April 6, 2017

Last Updated:

April 6, 2017