Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

ASP.NET 2.0 Error

  Asked By: Tanya    Date: Apr 09    Category: Sharepoint    Views: 2367

I am working on a sharepoint portal server that is running ASP.nET 1.1
in IIS. This application has been working fine for a few weeks. Last
night some people were on the box and this morning I am getting this

The Windows SharePoint Services virtual server has not been configured
for use with ASP.NET 2.0.xxxxx.0. For more information, please refer to
Knowledge Base article 894903 at http://go.microsoft.com/fwlink/?

I did not try upgrade this server as I don't want to run 2.0 on this
site. Whats more, is that it's saying the WSS site has not been
configured. howeever, this is a portal virtual server not a regular
WSS site. I am not sure what was done to make this change. Any
suggestions on what might have happened or how to fix it? I don't want
to upgrade the virtual server as it's a portal installation.



7 Answers Found

Answer #1    Answered By: Cory Brooks     Answered On: Apr 09

Which version of Sharepoint are you running?

I was advised, by a Microsoft Sharepoint expert, to abort a SQL 2005
Client instal on the Sharepoint server  running Share point 2003 as
it causes problems wiht that version of Share point. We had to
remove ASP.net 2.0 from the server to get things working  properly

Answer #2    Answered By: Ruth George     Answered On: Apr 09

We have had a number of issues where (if more than one version
of .NET is installed on the server) applications, including
SharePoint, are configured to run under one version of .NET but end
up loading assemblies for the other version and failing to run.

We have found that we need to put this in the SharePoint Portal 2003
web.config to prevent any attempt to load .NET 2.0 assemblies:

<supportedRuntime version="v1.1.4322"/>

This seems to be stronger medicine than just setting the ASP.NET
version in IIS manager.

Answer #3    Answered By: Peter Peterson     Answered On: Apr 09

I reset IIS to fix the problem but I will try adding this into the web.config to avoid any future issues.

Answer #4    Answered By: Kalyan Pujari     Answered On: Apr 09

If this is an 03 server  and no other pages are using 2.0, you should
uninstall 2.0 and re-register 1.1.

a. If R2 is installed you will need to uninstall .net 2.0 and re-
register 1.1
To re-configure .net 1.1, run the utility (aspnet_regiis –i) from the
command line on this directory:

Answer #5    Answered By: Isidro Berger     Answered On: Apr 09

I simply reset IIS, like I mentioned in my previous post and it fixed it. I need 2.0 installed on here as the WSS sites are using 2.0. The reason being: We are putting all of our custom webparts at the team site level linked from the portal  to take advantage of 2.0. This allows us to write our webparts using VS 2005 and make them more forward compatible for the 2007 upgrade that is going to take place in early 2007.

Answer #6    Answered By: Schuyler Le     Answered On: Apr 09

This is definitely a best practice. To upgrade to 2007, you will need to
be on WSS SP2 and SPS SP2 too.

Answer #7    Answered By: Kristina Cox     Answered On: Apr 09

I don't know for sure but I'd guess that your friends installed the .NET
Framework 2.0 onto your server. Not to worry, I believe that if you
change the IIS Web Site to use the still installed 1.1 version it should
stop throwing the error.

Didn't find what you were looking for? Find more on ASP.NET 2.0 Error Or get search suggestion and latest updates.