Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Site down with .NET 2.0 error

  Asked By: Alyssa    Date: Jun 24    Category: Sharepoint    Views: 1383

we have a SPS 2003 (SP2) small server farm that uses SQL 2005. I
installed SQL 2005 client tools to be able to use SPS backup and
restore tool. After installing this, at random times, the site errors
out that 'WSS is configured to use .NET 2.0 and is not supported'. The
event log has the following event:
Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1,
faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec,
debug? 0, fault address 0x000e9f96.

I am not planning to backup and restore using SQL backup and restore
any way, so, Is it safe to uninstall SQL 2005 client tools and
then .NET 2.0 framework from the server?
Did any one had this same issue and resolved? Please help!



8 Answers Found

Answer #1    Answered By: Tejaswani Barve     Answered On: Jun 24

Are you running .NET 2.0 in your SPS 2003 Web Application? If so, switch back to .NET 1.1 because SPS2003 SP2 does not support .NET 2.0… only WSS v2 SP2 supports .NET 2.0.

Did you also install WSS SP2 before SPS SP2?

Answer #2    Answered By: Harshita Padwal     Answered On: Jun 24

IIS web site  is runnign on .NET 1.1 only.
I installed WSS SP2 before SPS SP2 (its been a while, I am sure I did
the right order).
.NET 2.0 is installed by SQL 2005 client tool installation.

Answer #3    Answered By: Jennifer Jones     Answered On: Jun 24

Make sure the Web applications within the IIS Web site  within the portal are also .NET 1.1… somewhere it’s using .NET 2.0. I’d try to locate that and then work your way back.

Answer #4    Answered By: Annie Norris     Answered On: Jun 24

We had an issue in our environment where SPS would complain about
running under .NET 2.0 even though every application in the site  was
configured for .NET 1.1 in IIS. Apparently what can happen is that
during its search for assemblies it can sometimes come across a .NET
2.0 version and try to load it, despite the IIS setting.

The workaround is to add a setting in web.config to force it to load
only 1.1 assemblies.

Answer #5    Answered By: Chadd Hahn     Answered On: Jun 24

We are having a similar issue with our environment and I am working
with our Microsoft TAM to try and get this resolved. We never had a
problem with it until we upgraded recently our 2003 Portal
environment to SP2. Can you post the web.config settings that force
it to use 1.1? I've looked on the web and can only find use of
somthing like:

<requiredRuntime version="v1.1.4322"/>

Will something like that work?

Answer #6    Answered By: Jaime Weaver     Answered On: Jun 24

Look in IIS… when you install the 2.0 FX it adds a new tab “ASP.NET” to the properties dialog of each Web site/Web application. You want to make sure it’s set to 1.1 and not 2.0.

Answer #7    Answered By: Anibal Baird     Answered On: Jun 24

this issue arises because the setting in the properties
dialog in IIS is not always 100% effective.

Answer #8    Answered By: Karla Morrison     Answered On: Jun 24

I wish it were that simple. The ASP.NET tab says 1.1.

Didn't find what you were looking for? Find more on Site down with .NET 2.0 error Or get search suggestion and latest updates.