Home Dashboard Directory Help
Search

The 'TestWindowPackage' package did not load correctly by belflinx


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


11
0
Sign in
to vote
Type: Bug
ID: 776874
Opened: 1/18/2013 1:10:56 AM
Access Restriction: Public
0
Workaround(s)
view
8
User(s) can reproduce this bug

Description

I have Visual Sudtio 2012 Premium installed on a Windows 2008 R2 Standard server.

I was able to create MVC application and a Unit Test project with no problem.

I installed Visual 2012 SP1 and now i am not able to open unit test projects, the following message is displayed
"The 'TestWindowPackage' package did not load correctly" The problem way have been caused by a configuration change or the installation of another extension. You can get more information by examining the file c:\users\username\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.XML

I have had a look at the xml file mentioned above and have included the message below

<entry>
    <record>505</record>
    <time>2013/01/17 09:31:28.236</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>Begin package load [TestWindowPackage]</description>
    <guid>{BFC24BF4-B994-4757-BCDC-1D5D2768BF29}</guid>
</entry>
<entry>
    <record>506</record>
    <time>2013/01/17 09:31:28.272</time>
    <type>Error</type>
    <source>TestWindowPackage</source>
    <description>TestWindowPackage.Initialize failed with exception:System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage.Initialize()</description>
</entry>
<entry>
    <record>507</record>
    <time>2013/01/17 09:31:28.273</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>SetSite failed for package [TestWindowPackage]</description>
    <guid>{BFC24BF4-B994-4757-BCDC-1D5D2768BF29}</guid>
    <hr>80004003 - E_POINTER</hr>
    <errorinfo>Object reference not set to an instance of an object.</errorinfo>
</entry>
<entry>
    <record>508</record>
    <time>2013/01/17 09:31:28.275</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>End package load [TestWindowPackage]</description>
    <guid>{BFC24BF4-B994-4757-BCDC-1D5D2768BF29}</guid>
    <hr>80004003 - E_POINTER</hr>
    <errorinfo>Object reference not set to an instance of an object.</errorinfo>
</entry>

I have tried to create new Solutions with Unit Test Projects and am still getting the same message.

Is there a workaround or solution for this problem.

Jason
Details
Sign in to post a comment.
Posted by Microsoft on 7/22/2013 at 12:21 PM
@severino_can,

Since we have not heard back from you, we assume the issue has been resolved. Please feel free to reopen it if you run into the same problem again.

Thanks,
Oleg Sych
Posted by Microsoft on 7/10/2013 at 8:42 AM
@severino_can

Thank you for reporting the problem. Would you mind providing additional information to help us diagnose it?

* Collect Visual Studio setup logs

    Download collect.exe from http://go.microsoft.com/?LinkId=8967043.
    Run collect.exe and attach the log files it collects in %TEMP%\vslogs.cab to this bug

* Open Developer Command Prompt for Visual Studio 2012, run the following commands, and attach their output to this bug:

    cd %VSINSTALLDIR%
    dir *TestWindow*.dll /s
    cd %localappdata%\Microsoft\VisualStudio\11.0\Extensions
    dir *TestWindow*.dll /s

In the meantime, let’s try to get your Visual Studio working again.

* Run the following command from the Developer Command Prompt. It will delete the MEF composition cache which may have become corrupted.

    rmdir %localappdata%\Microsoft\VisualStudio\11.0\ComponentModelCache /s/q

* From Developer Command Prompt, run the following command

    devenv /log

* If you see errors or problems again, please attach the ActivityLog.xml file (if any) from the following folder to this bug.
    
    %appdata%\Microsoft\VisualStudio\11.0\

If this still does not fix the problem:

* Repair the Visual Studio 2012 installation
* Repair the Visual Studio 2012 Update installation (if you have it installed).
* Restart your computer, if necessary
* Repeat the previous set of steps starting with rmdir

Thanks,
Oleg Sych
Posted by steverino_can on 7/9/2013 at 11:55 AM
Getting this same problem:

