Comments
6 comments
-
Hello,
My first impression is that there is a rights problem. Can you stop and start the IISAdmin service from the Services control panel? -
Hi Brian,
Yes, I can start/stop the IIS Admin Service from the Services control panel. I can also stop/start IIS from the IIS Manager.
Thanks -
Hi Brian,
I rebooted the machine and now it works. If it's a requirement to restart Windows after installing ANTS in order to profile ASP.NET applications, the installer should say something about this.
Thanks,
Vince -
Hi Vince,
Thanks for getting back to us. There is no requirement for a reboot that I know of; it must have cleared up the problem for some other reason. I've done a bit of testing in this area and didn't need to reboot the machine after a fresh profiler installation. -
OK. At least if anyone else reports the same problem you can suggest that they try a reboot. I normally would done that myself in this case, but I couldn't reboot this particular machine just anytime I wanted to.
By the way, I'm *extremely* happy with ANTS 2.0. It's become an invaluable tool. -
Thanks!
Add comment
Please sign in to leave a comment.
Unable to start profiler - exception details System.Exception: Error stopping IISAdmin ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
Server stack trace:
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machineAndPort)
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 RedGate.Profiler.Engine.ProfilingSession.HelperStatusCallback(Object sender, StatusEventArgs e)
at RedGate.Profiler.Engine.ServiceHelper.OnStatus(StatusEventArgs e)
at RedGate.Profiler.Engine.ServiceHelper.ᐁ()
--- End of inner exception stack trace ---
Server stack trace:
at RedGate.Profiler.Engine.ServiceHelper.ᐁ()
at RedGate.Profiler.Engine.ServiceHelper.StartProfilingIIS(String currentUserName, String url)
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.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at RedGate.Profiler.Engine.ProfilingSession.StartProfiler()
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 [1]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at System.Windows.Forms.MethodInvoker.EndInvoke(IAsyncResult result)
at ᐃ.ᐄ(IAsyncResult )
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.