• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3797
  • Last Modified:

Could not load file or assembly 'SqlMgmt, Version=9.0.242.0, Culture=neutral, PublicKeyToken=xxx' or one of its dependencies. Strong name validation failed

I get this error on certain XP Pro machines when trying to run SQL Server Management Studio. Reloading the SQL 2005 application (at least the client tools) usually fixes it for a few runs, then we get it again. Reloading the entire OS fresh (patched to current with SP2) then reloading MS SQL 2005 Developer Editon also doesn't seem to fix it (oddly).

Anyone have any insight into this error? I'm guessing this has to do with the integrity of the dll or its dependencies; I can't imagine what would be going wrong with the files--they are not being altered.

OS: XP Pro SP2
App: MS SQL 2005 Dev Edition

Actual Error copy and paste:

TITLE: Microsoft SQL Server Management Studio

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

 

Failed to open connection dialog.

 

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

ADDITIONAL INFORMATION:

 

Could not load file or assembly 'SqlMgmt, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080xxx...' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) (mscorlib)

 

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

 

Strong name validation failed. (Exception from HRESULT: 0x8013141A)

 

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

BUTTONS:

 

OK

 

 

Could not load file or assembly 'SqlMgmt, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080xxx...' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) (mscorlib)

 

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

Program Location:

 

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.InitializeServiceProvider()

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer..ctor()

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorerPackage.CreateObjectExplorerTool(Guid& toolGuid)

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorerPackage.CreateTool(Guid& toolGuid)

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.SqlServer.Management.UI.VSIntegration.ServiceCache.GetObjectExplorer()

   at Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.AppIDPackage.ConnectToOe()

 

 

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

Program Location:

 

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.InitializeServiceProvider()

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer..ctor()

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorerPackage.CreateObjectExplorerTool(Guid& toolGuid)

   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorerPackage.CreateTool(Guid& toolGuid)

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.SqlServer.Management.UI.VSIntegration.ServiceCache.GetObjectExplorer()

   at Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.AppIDPackage.ConnectToOe()

 

0
rzup
Asked:
rzup
1 Solution
 
MikeWalshCommented:
I have not come across this, and a quick search of the newsgroups doesn't reveal much.. This error seems common with Visual Studio and if you search google for "Strong Named Validation Failed" you will see some of those examples, perhaps one of the solutions help oyu..

I would suggest applying Service Pack 1 (for SQL Server 2005) to your client installation to ensure it is running the latest, this may have been fixed during the SP, perhaps.

0
 
rzupAuthor Commented:
Thanks for the input.

I've seen other articles and posts related to strong validation, and have tried using, for example. the sn.exe utility to check validation. Such attempts haven't worked as of yet. It would be great to understand the issue in enough depth to create a systemic solution that would cover all validation errors. The entire issue is new to me and I understand it pretty much not at all.

In any case, applying the SP does work. Reinstalling the client tools also works--for a while (usually just once). If the SP works tomorrow, I'll consider it solved.

Thanks again.
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now