Outlook Web Access shows as text only after .NET Framework 2.0 update

I have Windows 2003 SBS environment where I recently updated the server and workstations to the .NET Framework 2.0.  Now my Outlook web access shows up as text only instead of the way it was prior to the update.  Any suggestions on how to restore it to what it was?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Make sure that you haven't got the virtual folders set to use .net 2.0 as 1.1 and 2.0 are totally different applications.
Also ensure that anonymous authentication is enabled on the /exchweb virtual directory in IIS manager.

americanmobileAuthor Commented:
where is the location of the virtual folders?  
IIS Manager - as I wrote above.

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

americanmobileAuthor Commented:
I still don't see the location of where to do this at.  I did come across this article, but didn't see where I could change it...


I don't want to make any changes til I am certain I will not disrupt my exchange server.

Am I right clicking and looking for .net?  where?

thanks for the help

That article explains exactly where and what to change.
This KB article explains almost the same thing: http://support.microsoft.com/default.aspx?kbid=883380

Open IIS Manager.
Open the default web site.
Right click on the /exchange virtual directory and choose Properties.
Click on tab for asp.net and ensure that the version number is 1.1 not 2.0.

The installation of asp.net 2.0 should not have caused problems with OWA unless something else was changed or the installation was carried out by another application that is not designed to co-exist with Exchange/OWA. I have 2.0 installed on all of my servers and it has never caused any problems.

americanmobileAuthor Commented:
Thanks.  I went but the tab for .net 2.0 is grayed out but it is on 2.0.  You can click on edit configuration but I still didn't see anything.

Let me give you the background.  They have a piece of medical software that resides on their server called MARS.  any client machine simply goes to the ip address of the server ( and the program runs.  They had use update all the clients to .net 2.0 framework and the server as well.

I right clicked on default website and didn't see /exchange.  I saw 'exchange' with the path \\.\backofficestorage\ddd.net\MBX.  I am assuming that is the exchange you were talking about?
Its on 2.0 and greyed out?
Oh dear, that isn't good. It sounds like their application has changed the default web site and forced the change to all virtual directories. That is very bad practise on the part of the software developer.
Did the supplier of the software use the Microsoft installation for .net framework 2.0 or did they use their own configuration? If this was an update that they supplied then they need to be instructed to fix it.
It wouldn't surprise me if they "recommend" that their software runs on a dedicated server and they are presuming that everyone is doing that.

Asp.net 1.1 and 2.0 should be considered different applications. 2.0 is not backwards compatible with 1.1.
While this may only appear to Affect OWA, it will cause further problems with Exchange. A lot of the public folder management is done through the web interface in the background so you may have issues working with public folders.

I can tell you how to fix the asp.net configuration to allow OWA to work, but it will break whatever is using 2.0.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.