PRF0003: Launch Error: Executable file not found ()

Hello everyone.

I got this error trying to profile an ASP.NET applications with several dependent DLLs. The same things happens in Instrumentation and Sampling. Search for the error code everywhere but it seems noone has got this before!

Hope someone can help me because i cant resolve this issue.

The file witch cant be found is referenced from more than one proyect in the solution. It seems as it cant be found because it was moved before by this same process of launching the profiler or something like that.

I will copy the performance output now:

Profiler started
Instrumenting C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Subsystem\PROSST - Profile\obj\Debug\PROSST.dll in place
Microsoft (R) VSInstr Post-Link Instrumentation 8.0.50727 x86
Warning VSP2013 : Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this.
Copyright (C) Microsoft Corp. All rights reserved.
File to Process:
C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Subsystem\PROSST - Profile\obj\Debug\PROSST.dll --> C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Subsystem\PROSST - Profile\obj\Debug\PROSST.dll
Original file backed up to C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Subsystem\PROSST - Profile\obj\Debug\PROSST.dll.orig
Successfully instrumented file C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Subsystem\PROSST - Profile\obj\Debug\PROSST.dll.
Instrumenting C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Application\WAIAPP - Web Application Interface\obj\Debug\WAIAPP.dll in place
Microsoft (R) VSInstr Post-Link Instrumentation 8.0.50727 x86
Copyright (C) Microsoft Corp. All rights reserved.
File to Process:
C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Application\WAIAPP - Web Application Interface\obj\Debug\WAIAPP.dll --> C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Application\WAIAPP - Web Application Interface\obj\Debug\WAIAPP.dll
Original file backed up to C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Application\WAIAPP - Web Application Interface\obj\Debug\WAIAPP.dll.orig
Successfully instrumented file C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Desarrollo\Application\WAIAPP - Web Application Interface\obj\Debug\WAIAPP.dll.
Warning VSP2013 : Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this.
PRF0003: Launch Error: Executable file not found ().
Collection file exited: C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Performance\Internet Banking061002(2).vsp
Profiler exited
Starting analysis for C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Performance\Internet Banking061002(2).vsp
Warning VSP2702 : 1 Empty processes skipped
Performance report C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Performance\Internet Banking061002(2).vsp contains no data.Completed Analysis for C:\Fuentes\Release Julio 2006 - Migracion y Nominas\Performance\Internet Banking061002(2).vsp
===================== Profiling Complete =====================

Thank you!
Ciencias

[4971 byte] By [Ciencias] at [2007-12-25]
# 1

Ciencias,

We worked very hard to get ASP.net profiling working out of the box with the Visual Studio Team system IDE. However, with ASP.net we occasionally run into a customer scenario where the profiler does not work out of the IDE. To get around this, can you try using the command line tools to profile your ASP.net application? Dave Gray wrote a very good article on doing just this. Check it out here: http://blogs.msdn.com/graycode/articles/AspNetOffRoadProfilingArticle.aspx.

~Ian

IanHuff at 2007-8-31 > top of Msdn Tech,Visual Studio Team System,Visual Studio Performance Tools (Profiler)...

Visual Studio Team System

Site Classified