ASP.Net process is configured to run under must be different

The following error is coming up when ever I start the ants profiler and selects asp.net application to profile.. The error message is as follows

" There was a problem starting the profiler. The user the ASP.Net process is configured to run under must be different to the currenrly logged on user. Please check the event log for more details"


I have verified the event log also and it has the same error message.

Could you provide some help on this. I am currently using the 'Ants Profiler 2.5.0 Build 492.

Error details on event log are as follows:

Unable to start profiler - exception details System.Exception: The user the ASP.NET process is configured to run under must be different to the currently logged on user

Server stack trace:
at RedGate.Profiler.Engine.ProfileIISController.ᐆ(String )
at RedGate.Profiler.Engine.ProfileIISController.StartProfilingIIS(String currentUserName, String url)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at RedGate.Profiler.Engine.ProfilingSession.StartProfiler()
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage 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 System.Windows.Forms.MethodInvoker.EndInvoke(IAsyncResult result)
at ᐃ.ᐄ(IAsyncResult )

For more information, see Help and Support Center at

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hello,

    The reason for this requirement is that ANTS profiles ASP .NET by enabling profiling for all programs run by the ASP .NET user. If the ASP .NET user is the logged-in user, this enables the profiling API for all programs running on your session, as well as ANTS Profiler itself! This will cause your system to run at a crawl and become practically unusable.

    To get around this, please edit the machine.config (usually in c:\winnt\microsoft.net\framework\v1.1.4322\config) and change the identity of the ASP .NET user to another account, MACHINE, or SYSTEM.
  • Thanks. It solved the problem.
This discussion has been closed.