Red Gate forums :: View topic - Could not start Memory Profiler on other Port
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
ANTS Memory Profiler Previous Versions
ANTS Memory Profiler Previous Versions forum

Could not start Memory Profiler on other Port

Search in ANTS Memory Profiler Previous Versions forum
Post new topic   Reply to topic
Jump to:  
Author Message
jaap.q42



Joined: 17 Dec 2009
Posts: 26

PostPosted: Wed Dec 23, 2009 11:17 am    Post subject: Could not start Memory Profiler on other Port Reply with quote

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()
Back to top
View user's profile Send private message
Chris.Allen



Joined: 12 Mar 2009
Posts: 588

PostPosted: Thu Dec 24, 2009 1:22 pm    Post subject: Reply with quote

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?
Back to top
View user's profile Send private message
jaap.q42



Joined: 17 Dec 2009
Posts: 26

PostPosted: Thu Dec 24, 2009 1:53 pm    Post subject: Reply with quote

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

Thx!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group