279 ERROR TestWindowPackage.Initialize failed with exception: System.InvalidOperationException: Loading MEF components failed with the following exception: The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information. 1) The specified argument cannot be empty. Parameter name: commandContainers Resulting in: An exception occurred while trying to create an instance of type 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer'. Resulting in: Cannot activate part 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer'. Element: Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer --> Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer Resulting in: Cannot get export 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer")' from part 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer'. Element: Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer") --> Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer Resulting in: Cannot set import 'Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer")' on part 'Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage'. Element: Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer") --> Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage Additional diagnostics here: MEF Import details for Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage ContractName Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer RequiredTypeIdentity Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer Satisfied by : Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer") ---> System.ComponentModel.Composition.CompositionException: The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information. 1) The specified argument cannot be empty. Parameter name: commandContainers Resulting in: An exception occurred while trying to create an instance of type 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer'. Resulting in: Cannot activate part 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer'. Element: Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer --> Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer Resulting in: Cannot get export 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer")' from part 'Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer'. Element: Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer") --> Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer Resulting in: Cannot set import 'Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer")' on part 'Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage'. Element: Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage.PackageContainer (ContractName="Microsoft.VisualStudio.TestWindow.VsHost.PackageContainer") --> Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage at System.ComponentModel.Composition.CompositionResult.ThrowOnErrors(AtomicComposition atomicComposition) at System.ComponentModel.Composition.Hosting.ImportEngine.SatisfyImportsOnce(ComposablePart part) at System.ComponentModel.Composition.Hosting.CompositionContainer.SatisfyImportsOnce(ComposablePart part) at System.ComponentModel.Composition.AttributedModelServices.SatisfyImportsOnce(ICompositionService compositionService, Object attributedPart) at Microsoft.VisualStudio.ComponentModelHost.ComponentModelHostExtensions.SatisfyImports[T](T serviceProvider) --- End of inner exception stack trace --- at Microsoft.VisualStudio.ComponentModelHost.ComponentModelHostExtensions.SatisfyImports[T](T serviceProvider) at Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage.InitializeContainer() at Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage.Initialize() PackageContainer loaded: False Certificates do not match: Microsoft.VisualStudio.TestWindow: [Subject] CN=Microsoft Corporation, OU=MOPR, O=Microsoft Corporation, L=Redmond, S=Washington, C=US [Issuer] CN=Microsoft Code Signing PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US [Serial Number] 33000000B011AF0A8BD03B9FDD0001000000B0 [Not Before] 1/24/2013 2:33:39 PM [Not After] 4/24/2014 3:33:39 PM [Thumbprint] 108E2BA23632620C427C570B6D9DB51AC31387FE Microsoft.VisualStudio.ExtensibilityHosting: [Subject] CN=Microsoft Corporation, OU=MOPR, O=Microsoft Corporation, L=Redmond, S=Washington, C=US [Issuer] CN=Microsoft Code Signing PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US [Serial Number] 33000000B011AF0A8BD03B9FDD0001000000B0 [Not Before] 1/24/2013 2:33:39 PM [Not After] 4/24/2014 3:33:39 PM [Thumbprint] 108E2BA23632620C427C570B6D9DB51AC31387FE
Posted by Microsoft on 5/15/2013 at 3:45 PM
The additional attached file did not aid us in reproducing this issue. If you still see problems with this bug please let us know and we can investigate.

Thanks,
Joshua Weber
Posted by Microsoft on 2/25/2013 at 9:08 AM
We were unable to duplicate this problem in our test environment. Please let us know if you are still experiencing the problem.
Posted by Microsoft on 2/4/2013 at 4:51 PM
We are working on duplicating the problem in our environment. In the meantime, could you try uninstalling Update 1, repairing Visual Studio 2012 installation and reinstalling Update 1?
Posted by David Lowndes on 1/31/2013 at 3:00 PM
I've tried those commands too - they've made no difference.
Windows 7.
Posted by ShinyDiscoBall on 1/30/2013 at 6:21 PM
I am also hitting this issue. I tried the following command but to no avail.

del %LocalAppData%\Microsoft\VisualStudio\11.0\ComponentModelCache
devenv /setup

I am running VS 2012 Update 1 on Windows 8. The error pops up everytime I laugh a sln or create a new project. Everytime!
Posted by Microsoft on 1/29/2013 at 1:10 PM
This may be caused by a corruption in the metadata cache Visual Studio maintains for its various components. Could you run the following two steps from the Developer Command Prompt for VS2012 and let us know if this fixed the problem? Please run these commands "As Administrator" to avoid file access errors.

del %LocalAppData%\Microsoft\VisualStudio\11.0\ComponentModelCache
devenv /setup

Thanks,
Oleg Sych
Posted by Microsoft on 1/20/2013 at 5:53 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/18/2013 at 1:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
ActivityLog.xml 4/10/2013 86 KB
ActivityLog.xml 7/17/2013 102 KB
ActivityLog.xml 11/13/2013 297 KB