locked
Profiling unit test throws error: WOW64 processes is not supported by this version of the profiling tools RRS feed

  • Question

  • Hi all,

    I'm trying to use Visual Studio 2010 Premium to profile a unit test.

    Last week I tried it, got some low perfomance results and now I wanted to optimize it but suddenly the profiler won't run with the following message:

     WOW64 processes is not supported by this version of the profiling tools.

    I've googled on it but I only found some really old posts about VS 2008/2005. What could be the problem with VS 2010?

    [See http://social.msdn.microsoft.com/Forums/en/vststest/thread/f91c20f0-d04e-4d18-935e-0689c9da0675]

    I looked at the link you gave me.. I understand that WOW64 has something to do with emulating a 32 bit process on a 64 bit machine? I am running Windows 7 64 bit.. Could it have anything to do with my project configuration settings? (any cpu, mixed platforms?) 

    Thanks for your help,

    Wouter de Kort

    Friday, December 3, 2010 7:28 AM

Answers

All replies

  •  

    Hi,

     

    Thank you for your question. We're doing research on this case. It might take some time before we get back to you.


    Sincerely,
    Eric
    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact msdnmg@microsoft.com.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Monday, December 6, 2010 10:25 AM
  • Hi eryang,

     

    thanks for your reply. Do you have any suggestions in the mean time? Would a reinstall do anything?

    i've checked profiling on another machine (32-bit) and that worked... I'll try to check it on another 64bit machine. see if that works..

    Hope you have any workaround in the meantime...

     

    Wouter

    Monday, December 6, 2010 1:46 PM
  •  

    It is a restriction for VSTS 2005 to profile a WOW64 process, but the restriction is not applied to VS 2010.

     

    You mentioned that the profiler works well "last week", right? Do you still remember what changed you made to your project this week? You may create another simple project on the same machine to see whether it can be reproduced.


    Sincerely,
    Eric
    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact msdnmg@microsoft.com.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by eryang Monday, December 27, 2010 2:26 PM
    • Unmarked as answer by WouterdeKortMVP Monday, December 27, 2010 2:27 PM
    Tuesday, December 7, 2010 6:35 AM
  • OK I've tested a few things.

     

    I run the profiler on a unit test on a colleagues machine (also 65 bit, Windows 7) and that works perfect.

    I've also created a new project on my own machine. Added a WCF service project, created a unit test project, added a service reference and used it in a unit test and this also worked perfect. I got a nice report of the profiler.

    So.. the problem is somewhere in the combination of the project and my pc.

    Any idea where to look?

    [Update]

    I've also got a specif version from 2 weeks ago and it gives me the same error. So something else changed in my computer settings..

    Tuesday, December 7, 2010 8:42 AM
  • Please see

    Visual Studio Team System Profiling Tools FAQ

    http://msdn.microsoft.com/en-us/library/dd164415(VS.90).aspx

     

    WOW64 and Your Profiler

     

    http://blogs.msdn.com/b/davbr/archive/2006/11/13/wow64-and-your-profiler.aspx

     

     

    Walkthrough: Command-Line Profiling Using Sampling

     

    http://msdn.microsoft.com/en-us/library/aa985628.aspx

     

    Walkthrough: Command-Line Profiling Using Instrumentation

     

     

    http://msdn.microsoft.com/en-us/library/aa985627.aspx


    bill boyce
    Friday, December 17, 2010 7:35 PM
  • Ok! Things are working again..

     

    I've read the info you gave me and just tried some things. I created a new 'Profiler' configuration with everything set to X86. And that suddenly works.. while analysing the report it shows quite a few 'cannot load symbols' with a windows\syswow64 path..


    I'll have a look if I can fix that (have already configured the symbol server) but at least I can profile my unit tests and my asp.net host application :)

     

    Thanks for your help!

     

    Wouter

    Monday, December 20, 2010 9:25 AM