How can we help you today? How can we help you today?
JustinLofquist

Activity overview

Latest activity by JustinLofquist

Thanks - that got us closer (or differen. We are now in the same situation as a previous post: "Profiling asp.net app: Timed out waiting for port 8013 on" The error we recieve is: Could not start IIS. RedGate.Profiler.Engine.Exceptions.CannotStartIisSessionException at bt.Launch() at RedGate.Profiler.Session.ProfilerSession.h() Caused by: Could not start IIS. RedGate.Profiler.Engine.Exceptions.CannotStartIisSessionException at bt.Launch() Caused by: Timed out waiting for port 8013 on 10.127.9.82 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 bt.StartProfilingIIS(String currentUserName, Uri& url) at RedGate.Profiler.Engine.Startup.IIS.IISStarter.StartProfilingIIS(String currentUserName, Uri& url) 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.IProxyIISSession.StartProfilingIIS(String currentUserName, Uri& url) at bt.Launch() To answer the questions asked in the other post, the OS is Windows 2000. We are running IIS 6, and using ANTS Profiler module. The web server is local. We have tried localhost and machinename in the URL. / comments
Thanks - that got us closer (or differen. We are now in the same situation as a previous post: "Profiling asp.net app: Timed out waiting for port 8013 on" The error we recieve is: Could not start ...
0 votes
Login failed for user '(null)': Not associated with...
I am running ANTS Profiler 4.1 against an MSCRM 3.0 application, and am recieinvg the error: "Login failed for user '(null)': Not associated with a trusted SQL Server connection". I have a feel...
2 followers 3 comments 0 votes