Jaa


SSMS Error “HRESULT: 0x80131040” encountered while opening a Table in Design-View

Hello,

April 09, has lot more than expected. During my usual stuff, I was trying to open a table in “Design” view, I got this error

TITLE: Microsoft SQL Server Management Studio ------------------------------

The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (SQLEditors)

Analysis:

Started my search on the ERROR, and I found a Blog-Link. This explains that “Error is encountered when we try to open a table with SQL Server Management Studio 2005 after installing SQL Server 2008 (Katmai - CTP November 2007) for testing purposes on the same machine.”

However, it’s been ages that SQL2K5 and SQL2K8 been working fine on my machine. I then verified the solutions steps. It suggests to rebuild SQL Server 2005 Registry by running setup from command prompt. As this needs downtime, I was eager to explore alternate options.

Solution Steps:

There are few things specific to my box:

  • I have SQL 2005 and SQL 2008 both installed on same server

MSDN Link ASP.NET IIS Registration Tool explains “When multiple versions of the .NET Framework are executing side-by-side on a single computer, the ASP.NET ISAPI version mapped to an ASP.NET application determines which version of the common language runtime (CLR) is used for the application. The ASP.NET IIS Registration Tool (Aspnet_regiis.exe) allows an administrator or installation program to easily update the script maps for an ASP.NET application to point to the ASP.NET ISAPI version that is associated with the tool”

Ran Below command:

aspnet_regiis –i

  • The command installs the ASP.NET version that is associated with the ASP.NET IIS Registration tool and updates the script maps of all existing ASP.NET applications.
  • Note that only applications that are currently mapped to an earlier version of ASP.NET are affected.

The Table “Design” view is fine again and I’m sorted :)

Disclaimer: I work at Microsoft. Everything here, though, is my personal opinion and is not read or approved by Microsoft before it is posted. No warranties or other guarantees will be offered as to the quality of the opinions or anything else offered here.

Comments