More often than not, when I run a Performance Session, I get a small dialog box that says:
Launch Error
PRF0025: No data was collected.
However, the session does create a .vsp file that I can then add to the Performance Explorer and view the report. Is this a known issue, or am I doing something wrong
Thanks,
Bob Willer
BetaID 267513

Launch Error, no data was collected
mrlittlejon
There is no other error messages in the output window. I have copied & pasted the output window below. Yes, the report data looks *somewhat* correct. I say *somewhat* because the call tree doesn't go any deeper than 1 branch, however the Allocation and Obects Lifetime pages are all appear to be fully populated.
It was done using instrumentation, however, I get the same error box using sampling. The solution is a small project (6 class library projects, 1 unit test project, 1 windows form project, and a console app that is calling the class library functions. The console app is the app that is being profiled)
Running Beta 2, Windows XP Pro SP 2. However, it is NOT a clean install of Beta 2 as I had the December CTP installed, but removed it before installing. Over the next day or two I will try it on a clean install when I get another machine available.
If there is anything else I can help with, let me know.
Bob Willer
BetaID 267513
Output Window:
(Note: I removed my file names & paths and replaced them with 'MyApp')
==========================================================
Profiler started
Instrumenting C:\Myapp.Performance.exe in place
Microsoft (R) VSInstr Post-Link Instrumentation 8.0.50215 x86
Copyright (C) Microsoft Corp. All rights reserved.
File to Process:
C:\MyApp.Performance.exe --> C:\MyApp.Performance.exe
Original file backed up to C:\MyApp.Performance.orig.exe
Successfully instrumented file C:\MyApp.Performance.exe.
Successfully attached to process: 3280
Exited from process: 3280
Collection file exited: C:\MyApp050426.Performance.vsp
Profiler exited
PRF0025: No data was collected.
===================== Profiling Complete =====================
rdb
Are there other error messages in the output window Does the data in the report look correct Was this in sampling or instrumentation mode
Any other details you can provide about your scenario would be helpful for us tracking down a repro case.
Marc
jimschor
Patrick, are you running in sampling or instrumentation mode
Do you get the same problem with memory allocation collection turned off
Does the data look valid when you open the report (the data looked somewhat valid to Bob)
Have you tried the scenario on the command line
What language are you using
I'm trying to narrow down the sorts of scenarios that this problem seems to be happening on so we can better target a repro.
Thanks for any details you can provide.
Marc
CsharperNow
You are lucky today. I'm having the samen problem here. I'm running a heavy memory load network thread in Performance Explorer.
Feper
Bob:
Thanks for your more detailed information. Unfortunately, we still haven't been able to get a repro for the problem you've run into.
Have you tried instrumenting a simpler windows application (ie no dlls)
Have you tried running the instrumented version of the application from the command line to see if there is an error we are just not seeing (on that same note, check the application event log to see if there are any errors there)
Are you using signed binaries (instrumentation breaks signing so they need to be resigned)
Have you tried the whole scenario from the command line
Have you had any success with a clean machine
Hopefully we can try to narrow down what the problem is to better identify it. Thanks for you feedback.
Marc