Ask a questionAsk a question
 

QuestionCannot open source file

  • Tuesday, February 10, 2009 3:47 AMJustin EtheredgeMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    My VM of Visual Studio 2010 was working fine but then all of the sudden any time I try to open a source file I get the error:

    "Exception has been thrown by the target of invocation."

    When I click "ok" nothing happens.

    The only errors in the event log are these two:

    Log Name:      Application
    Source:        TraceLog Profiler
    Date:          12/2/2008 10:39:21 PM
    Event ID:      5
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      VS2010CTP
    Description:
    TraceLog Profiler failed in initialization due to a lack of instrumentation methods, process ConsoleApplication2.vshost.exe
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="TraceLog Profiler" />
        <EventID Qualifiers="58454">5</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-12-03T06:39:21.000Z" />
        <EventRecordID>13937</EventRecordID>
        <Channel>Application</Channel>
        <Computer>VS2010CTP</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ConsoleApplication2.vshost.exe</Data>
        <Binary>00000000</Binary>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        .NET Runtime
    Date:          12/2/2008 10:39:21 PM
    Event ID:      1022
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          VS2010CTP\Administrator
    Computer:      VS2010CTP
    Description:
    .NET Runtime version 4.0.11001.1 - Loading profiler failed.  The profiler COM object was instantiated, but the profiler failed during its initialization callback.  Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'.  HRESULT: 0x80004005.  Process ID (decimal): 5884.  Message ID: [0x2505].
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1022</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-12-03T06:39:21.000Z" />
        <EventRecordID>13938</EventRecordID>
        <Channel>Application</Channel>
        <Computer>VS2010CTP</Computer>
        <Security UserID="S-1-5-21-680025851-272716454-1362934670-500" />
      </System>
      <EventData>
        <Data>.NET Runtime version 4.0.11001.1 - Loading profiler failed.  The profiler COM object was instantiated, but the profiler failed during its initialization callback.  Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'.  HRESULT: 0x80004005.  Process ID (decimal): 5884.  Message ID: [0x2505].</Data>
      </EventData>
    </Event>

    Any ideas?

    Thanks,
    Justin Etheredge

    http://www.codethinked.com

All Replies

  • Wednesday, April 29, 2009 10:51 PMIrmatDen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello all,

    Any news about this issue ? It seems I'm getting the same error, but it has never worked fine (first evening spent with it, so... :))

    * The only things I can open are C# & VB forms in designer (tested various C++, C# & VB projects)
    * When trying to look at code in C# & VB, I get the same error message: "Exception has been thrown by the target of invocation. "
    * When trying to open a C++ code file, the error message is: "The operation could not be completed. "

    Thanks in advance for any suggestions
  • Thursday, April 30, 2009 11:57 PMIrmatDen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Nevermind, I got it "solved" (well, kinda).

    If anyone has the same trouble, here's what I've done: when finished installing the CTP virtual harddrive, I immediatly launched it w/o applying first the setting to disable clock synchronisation. So, I wiped out the extracted vhd, extracted a brand new one, immediatly applied the clock synch fix, and every thing works nicely after this.