Hello,

Ater update from version 2.7.0.5 connection between my client 2.10.0.4 for Visual 2010 and corresponding Grid Node Server running on Windows 2008 Server looks like it's working. Projects are being compiled and tests run. Despite i'm still receiving error messages:

System.Exception: Service nCrunch.Core.Grid.Connectivity.GridContractMessageBugReportDataProvider is not registered
w nCrunch.Common.ServiceLocator.FetchInstance[T](Boolean throwOnMissingService)
w nCrunch.Core.Grid.Connectivity.ReceivableSerializationContractMessage.GetMessage(BinarySerializer serializer)
w nCrunch.Core.Grid.Connectivity.GridMessageReceiver.TryRead(Byte[] newData, Int32 newDataLength)
w nCrunch.Core.Grid.Connectivity.OpenConnection..()
w nCrunch.Common.ErrorHandler.DoWithErrorHandling(Action action, Object context)

Are the exceptions somewhat important or how to get rid of them?

I have already installed correct version. I have checked it out in programs/function Windows console and as I have mentioned tests are being run on that server.

In server log there are serveral exceptions:

[14:02:07.0499-?-28] Ceasing to send messages because of an error (was the connection closed?): System.IO.IOException: Nie można zapisać danych do połączenia transportowego: Nawiązane połączenie zostało przerwane przez oprogramowanie zainstalowane w komputerze-hoście. ---> System.Net.Sockets.SocketException: Nawiązane połączenie zostało przerwane przez oprogramowanie zainstalowane w komputerze-hoście
w System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
--- Koniec śladu stosu wyjątków wewnętrznych ---

Server stack trace:
w System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
w  .Write(Byte[] , Int32 , Int32 )
w nCrunch.Core.Grid.Connectivity.Zlib.DeflateStream.Write(Byte[] buffer, Int32 offset, Int32 count)
w nCrunch.Core.Grid.Connectivity.BidirectionalStream.Write(Byte[] buffer, Int32 offset, Int32 count)
w System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
w System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]:
w System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
w System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
w nCrunch.Core.Grid.Connectivity.BidirectionalStream..EndInvoke(IAsyncResult )
w nCrunch.Core.Grid.Connectivity.BidirectionalStream.EndWrite(IAsyncResult asyncResult)
w nCrunch.Core.Grid.Connectivity.GridMessageSender.(IAsyncResult )

and then

[14:02:07.6321-NodeProcessor-7] Build was successful for C:\NCrunch Grid Node\6036\52\[project name].dll
[14:02:07.6881-NodeProcessor-29] Build was successful for C:\NCrunch Grid Node\6036\51\[project name].dll

Indeed the client running previous version was the reason of these messeges while the server was doing its job for new clients.

I'd like to better understand the logic of Ncrunch grid. Could you tell me why the server is broadcasting such a messeges? It is not enough to log them in the file?

Thanks for your help.

When connecting to multiple servers there is a probability to leave the problems unnoticed. So I think that is good idea to broadcast them.

Thank you for the explanation.