No connection could be made because the target machine actively refused it 127.0.0.1:61137

Question

4.00/5 (1 vote)

See more:

Win2008-R2

, +

Hi,

I am trying to execute a NUnit test case (.Net 4.0 .dll, compiled against NUnit 2.5.9 ) using NUnit console in Windows 2008 R2 (X64) but it fails with below error message. Any idea?

----

System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:61137

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.RemoteConnection.CreateNewSocket()
   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 NUnit.Core.TestRunner.get_Running()
   at NUnit.Core.ProxyTestRunner.get_Running()
   at NUnit.Util.TestLoader.get_Running()
   at NUnit.Gui.NUnitForm.get_IsTestRunning()
   at NUnit.Gui.NUnitForm.NUnitForm_Closing(Object sender, CancelEventArgs e)
   at System.Windows.Forms.Form.OnClosing(CancelEventArgs e)
   at System.Windows.Forms.Form.WmClose(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Posted 18-Mar-11 4:57am

Member 4545580

Updated 18-Mar-11 7:39am

Richard MacCutchan

v3

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Eduard Keilholz · Answer 1 · 2011-03-18T05:37:00

Solution 1

Erhm, are you sure your firewall is switched off, or that you've created a rule in your firewall allowing communication over the given port 61137?

Posted 18-Mar-11 5:37am

Eduard Keilholz

Member 4545580 · Answer 2 · 2011-03-18T06:23:00

Solution 2

Hi Eduard,

Thanks for your response.

Port number is changing all the time. Now it's 61137 and last time it was some thing else.
I am executing the DLL manually using NUnit in a single box..should I be checking the firewall even if the DLL is not calling any external services?

Thanks,
Venu

Posted 18-Mar-11 6:23am

Member 4545580

Comments

Eduard Keilholz 18-Mar-11 12:26pm

I do think so, just try to switch it off for a brief moment. If your code works, you know the firewall is in your way, else you have to find the problem somewhere else.

Richard MacCutchan 18-Mar-11 13:41pm

I don't think the firewall looks at messages on the loopback address.

Richard MacCutchan 18-Mar-11 13:42pm

Are you sure you have a listener on this address?

Member 4545580 18-Mar-11 14:13pm

ping 127.0.0.1:61137 doesn't work
but 127.0.0.1 works fine.

snkscore · Answer 3 · 2011-04-22T06:56:00

I don't know if this is possible, but I got this same error from NUnit when I actually had an infinite loop going in one of my tests.

I had some overloaded assert method that ended up looping back on itself. When I ran the code using the TestDriven.Net tool I saw the stack overflow exception that was causing Nunit to hang, and eventually return the error you mentioned.