locked
VS 2013 Native c++ Test Manager fails to initialize RRS feed

  • Question

  • I recently upgraded to Win 8.1 and VS2013 and things were working just fine.

    Then after getting some random automatic Windows update, the test engine won't run. Also the c++ AMP blog samples now generate run time DX errors. So this is what I tried to remedy the problem:

    1) I wiped my system clean and re-installed Windows 8/8.1 with all the updates.

    2) I re-installed VS2013 and checked for updates.

    3) I cleaned my solution and rebuilt.

    It makes no difference. The problems remain.

    Anyone have an idea what is going on?

    Thanks, Ed

    Test Error output

    ---------------------------

    CLR:(C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll) Rejecting native image because native image dependency C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll had a different identity than expected

    *** HR originated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\copyout.cpp, line 1391


    *** HR propagated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\identityauthority.cpp, line 278


    *** HR originated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\copyout.cpp, line 1391


    *** HR propagated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\identityauthority.cpp, line 278

    First-chance exception at 0x00007FF8A266C361 (clr.dll) in vstest.executionengine.exe: 0xC0000005: Access violation reading location 0x00007FF8A4267F38.
    First-chance exception at 0x00007FF8A266C361 (clr.dll) in vstest.executionengine.exe: 0xC0000005: Access violation reading location 0x00007FF8A4267F38.
    The program '[4876] vstest.executionengine.exe' has exited with code 0 (0x0).

    D3D error output with HelloWorld

    -------------------------------------------

    First-chance exception at 0x00007FF8B6B1AB78 in HelloWorld_AMP.exe: Microsoft C++ exception: _com_error at memory location 0x000000775049B060.
    First-chance exception at 0x00007FF8B6B1AB78 in HelloWorld_AMP.exe: Microsoft C++ exception: _com_error at memory location 0x000000775049BD00.
    First-chance exception at 0x00007FF8B6B1AB78 in HelloWorld_AMP.exe: Microsoft C++ exception: _com_error at memory location 0x000000775049BF50.
    GPU Device Created.
    First-chance exception at 0x00007FF8B6B1AB78 (KernelBase.dll) in HelloWorld_AMP.exe: 0x0000A00B (parameters: 0x000000000024D000).
    D3D11 ERROR: ID3D11Device::CreateBuffer: CheckFeatureSupport() API with D3D11_FEATURE_D3D11_OPTIONS1 must report support for MapOnDefaultBuffers for a D3D11_USAGE_DEFAULT Buffer Resource to have CPUAccessFlags set (note that for MapOnDefaultBuffers support, the Device or DeviceContextState must be created with feature level greater or equal to D3D_FEATURE_LEVEL_11_0, and the driver must support it). CPUAccessFlags are currently set to: D3D11_CPU_ACCESS_READ (1), D3D11_CPU_ACCESS_WRITE (1). Feature Level is (D3D_FEATURE_LEVEL_11_1), and MapOnDefaultBuffers is (false). [ STATE_CREATION ERROR #63: CREATEBUFFER_INVALIDCPUACCESSFLAGS]
    First-chance exception at 0x00007FF8B6B1AB78 in HelloWorld_AMP.exe: Microsoft C++ exception: _com_error at memory location 0x000000775049E6D0.
    D3D11 ERROR: ID3D11Device::CreateBuffer: CreateBuffer returning E_INVALIDARG, meaning invalid parameters were passed. [ STATE_CREATION ERROR #69: CREATEBUFFER_INVALIDARG_RETURN]
    The program '[3600] HelloWorld_AMP.exe' has exited with code 0 (0x0).

    Sunday, January 5, 2014 10:00 PM

Answers

  • Hi Barry,

    I performed all your recommended steps. Doing devenv.exe /resetsettings made the mscorlib error go away. Since I wiped the system completely, this seems to imply that I was picking up bad settings from the VisualStudio cloud. If cloud settings are the problem, no amount of re-installing is going to fix the problem.

    Thanks, Ed

    So, this error is now gone:

    CLR:(C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll) Rejecting native image because native image dependency C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll had a different identity than expected

    However the other errors still remain when debugging a unit test:


    *** HR originated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\copyout.cpp, line 1391


    *** HR propagated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\identityauthority.cpp, line 278


    *** HR originated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\copyout.cpp, line 1391


    *** HR propagated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\identityauthority.cpp, line 278

    First-chance exception at 0x00007FFF0CC1C361 (clr.dll) in vstest.executionengine.exe: 0xC0000005: Access violation reading location 0x00007FFF093E7F38.
    First-chance exception at 0x00007FFF0CC1C361 (clr.dll) in vstest.executionengine.exe: 0xC0000005: Access violation reading location 0x00007FFF093E7F38.
    The program '[332] vstest.executionengine.exe' has exited with code 0 (0x0).

    I uninstalled VS2013, cleared all of the logs and temp files, rebooted, then re-installed.

    Link to new vslogs file

    https://skydrive.live.com/redir?resid=5BD22A6C6E512640!11449&authkey=!AHhgHp14275ZcNc&ithint=file%2c.cab

    Update:

    I wiped the system clean again. Installed Win 8/8.1 with updates, but did not use a Windows online account. I used a local account. I installed VS2013 from a downloaded version and did not use the online Microsoft account. I was trying to isolate it from any possible cloud influences. I disconnected my ethernet during installation to ensure no hidden connections. There was no effect, the problems are identical and still remain. The AMP Direct X problem could have possibly had something to do with my graphics card even though I am using the certified driver from Microsoft. However, creating a simple empty native C++ unit test and debugging it causes the same errors listed above. I don't see how that could have anything to do with my hardware configuration. This appears to be a pure and simple installation problem.

    Update:

    I just installed VS2013 SP1. There CLR errors are still being spewed out, but at least now the access violations are fixed and my tests run again.

     

    • Edited by ewconnell Sunday, January 26, 2014 4:06 AM Problem mostly solved
    • Marked as answer by ewconnell Sunday, January 26, 2014 4:06 AM
    Tuesday, January 7, 2014 5:35 PM

All replies

  • Hi,

    Please use http://aka.ms/vscollect  to gather the installation logs. After using it, you will find vslogs.cab from %temp% folder. Please upload the file to https://skydrive.live.com/   and share the link here.

    Best regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, January 6, 2014 9:58 AM
  • Hi Amanda, thank you for your reply. Here is the link to the vslogs.cab file

    https://skydrive.live.com/redir?resid=5BD22A6C6E512640!11447&authkey=!ANqTPXB1ue2lRSQ&ithint=file%2c.cab

    Monday, January 6, 2014 12:32 PM
  • Hi,

    There are some installation errors in log.We are moving this threa dto Visual Studio Setup and installation forum for better response.

    Best regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, January 7, 2014 1:57 AM
  • Hi ewconnell,

    I checked your logs and find the following:

    Error 0x80070103: Failed to find product code for given upgrade code.

    Could you please check this page http://support.microsoft.com/kb/952032

    It seems you haven't patched up your OS when you installed Visual Studio 2013 which caused the problem. Please refer to that page to updates first.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, January 7, 2014 2:31 AM
  • The article you reference appears to recommend that all the drivers need to be up to date.

    I followed the normal Windows 8/8.1, and VS install procedures. I ran Windows Update and it says that everything is up to date.

    What OS patching are you referring to?

    Specifically what do you want me to do to fix this problem?

    Thank you, Ed

    Tuesday, January 7, 2014 2:39 AM
  • Hi Ed,

    The error is related to the your installation on 1.5 but not now. In my mind, the problem is already there before your update your OS.

    So let's try the following possible workaround to fix:

    1. Try repair by re-run your setup. (I didn't see you've choosed this option, you can give it a try)

    2. Try reset VS using some of the following commands:

    -------------------------------------------------------------

    "Please open an administrative CMD window and navigate to C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE and run these commands:

    1.devenv.exe  /safemode

    2.devenv.exe  /resetskippkgs

    3.devenv.exe  /installvstemplates

    4.devenv.exe  /resetsettings

    5.devenv.exe  /resetuserdata 

    Note that the above steps are unrelated and so checking if your issue has been resolved, after every step may help you save time on steps that were not required!

    Please rename these 2 registry keys under the registry editor:

    HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config

    HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0

    "

    ------------------------------------------------------------------------

    If you have problem run the command, just try drag or type in the devenv.exe to your run prompt, like the following:

    "E:\Visual Studio 2013\Common7\IDE\devenv.exe" /resetuserdata

    3. If the problem cannot be solved, It seems you have tried reinstalled your OS before. So you don't mind to reinstall your OS again to fix this issue?(I always avoid using this because you may think it is so complex and annoying). The right steps should be like the following:

    a. Reinstall your OS

    b. Patched up

    c. Install VS.

    However you don't need to do this at this time, I still cannot be sure if it is Update issue or installation issue. If repair and reset doesn't work, please just clear your %temp% folder and reinstall VS then share your log a second time.(I need to check whether your problem is pending on installation or any updates). If the installation is OK. I will help you check which update caused the problem and report it for you to get some help.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.




    • Edited by Barry Wang Tuesday, January 7, 2014 3:02 AM
    Tuesday, January 7, 2014 3:00 AM
  • Hi Barry,

    I performed all your recommended steps. Doing devenv.exe /resetsettings made the mscorlib error go away. Since I wiped the system completely, this seems to imply that I was picking up bad settings from the VisualStudio cloud. If cloud settings are the problem, no amount of re-installing is going to fix the problem.

    Thanks, Ed

    So, this error is now gone:

    CLR:(C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll) Rejecting native image because native image dependency C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll had a different identity than expected

    However the other errors still remain when debugging a unit test:


    *** HR originated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\copyout.cpp, line 1391


    *** HR propagated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\identityauthority.cpp, line 278


    *** HR originated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\copyout.cpp, line 1391


    *** HR propagated: -2147024774
    ***   Source File: d:\iso_whid\amd64fre\base\isolation\com\identityauthority.cpp, line 278

    First-chance exception at 0x00007FFF0CC1C361 (clr.dll) in vstest.executionengine.exe: 0xC0000005: Access violation reading location 0x00007FFF093E7F38.
    First-chance exception at 0x00007FFF0CC1C361 (clr.dll) in vstest.executionengine.exe: 0xC0000005: Access violation reading location 0x00007FFF093E7F38.
    The program '[332] vstest.executionengine.exe' has exited with code 0 (0x0).

    I uninstalled VS2013, cleared all of the logs and temp files, rebooted, then re-installed.

    Link to new vslogs file

    https://skydrive.live.com/redir?resid=5BD22A6C6E512640!11449&authkey=!AHhgHp14275ZcNc&ithint=file%2c.cab

    Update:

    I wiped the system clean again. Installed Win 8/8.1 with updates, but did not use a Windows online account. I used a local account. I installed VS2013 from a downloaded version and did not use the online Microsoft account. I was trying to isolate it from any possible cloud influences. I disconnected my ethernet during installation to ensure no hidden connections. There was no effect, the problems are identical and still remain. The AMP Direct X problem could have possibly had something to do with my graphics card even though I am using the certified driver from Microsoft. However, creating a simple empty native C++ unit test and debugging it causes the same errors listed above. I don't see how that could have anything to do with my hardware configuration. This appears to be a pure and simple installation problem.

    Update:

    I just installed VS2013 SP1. There CLR errors are still being spewed out, but at least now the access violations are fixed and my tests run again.

     

    • Edited by ewconnell Sunday, January 26, 2014 4:06 AM Problem mostly solved
    • Marked as answer by ewconnell Sunday, January 26, 2014 4:06 AM
    Tuesday, January 7, 2014 5:35 PM