An error occurred while starting the Symantec Application Server Service; Reason for failure: There is already a listener on IP endpoint 0.0.0.0:1431. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations.

book

Article ID: 158047

calendar_today

Updated On:

Products

Control Compliance Suite Unix Control Compliance Suite Windows

Issue/Introduction

Unable to start CCS Application Server Service.

An error occurred while starting the Symantec Application Server Service; Reason for failure: There is already a listener on IP endpoint 0.0.0.0:1431. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations.

Application server log:

SUSP_SP,Error,Symantec.CCS.Common,AppserverService,2124,,7,DoBind,,0,0,"Symantec.CSM.AppServer: Start failed 00:00:16.8481175 : System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:1431. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at System.ServiceModel.Channels.SocketConnectionListener.Listen()
   --- End of inner exception stack trace ---
   at System.ServiceModel.Channels.SocketConnectionListener.Listen()
   at System.ServiceModel.Channels.ConnectionAcceptor.StartAccepting()
   at System.ServiceModel.Channels.ExclusiveTcpTransportManager.OnOpen()
   at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
   at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
   at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

Resolution

This issue is observed when Dot Net 4.5 is installed on CCS application server. Uninstall Dot Net4.5 from application server and Install Dot Net 4.0 version.

Dot Net 4.0 install is provided in CCS 11.0 base installation setup or download from below microsoft link.

http://www.microsoft.com/en-us/download/details.aspx?id=17718

 


Applies To

CCS 11.0