dotTrace fails to start profiling IIS WCF service, "The system cannot find the file specified"

After following advice to add read access for IIS users, still cannot start the profiler.

"Failed to start profiling: Can't start profiling.  Details:

Can't attach profiler

[location] = C:\Build Agent\work\f532b5455ffc19e9\Profiler\Kernel\Windows\Native\Solution\attach_helper\src\attach_to_process.cpp(44)

[function] = void __cdecl jetbrains::profiler::attach_helper::commands::attach_to_process( const struct jetbrains::profiler::attach_helper::commands::attach_params &)

[hresult] = 80070002, COR_E_FILTENOTFOUND, The system cannot find the file specified."

Any advice?




This issue can be caused by missing IIS components. Could you please check if "ASP.NET 3.5" and "ASP.NET 4.5/4.6" components are installed on your machine?


Thank you for the reply.

This is Windows Server 2008 R2.  .NET Framework 3.5.1 is installed via features, and Microsoft .NET Framework 4.6.1 shows as installed via the Programs and Features Control Panel.


I see. A few more questions:

- Did you try to restart IIS/the computer?

- Don't you run your application under debugger?


Hi Konstantin,

   I did try to restart the system.

   This is a deployment on our dev servers that we are working on.  Locally we can run in a debugger, but we are trying to track down performance issues that do not occur on our local machines.  

   dotTrace can profile in this manner, correct?

   Thanks for your assistance!



It may also be relevant that this service communicates via the nettcp binding, and we need to keep it that way.  We cannot implement http in this scenario.



Yes, dotTrace can profile applications on any machine, if they are not running under debugger and there are no other running profilers or monitoring tools.

It looks like there are some issues with detecting .NET processes on this server. Is it possible to perform a remote debugging session? Our developer will connect to your machine via TeamViewer and try to find out what causes the problem. All operations we perform will be under your full control. Also we can sign an NDA, if needed. Is it okay for you? If so, could you please create a support ticket ("Submit a request" button in the upper right corner)?


Thank you Konstantin,

   We are very interested in pursuing the path mentioned above.  I am submitting a support ticket to get things rolling, thanks kindly!


I had the same problem on localhost IIS Express but I got it to work.

The root cause in my case is that I tried to attach to an IIS Express process before it had a chance to serve an ASP.NET request. I don't know exactly what's going on under the hood with IIS Express and ASP.NET, but it could be that the ASP.NET app isn't even running until you make a request that exercises some ASP.NET code, be it a webform, an MVC controller, a .svc endpoint, an .ashx handler, etc.

My solution was to do things in this order:

  1. Start IIS Express (if not started already)
  2. Important -- make an ASP.NET request, i.e. an aspx page, an MVC request, a WCF service, an asmx service, etc.
  3. Use dotTrace to attach to the process. It should work at this point.

Please sign in to leave a comment.