Agent failed to register with the server

I’m getting this error periodically.

Here’s the information from the event log:
Agent failed to register with the server six times. Time elapsed for last registration attempt was 120016ms.
Error message: Exception: TimeoutException

Message: This request operation sent to net.pipe://localhost/ContinuaCI/IAgentRegistrationService did not receive a reply within the configured timeout (00:02:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

Stack Trace:
Server stack trace:
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

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 Continua.Modules.Builds.Common.Services.Contracts.IAgentRegistrationService.RegisterV3(String hostname, Int32 port, String version, Boolean propertiesCollected, String collectorsHash)
at Continua.Modules.Builds.Agent.RegistrationController.Register()

This is on a new machine and we’re setting up clean, using MSSQL 2017 as the backend.

Any other log files I can look into or areas I can poke around to try to determine what the cause is? This is running 1.9.2.580

Thanks.

This suggests the Continua Server service is not responding to the wcf call. Have a look in the windows event log and see if the server is reporting any errors.

This can be caused by something else running on port 9000 causing the wcf server to fail (annoyingly wcf will then also fail for all transports) - but that should be logged in the event log.

running netstat -a -b -n should show if any other process has claimed port 9000.

Restarting the Continua Server service should help resolve this, however if there is other software installed that is using port 9000 then you may need to change the port Continua uses

https://wiki.finalbuilder.com/display/continua/Networking+and+Security

If none of the above helps, then the next step is to enable debug logging on the server service - then wait till the issue occurs, stop the service, disable debug logging (it does slow things down) and send the debug log to support @ finalbuilder.com