receiving Web part errors following an upgrade to .net 2.0

I have upgraded my Windows 2003 SBS to .net 2.0.
Following the upgrade i get the following error message "Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists" any page I try to goto on my "companyweb" site.

If I change the ASP.NET version on my companyweb virtual service in IIS I get an error about not being able to run two different .net versions on the same server
ivolachAsked:
Who is Participating?
 
Jeffrey Kane - TechSoEasyConnect With a Mentor Principal ConsultantCommented:
Sorry, I totally clipped the command line in my initial comment to you.  

The command to run is

C:\>WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

Please try running that and see if it resolves your problem.  If it doesn't, run it with a -r instead of -i, and then follow that by running it again with the -i switch.

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
.NET 2.0 is not an "UPGRADE" to .NET 1.1, so did you install it for a particular application you added to your server?

Because none of the default SBS web sites are able to run on .NET 2.0.

If you don't have any need for it, uninstall it, and then you must re-register .NET 1.1 by running the following command:

C:\>WINDOWS\Microsoft.NET\Framework\v1.1.4322\  -i


Jeff
TechSoEasy

0
 
ivolachAuthor Commented:
I have installed it and registered it.
I have an application that does need it and when I have tried to run that application in .net 2.0 and the rest in .NET 1.1 I kept getting the error message that I can not run two different .net versions on the same server process.

At the moment, except for sharepoint, all the other default SBS web sites seems to be working fine.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If you need to be running .NET 2.0, then you create a separate Application Pool for that site.  You can't mix 1.1 and 2.0 in the same Application Pool.

Jeff
TechSoEasy
0
 
ivolachAuthor Commented:
Thank you Jeff
I have created a separate application pool and a new virutal server rather than creating virutal directory for the application yet I am still getting the error message

Igal
0
 
ivolachAuthor Commented:
I have gone through the whole suggested process and everything is working now.

Thanks
0
All Courses

From novice to tech pro — start learning today.