Fatal exception on incomming TCP connect

[Anonymous]

Hello again…

now that my project is working pretty well on my Developer Machine (Win7 Pro, x64, VS2010 Pro), i tried to move the Service to a dedicated box (Win7 Pro, x64). The Service starts fine, no errors. When i fire up the GUI from localhost or remote, the server application crashes with the following exception:

2013-12-19 14:50:22.4574 [TRACE] - Checking for existing connection by endPoint='10.15.159.101:3179' and connectionType='TCP' 
2013-12-19 14:50:22.4574 [TRACE] - Creating new TCPConnection to connectionInfo='[TCP] Local -> 10.15.159.101:3179'. Connection will be established. 
2013-12-19 14:50:22.4574 [TRACE] - Checking for existing connection by endPoint='10.15.159.101:3179' and connectionType='TCP' 
2013-12-19 14:50:22.4574 [TRACE] - Adding connection reference by endPoint. Connection='[TCP] Local -> 10.15.159.101:3179'. 
2013-12-19 14:50:22.4574 [TRACE] - RetrieveConnection by remoteEndPoint='10.15.159.101:3179' and connectionType='TCP'. No matching connection was found. 
2013-12-19 14:50:22.4574 [TRACE] - Checking for existing connection by endPoint='10.15.159.101:3179' and connectionType='TCP' 
2013-12-19 14:50:22.4574 [TRACE] - Establishing new connection with [TCP] Local -> 10.15.159.101:3179 
2013-12-19 14:50:22.4804 [TRACE] - Checking for existing connection by endPoint='10.15.159.101:3179' and connectionType='TCP' 
2013-12-19 14:50:22.4804 [TRACE] - Listening for incoming data from [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 
2013-12-19 14:50:22.4804 [TRACE] -  ... 92 bytes added to packetBuilder. 
2013-12-19 14:50:22.4804 [TRACE] -  ... checking for completed packet with 92 bytes read. 
2013-12-19 14:50:22.4804 [DEBUG] - Waiting for client connnectionInfo from [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 
2013-12-19 14:50:22.5034 [FATAL] - A fatal exception occured in IncomingPacketHandleHandOff(), connection with [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 be closed. See log file for more information. 
2013-12-19 14:50:22.5034 [FATAL] - CommsError 
2013-12-19 14:50:22.5034 [DEBUG] - Closing connection with [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 due to error from [16]. 
2013-12-19 14:50:22.5034 [DEBUG] - Connection setup exception. ServerSide with [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179, Connection was closed during setup from [16]. 
2013-12-19 14:50:22.5034 [DEBUG] - Closing connection with [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 due to error from [6]. 
2013-12-19 14:50:22.5034 [TRACE] - Entering RemoveConnectionReference for [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 
2013-12-19 14:50:22.5034 [TRACE] - Entering RemoveConnectionReference for [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 
2013-12-19 14:50:22.5204 [TRACE] - Removed connection reference by endPoint for [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 
2013-12-19 14:50:22.5204 [DEBUG] - Triggered global shutdown delegates with [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 
2013-12-19 14:50:22.5204 [INFO] - [GuiCom] Client [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 getrennt 
2013-12-19 14:50:22.5444 [DEBUG] - Closing connection with [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 due to error from [13]. 
2013-12-19 14:50:22.5444 [TRACE] - Entering RemoveConnectionReference for [TCP] 10.15.146.4:5678 -> 10.15.159.101:3179 

I enabled all logging functions i could find, level Trace. There is no other log-file anywhere. Does Networkcomms need any dependencies besides .net framework 4.0 ?

[Anonymous]

There are no other dependencies at all. Can I ask what NetworkComms.Net version you’re using? I cannot remember exactly what error [16] was but it is not present in the current version. If you could try downloading the latest version that would be appreciated?

Matt

[Anonymous]

I will have to look into that tomorrow, but i am pretty sure i’m using the lastest version (2.3).
However, it might be that the VS Project references an older .dll which would be a shame for me … Will check tomorrow and report back here

-Namikon

[Anonymous]

Hm… You were right on this. Somehow an older version of NetworkComms.dll sneaked in. Good thing is it works now as expected.

Thanks a lot 🙂

[Anonymous]

Brilliant. Thanks for letting us know 😉

Marc

[Author]

Posts