Thread aborted when profiling ASPNET app

Code and memory profiling for .NET developers.

Moderators: Brian Donahue, richardjm, StephenC

Thread aborted when profiling ASPNET app

Postby nfallon » Tue Jan 20, 2009 5:25 pm

I'm trying to profile my ASP.NET app and am getting a "Thead aborted" error in the browser only when I'm using the Profiler.


Can I see a log from the Profiler or something to show where it's failed?

Interestingly a different version of my app does profile successfully. The difference between the 2 is that one makes calls to an Assembly
generated by ourselves, could it be possible the Profiler cannot work with our custom Assembly. The Assembly itself was written directly from our own custom compiler.

My Event Log shows the following:
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 20/01/2009
Time: 16:03:07
User: N/A
Computer: MYPC
Description:
Event code: 3001
Event message: The request has been aborted.
Event time: 1/20/2009 4:03:07 PM
Event time (UTC): 1/20/2009 4:03:07 PM
Event ID: 60a9ae1462de4799b787962ee83ebba7
Event sequence: 28
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/ROOT/server-2-128769407589635458
Trust level: Full
Application Virtual Path: /server
Application Path: c:\\inetpub\\wwwroot\\server\\
Machine name: MYPC

Process information:
Process ID: 1392
Process name: aspnet_wp.exe
Account name: MYPC\\ASPNET

Exception information:
Exception type: HttpException
Exception message: Request timed out.

Request information:
Request URL: http://localhost/server/aspx/app.aspx?EncCode=E
Request path: /server/aspx/app.aspx
User host address: 127.0.0.1
User: logonTicket
Is authenticated: True
Authentication Type: Forms
Thread account name: MYPC\\ASPNET

Thread information:
Thread ID: 1
Thread account name: MYPC\\ASPNET
Is impersonating: False
Stack trace:


Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

nfallon
 
Posts: 1
Joined: Tue Jan 20, 2009 5:17 pm

Postby Brian Donahue » Thu Jan 22, 2009 6:08 pm

I can't say for sure what's happening based on the evidence, but I would look into security -- maybe when you are profiling the security environment makes it impossible to load your assembly into the application.

ANTS Profiler launches ASP .NET applications in IIS under the SYSTEM account, so this account would need read access to the folder containing your assembly.

Alternatively you can use the Development Web Server option, which runs as your desktop login, or change the identity of the "ANTS Performance Profiler Service" or "ANTS Memory Profiler Service" in the services control panel. That will make the web application start as the user you specify instead of SYSTEM.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am


Return to ANTS Profiler Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests