Microsoft AntiSpyware BETA 1
January 9, 2005
I’ve just downloaded and installed the Microsoft AntiSpyware BETA 1 thing from Microsoft. I completed an intelligent scan and found no spyware so now I am doing a deeper scan. I’ve never run anti-spyware before – never felt the need since I am extremely careful about not only what I install but who I get it from. I’ve always been fairly dubious about the anti-spyware companies anyway.
So far I am impressed, the product is simple enough to use and it doesn’t seem to be hitting my perf at all (other than when it is actually doing this deep scan). It’ll be interesting to see whether I actually pick up any spyware over the coming months while I am running it.
February 2, 2005 at 12:00 am
I think the AnitSpyware broke NUnit. Since the install of AntiSpyware, NUnit (I run it inside VS 2003 using the Mailframe TestRunnerAddIn on a W2K workstation) fails with the following error:
“System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it”
I’ve tried turning AntiSpyware off, rebooting, reinstalling NUnit – to no avail.
February 2, 2005 at 12:00 am
It could be blocking – it could also be your firewall or your proxy server settings.
February 28, 2005 at 12:00 am
shot in the dark here, but it seems possible that it also blocks tcp remoting functionality I’m writing in C#. Has anyone else experienced this?
February 28, 2005 at 12:00 am
Its quite possible. If you disable it does the remoting start working again?
March 18, 2005 at 12:00 am
I think I may have not explained this properly in my earlier post.
Prior to installing MS Antispyware on my workstation, NUnit and the TestRunner addin were running without issue within my Visual Studio v2003 IDE.
Upon installation of Antispyware, the TestRunner is no longer able to load the test assembly (after pressing the “reload test assembly” button. The stack trace (below) is thrown into the VS output window.
However, NUnit’s external test runner (NUnit-GUI) continues to work. It is able to run the tests, but since it is outside Visual Studio, running the debugger becomes more problematic.
Yes, it seems that remoting has been blocked by Antispyware, but I have disabled Antispyware “real-time” protections and it did not help.
Here’s the stack trace. Anyone care to weight-in?
Thanx!
————————————-
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
Server stack trace:
at Microsoft.Web.Services.Messaging.SoapTcpChannel.Connect()
at Microsoft.Web.Services.Messaging.SoapTcpChannel.Send(SoapEnvelope envelope)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at Microsoft.Web.Services.AsyncResult.End(IAsyncResult result)
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, SoapEnvelope envelope)
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, Object obj)
at Mailframe.TestRunner.Server.TestRunnerClient.UnloadAssembly(LoadAssemblyMessage message)
at TestRunnerAddin.ProjectTestPanel.UnloadAssemblies()
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
Server stack trace:
at Microsoft.Web.Services.Messaging.SoapTcpChannel.Connect()
at Microsoft.Web.Services.Messaging.SoapTcpChannel.Send(SoapEnvelope envelope)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at Microsoft.Web.Services.AsyncResult.End(IAsyncResult result)
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, SoapEnvelope envelope)
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, Object obj)
at Mailframe.TestRunner.Server.TestRunnerClient.UnloadAssembly(LoadAssemblyMessage message)
at TestRunnerAddin.ProjectTestPanel.UnloadAssemblies()
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
Server stack trace:
at Microsoft.Web.Services.Messaging.SoapTcpChannel.Connect()
at Microsoft.Web.Services.Messaging.SoapTcpChannel.Send(SoapEnvelope envelope)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at Microsoft.Web.Services.AsyncResult.End(IAsyncResult result)
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, SoapEnvelope envelope)
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, Object obj)
at Mailframe.TestRunner.Server.TestRunnerClient.LoadAssembly(LoadAssemblyMessage message)
at TestRunnerAddin.ProjectTestPanel.LoadAssemblies()
March 18, 2005 at 12:00 am
Also I have noticed that when I try to restart the test runner process, I get the following message in the VS output window:
System.Web.Services.Protocols.SoapException: Server unavailable, please try later –> Exception has been thrown by the target of an invocation. –> Could not find file "C:\Documents and Settings\mercules.AIRCAT\VSWebCache\AIRCATCFG_443\use\bin\bin".
at Microsoft.Web.Services.Messaging.SoapClientAsyncResult.get_Response()
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, SoapEnvelope envelope)
at Microsoft.Web.Services.Messaging.SoapClient.SendRequestResponse(String methodname, Object obj)
at Mailframe.TestRunner.Server.TestRunnerClient.LoadAssembly(LoadAssemblyMessage message)
at TestRunnerAddin.ProjectTestPanel.LoadAssemblies()
What is this “"” file?
March 19, 2005 at 12:00 am
Hi there,
The quot thing is actually a HTML encoded quote character
It looks like a flat out rejected connection attempt between VS and the test runner.
Did you see a pop up at all that you said “block” to?
May 3, 2005 at 12:00 am
So, TestRunner uses an out of process test component with remoting in order to separate the tests from VS.NET. You’ll need to configure your firewall to allow the socket.
Also, grab the latest version!