Could not start Memory Profiler on other Port

Memory profiling for .NET developers

Moderators: StephenC, Alex.Davies, AndrewH, melvyn.harbour

Could not start Memory Profiler on other Port

Postby jaap.q42 » Wed Dec 23, 2009 11:17 am

I couldn't start the memory profiler on unused port, i've used other ports, opened them in my firewall etc.

Can someone please explain why this is happening?

I'm using 5.2.0.44 build sent to me by stephen.

Timed out waiting for port 8013 on 127.0.0.1 to become available
RedGate.Profiler.Engine.Exceptions.CannotStartSessionException
at RedGate.Profiler.Engine.Startup.Sessions.BaseSession`1.Launch()
at RedGate.Memory.Controller.Session.ProfilerSession.Launch()

Caused by:

Timed out waiting for port 8013 on 127.0.0.1 to become available
RedGate.Profiler.Engine.Exceptions.CannotStartIisSessionException
at RedGate.Profiler.Engine.Startup.Sessions.IISSession`1.PerformLaunch()
at RedGate.Profiler.Engine.Startup.Sessions.BaseSession`1.Launch()

Caused by:

Timed out waiting for port 8013 on 127.0.0.1 to become available
RedGate.Profiler.Engine.Startup.IIS.PortTimeoutException
stack trace:
at RedGate.Profiler.Engine.Startup.IIS.IISUtilities.WaitForPort(IPAddress address, Int32 port, Int32 timeout)
at RedGate.Profiler.Engine.Startup.IIS.IISUtilities.WaitForPort(String hostname, Int32 port, Int32 timeout)
at RedGate.Profiler.Engine.Startup.IISActuators.IISW3wpStarterActuator`1.StartProfilingIIS(String currentUserName, String subprocessVariableValue)
at RedGate.Profiler.Engine.Startup.IIS.IISStarter`1.StartProfilingIIS(String currentUserName, String subprocessVariableValue)
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)
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.Startup.IIISActuator`1.StartProfilingIIS(String currentUserName, String subprocessVariableValue)
at RedGate.Profiler.Engine.Startup.Sessions.IISSession`1.PerformLaunch()
jaap.q42
 
Posts: 26
Joined: Thu Dec 17, 2009 3:21 pm

Postby Chris.Allen » Thu Dec 24, 2009 1:22 pm

There's a chance that it could simply be profiler overhead causing a timeout but this is unlikely. Usualy it means w3wp.exe has crashed. Do you get errors in the windows application event log?

Are you saying that the normal IIS port is working fine?
Chris.Allen
 
Posts: 594
Joined: Thu Mar 12, 2009 4:17 pm

Postby jaap.q42 » Thu Dec 24, 2009 1:53 pm

Yes, it works using the "restarts IIS" option. I'm currently occupied with other stuff, I'll come back with logs/Event logs.

Thx!
jaap.q42
 
Posts: 26
Joined: Thu Dec 17, 2009 3:21 pm


Return to ANTS Memory Profiler Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests