HELP : waiting for port 80 to become available on WINDOWS 2003
Brian Donahue
Posts: 6,590 Bronze 1
Hi Johan,
Because of some limitations in IIS, ANTS Profiler determines that the
website is available by trying port 80 and waiting for a response. That
works just fine, except when your website or webservice uses a port other
than 80. In that case, Profiler will never detect that IIS has restarted!
To avoid this, you need to set your web application up, at least
temporarily, to use port 80.
Regards,
Brian Donahue
Red Gate Technical Support
"Johan AMROUCHE" <jamrouche@netfective.com> wrote in message
news:3x9SuvVeEHA.2008@server53...
> I am running Windows 2003 and am not having any luck profiling a web
> service. When I attempt to profile things seem to proceed along (service
> shutdown and restart) but as Ants tries th "Start the Web Service". Things
> hang. The following message ends up in the event log:
>
> System.Exception: Timed out waiting for port 80 to become available
>
> Server stack trace:
>
> at RedGate.Profiler.Engine.ServiceHelper.a()
>
> at RedGate.Profiler.Engine.ServiceHelper.StartProfilingIIS()
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(Met
> hodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean
> fExecuteInContext, Object[]& outArgs)
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessa
> ge msg, Int32 methodPtr, Boolean fExecuteInContext)
>
> Exception rethrown at [0]:
>
> at RedGate.Profiler.Engine.ProfilingSession.StartProfiler()
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(Met
> hodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean
> fExecuteInContext, Object[]& outArgs)
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMess
> age 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 RedGate.Profiler.UI.c.EndInvoke(IAsyncResult result)
>
> at RedGate.Profiler.UI.frmMain.a(IAsyncResult )
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
>
>
Because of some limitations in IIS, ANTS Profiler determines that the
website is available by trying port 80 and waiting for a response. That
works just fine, except when your website or webservice uses a port other
than 80. In that case, Profiler will never detect that IIS has restarted!
To avoid this, you need to set your web application up, at least
temporarily, to use port 80.
Regards,
Brian Donahue
Red Gate Technical Support
"Johan AMROUCHE" <jamrouche@netfective.com> wrote in message
news:3x9SuvVeEHA.2008@server53...
> I am running Windows 2003 and am not having any luck profiling a web
> service. When I attempt to profile things seem to proceed along (service
> shutdown and restart) but as Ants tries th "Start the Web Service". Things
> hang. The following message ends up in the event log:
>
> System.Exception: Timed out waiting for port 80 to become available
>
> Server stack trace:
>
> at RedGate.Profiler.Engine.ServiceHelper.a()
>
> at RedGate.Profiler.Engine.ServiceHelper.StartProfilingIIS()
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(Met
> hodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean
> fExecuteInContext, Object[]& outArgs)
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessa
> ge msg, Int32 methodPtr, Boolean fExecuteInContext)
>
> Exception rethrown at [0]:
>
> at RedGate.Profiler.Engine.ProfilingSession.StartProfiler()
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(Met
> hodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean
> fExecuteInContext, Object[]& outArgs)
>
> at
>
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMess
> age 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 RedGate.Profiler.UI.c.EndInvoke(IAsyncResult result)
>
> at RedGate.Profiler.UI.frmMain.a(IAsyncResult )
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
>
>
This discussion has been closed.
Comments