Tuesday, February 22, 2011

.NET Runtime version 2.0.50727.3615 - Fatal Execution Engine Error (7A0360B0) (80131506)

Phil's fairly useful blog, Monday, 11 January 2010, Visual Studio 2008 crash using Reporting Services 2008 charts
http://phil-austin.blogspot.com/2010/01/visual-studio-2008-crash-using.html
Seems relevant to my recent .NET Framework crashing issues

In my case Visual Studio 2008 SP1 silently and completely aborts when loading an up until now working Solution (SQL SERVER 2008 SP1, .NET 3.5 SP1, VSTS 2008 Developer, VSTS 2008 Database, TeamExplorer 2008, TFS 2005)
Initially, I crated a blank solution, imported the projects, overwrote the existing solution, bound back to TFS and checked in.
This process seemed to have fixed the issue for a few days, then the crashes started again.

Something new to the environment - SQL SERVER 2008 R2 Express
So we'll strip that out, rebuild the SQL SERVER 2008 Development Ed with Service Packs, SP the VS editions and attempt to move forward.

Even though I'm trying to strip an SQL Server 2008 R2 Express Edition, I found this blog helpful http://sqlblog.com/blogs/aaron_bertrand/archive/2010/10/25/fun-with-software-uninstalling-sql-server-2008-r2-evaluation-edition.aspx
Why?
Because internally the SQL Server 2008 R2 Express Edition is reporting itself to be an Expired Evaluation Edition?
I was required to strip out all 10.5x instances of SQL SERVER 2008 objects, tools, shared components.
Run VS2008 SP1
Run SQL SERVER 2008 Development Ed – added edit existing instances
Run SQL SERVER 2008 SP2