July 1, 2015 at 12:46 pm
When I start-up SSMS 2014 and make 1st connection to a server, I get the following error message:
The 'Microsoft.Practices.EnterpriseLibraty.Configuration.Design.VisualStudi olntegration2010.VisualStudiolntegration2010Package, Microsoft.Practices.EnterpriseLibraty.Configuration.Design.VisualStudio Integration2010, Version=1.0.0.0, Culture= neutral, PublicKeyToken=null' package did not load correctly.
The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by running the application together with the/log parameter on the command line, and then examining the file 'C:\Users\MY_LOGIN\AppData\Roaming\Microsoft\AppEnv\10.0 ActivityLog.xml'.
Continue to show this error message?
I followed their direction and launched SSMS with /log key, but the XML file is very large - about 1 GB and keeps growing.
Did anybody had similar problem? I re-installed my SSMS from Microsoft site, but the problem still persists.
What should I look in this file for?
July 1, 2015 at 1:20 pm
Don't bother looking in that file, it will only tell you the same thing - that the package failed to load.
You have installed a Visual Studio extension package (it may have been installed by another piece of software), and these are not compatible with SSMS, and yes I would say it is a bug, but it as been present since SQL 2008 and is still there in 2014, so not much chance of a fix.
The only way to stop the error you are seeing (short of a hack) is to remove the extension from SSMS.
Extension packages can be stored pretty much anywhere on the client, but the usual places are in your user profile (%LOCALAPPDATA%)
e.g. C:\Users\mister.magoo\AppData\Local\Microsoft\SQL Server Management Studio\12.0\Extensions
or under the SSMS installation folders
e.g. C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\Extensions
The actual extension folder will be named something absurd like z05we0ea.mff, and you can remove it by simply deleting the folder when SSMS is not running.
**WARNING** Make sure you get the correct folder!!! And back it up first!!! **
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);July 1, 2015 at 2:19 pm
Thanks for quick reply. Here is what I tried to do:
I found that extensions folder is actually installed in SQL Server directory:
C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\Extensions
and it has sub-folder named Application.
It has 30 DLL's, 20 package def's and one xml manifest file named "extention.vsixmanifest". It just lists all pkgdef's in its <content> tag.
Since none of these files looked like '%Visual%Studio%Integration', I moved entire Application folder to another place.
But if I try to start SSMS after that, I get a message "A problem occurred when loading the menu. To fix this problem, run 'Ssms.exe /resetsettings' from the command prompt. Note: this command resets your environment settings."
So I ran it from DOS prompt. But got another message listing all the keys for ssms.exe, but /resetsettings is not among them. And of course it does not start SSMS.
And finally I brought my Application folder back to it's original place and I am again with my initial problem.
July 1, 2015 at 4:10 pm
mister.magoo (7/1/2015)
The actual extension folder will be named something absurd like z05we0ea.mff, and you can remove it by simply deleting the folder when SSMS is not running.**WARNING** Make sure you get the correct folder!!! And back it up first!!! **
That bit was important!
IF the folder doesn't have a weird name and it's in the SSMS installation folder, leave it alone!
If you didn't find any weirdly named folders in either location, then the package may have it's own folder somewhere else.
If you look inside the file ssms.exe.config, there id a node called "probing" right near the start, which has an attribute called privatePath.
Check the value of privatePath, it may include a path to your installed package.
Also check the ssms.pkgdef (open it in notepad), for the values in "PkgDefSearchPath", your software may be in there.
Failing all that, you could just try uninstalling the Microsoft Enterprise Library and reinstalling it, but this time make sure not to include SSMS in the products to install it to.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);July 6, 2015 at 1:26 pm
Thanks for your patience, Mister Magoo.
There was a long holiday weekend, and now I am back to my problem.
If you look inside the file ssms.exe.config, there id a node called "probing" right near the start, which has an attribute called privatePath.
This is what privatePath of probing has. just to be able to read easier, I moved the values from one contiguous line into a column:
probing privatePath=
"Extensions\Application;
IDE\PublicAssemblies;
IDE\PrivateAssemblies;
IDE\ProjectComponents;
IDE\Components;
IDE\CommonExtensions\Microsoft\TemplateProviders;
IDE\PrivateAssemblies\DataCollectors;
IDE\PrivateAssemblies\DataCollectors\x86;
IDE\StartPageAssemblies;
IDE\CommonExtensions\Platform;
IDE\CommonExtensions\Microsoft\Editor;
IDE\CommonExtensions\Platform\Debugger"/>
Since it points to IDE folder, I started to search for this folder on all my drive, and found 9. One is for Microsofet SQL Server/100/, but all the rest for Microsoft Visual Studio 8 | 9.0 |10.0 | 11.0 |, all of them located under parent directory Common7.
Tried to manually find a wierd file name in them, but could not find it.
Also check the ssms.pkgdef (open it in notepad), for the values in "PkgDefSearchPath", your software may be in there.
Here is what it has:
"PkgDefSearchPath" = "$ShellFolder$\Common7\IDE\ShellExtensions;$ShellFolder$\Common7\IDE\CommonExtensions;
I thought that $ShellFolder$ is some kind of a global variable on my PC, but how to find its value? And after all, it points again to Comman7\IDE.
Failing all that, you could just try uninstalling the Microsoft Enterprise Library and reinstalling it, but this time make sure not to include SSMS in the products to install it to.
I have [Microsoft Enterprise Library 5.0 Optional Update 1] and [Microsoft Enterprise Library 5.0 Silverlight Integration pack]. But I am little bit nervous to uninstall it. I also have SSMS 2008 and it's working without any bugs.
July 6, 2015 at 1:51 pm
OK, let's try another way.
Open regedit (usual rules apply - don't change anything) and navigate to:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\XX.0\Packages (where XX is your version number - I think 2014 is 12.0)
Make a note of the Keys (not values) within Packages - they are guids.
Now navigate to
HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\XX.0_Config\Packages
And find each of your Package Guids.
Inside each key there should be a Value called CodeBase which will tell you the location of the DLL being loaded.
One of these should be related to Microsoft.Practices.EnterpriseLibrary.Configuration.Design.VisualStudio Integration2010
Once you have found it and are sure it is correct, you can delete the key from
HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\XX.0_Config\Packages
and
HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\XX.0\Packages
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply