Error Stopping IISAdmin
rkarthikeyan5
Posts: 3
Hello
I downloaded the trial version of the latest ANTS profiler.
My machine is Windows 2000, .NET 1.1 and IIS 5.0
When I go through the wizard, I give the following information.
Select ASP.NET web application hosted in IIS
PATH:
http://application url
.NET framework version : 1.1
IIS version : IIS 5
Username : ASPNET
Password : Automatically Detected
When I click Finish - It prompts for restarting the IIS, and when I give YES, IT shows the following error
THERE WAS A PROBLEM STARTING THE PROFILER
ERROR STOPPING IISADMIN
PLEASE CHECK THE EVEN LOG FOR MORE DETAILS
and the Event log has
I have gone through some previous posts and they all point to the port being used issue. Could you please assist me in figuring out this issue?
Thanks in advance
I downloaded the trial version of the latest ANTS profiler.
My machine is Windows 2000, .NET 1.1 and IIS 5.0
When I go through the wizard, I give the following information.
Select ASP.NET web application hosted in IIS
PATH:
http://application url
.NET framework version : 1.1
IIS version : IIS 5
Username : ASPNET
Password : Automatically Detected
When I click Finish - It prompts for restarting the IIS, and when I give YES, IT shows the following error
THERE WAS A PROBLEM STARTING THE PROFILER
ERROR STOPPING IISADMIN
PLEASE CHECK THE EVEN LOG FOR MORE DETAILS
and the Event log has
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.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 RedGate.Profiler.Engine.ProfilingSession.ServiceStatusCallback(Object sender, StatusEventArgs e) at RedGate.Profiler.Engine.ProfileIISController._1(StatusEventArgs ) at RedGate.Profiler.Engine.ProfileIISController._5() --- End of inner exception stack trace --- Server stack trace: at RedGate.Profiler.Engine.ProfileIISController._5() at RedGate.Profiler.Engine.ProfileIISController.StartProfilingIIS(String currentUserName, String& url, WebApplicationDefinition appDef) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, 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(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, 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 _5._4(IAsyncResult )
I have gone through some previous posts and they all point to the port being used issue. Could you please assist me in figuring out this issue?
Thanks in advance
Comments
IISProfileHostLog - has the following
ANTS Profiler has the following -
If it's not that, it could be a routing problem in a computer with two network interface cards and the request is going to an interface that doesn't have the NETBIOS protocol enabled.
Something is causing Windows to explicitly terminate connections to the computer when a netbios/WMI connection is requested.