Hi all,

While installing service center on deployment controller I am getting the below mentioned error.

DUe to some server level problem, we terminated the front end server and later relaunched front end server. That means IP address got changed for FE server. 

From DC side, while clicking on Apply and Exit, it's still pointing to old ip of FE server. Where should I make changes to fix this issue?


Deployment Controller  >>>> One Front end server

Service Center Installer v10.0.603.0

Start installing Service Center v10.0.603.0...

This operation may take a few minutes to complete...

Publishing Extension(s)...

Publishing Extension 'OMLProcessor'...

Publishing Extension 'IntegrationStudio'...

Reading ServiceCenter.oml oml file information...

Adding ServiceCenter eSpace to database...

Compiling ServiceCenter eSpace...

Preparing ServiceCenter eSpace deployment...

Deploying ServiceCenter eSpace...

Message 1
  [Error] Deployment Error
Error broadcasting message to Front-end Server osdffe1
( old IP Adress of Front end server)):System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond old IP address of FE server:12001

Server stack trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)
   at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at OutSystems.HubEdition.IBroadcastListener.MessageTransmission(BroadcastMessage msg)
   at OutSystems.HubEdition.DeploymentController.Compiler.SendMessageToFrontEnd(BroadcastMessage msg, Dictionary`2 serversTable, HEMessageArrayList messages, String nodeName, String ipAddress, Boolean useCompactMsg, CountDownLatch countdown, ServiceKind serviceKind).


Restarting the OutSystems services in that frontend should fix your problem. Did you already try that?


João Rosado