HELP With Windows Server 2003

Brian DonahueBrian Donahue Posts: 6,590 New member
Hi Jim,

I've had a look at the code that waits for port 80 to become available,
and it's simply trying to initiate a connection to TCP port 80 on your
computer. Somehow, your IIS has fallen and it can't get up!

Can you check your system event log around the time that Profiler dies
and see if you have an error from W3C stating "The server couldn't bind
instance 1" or something to that effect? Please let me know if you have that
entry. I think I've seen this problem before.

Regards,

Brian Donahue

Technical Support Engineer

Red Gate Software Ltd.

+44 870 1600 037

mailto:[email protected]



"Jim Culbert" <[email protected]> wrote in message
news:[email protected]
> 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.
>
>

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 New member
    ANTS Profiler now makes requests to the port of the website that you are profiling, based on the URL that you had entered in the URL box. This error shoudl not occur any more unless IIS has some difficulty restarting.
This discussion has been closed.