Solved

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

Posted on 2007-04-11
7
268 Views
Last Modified: 2010-04-18
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?
0
Comment
Question by:americanmobile
  • 4
  • 3
7 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 18892347
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.

Simon.
0
 

Author Comment

by:americanmobile
ID: 18892453
where is the location of the virtual folders?  
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18893452
IIS Manager - as I wrote above.

Simon.
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

Author Comment

by:americanmobile
ID: 18895648
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...

http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permissions-Exchange-2003.html

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

0
 
LVL 104

Expert Comment

by:Sembee
ID: 18897011
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.

Simon.
0
 

Author Comment

by:americanmobile
ID: 18897427
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 (192.168.69.2/#) 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?
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 18897490
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.

Simon.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now