Registered users    
MembershipMembership:
Latest New UserLatest:chris reilly
New TodayNew Today:9
New YesterdayNew Yesterday:8
User CountOverall:23336
Private messaging    
You must be logged in to use this module.
Top 10 posters    
NamePosts
Mariette Knap12900
Marina Roos12523
Eriq Neale2114
Michael Patrick1913
Stan Guinn1913
Robert Pearman1771
Nick Pieters1425
Stewart Brown617
william warren601
Kevin D.579
Welcome unauthorized visitor    
If you want to join us in the discussions on this forum you need to register first. Registration is free! If you are already a registered user please login to join the forum.
Small Business Server Support Forum    
Forums > Microsoft Small Business Server 2003 & 2000 > Exchange Server 2003
Subject: OWA and ActiveSync broken with ASP.NET 2.0
Prev Next
You are not authorized to post a reply.

Author Messages
Edgar Torres User is Offline
United States
Member since
11/13/2007

Registered Users
Posts: 8
11/13/2007 04:31 AM  
Folks, I've been going through tens of forums on numerous websites, so I apologize if I missed a post in this forum, but my OWA and ActiveSync have stopped working, so I'm a bit stressed about it.  I'd appreciate any assistance you can provide.
 
Not realizing that SBS2003 websites apparently require APS.NET 1.1, I created an ASP.NET 2.0 master page.  When I installed the master page to my website, I [naturally] specified ASP.NET 2.0 under the default website's properties.  Needless to say, my companyweb stopped working and pointed me to http://support.microsoft.com/?id=894903, which quickly instructed me to configure my site for ASP.NET 2.0.  After following the directions in the article, companyweb started working, but OWA and ActiveSync broke.
 
I've tried setting all the sites back to ASP.NET, but something is still missing, because the virtual sites are still not working.  Is there any way to reset the websites, without rebuilding the server?
 
I'm unable to uninstall ASP.NET 2.0, because "...it might affect other applications that are installed."  I've tried re-running the Email and Internet Connection Wizard, but it hasn't helped.
 
Is there any way to undo the effects of that damn STSADM -o -upgrade -forceupgrade command?
 
Please folks, ANY help would be greatly appreciated!
Marina Roos User is Offline
The Netherlands
Member since
3/24/2005

Microsoft MVP
Posts: 12523
8/30/2008 07:09 PM  
Hi Edgar,

Did you figure this out yet?
Marina Roos Smallbizserver.Net AdministratorMission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local  network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain'
Edgar Torres User is Offline
United States
Member since
11/13/2007

Registered Users
Posts: 8
9/01/2008 12:38 AM  
Hi, Marina, i don't believe I did. (This was quite some time ago.) I am currently up and running, but I don't think I was able to figure it out. I think I may have simply rebuilt the entire server. (I've done this several times, over the course of the past few years, so I'd written a document that captures all of my post-installation configurations, so I've got the rebuild process down to just a few hours.)

Do you have a solution, or were you just looking for input?
Marina Roos User is Offline
The Netherlands
Member since
3/24/2005

Microsoft MVP
Posts: 12523
9/01/2008 05:16 PM  
Hi Edgar,
 
You must make sure that the SBS websites are using .Net 1 and not .Net 2.
Marina Roos Smallbizserver.Net AdministratorMission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local  network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain'
Edgar Torres User is Offline
United States
Member since
11/13/2007

Registered Users
Posts: 8
9/01/2008 05:19 PM  
LOL Yeah, I sort of figured that out a long time ago. :-) I am eagerly awaiting the November 12th release of Cougar (SBS2008). Do you know if Cougar will have the same limitation, or will I be able to develop into the main site with ASP.Net2 or 3?
Marina Roos User is Offline
The Netherlands
Member since
3/24/2005

Microsoft MVP
Posts: 12523
9/01/2008 05:42 PM  
Hi Edgar,
 
You can use .Net2 or .Net3, as long as you make sure that the SBS websites stay on .Net1.
Marina Roos Smallbizserver.Net AdministratorMission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local  network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain'
Edgar Torres User is Offline
United States
Member since
11/13/2007

Registered Users
Posts: 8
9/01/2008 06:32 PM  
Really? Even with SBS2008, we'll have to keep the main site on .Net1? Interesting that Microsoft didn't lift that limitation, especially considering that we now have .NET35. Thanks for the info...
Marina Roos User is Offline
The Netherlands
Member since
3/24/2005

Microsoft MVP
Posts: 12523
9/01/2008 06:35 PM  
Hi Edgar,
 
I was talking about SBS 2003, not 2008.
Marina Roos Smallbizserver.Net AdministratorMission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local  network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain'
Matt Enderle User is Offline
United States
Member since
8/12/2008

Registered Users
Posts: 24
9/03/2008 03:47 AM  
I have been having to deal with this recently with several clients (SBS and Standard 03) with the new iPhone 3G activesync release. I have solved the problem following these instructions.

http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html

You are not authorized to post a reply.
Forums > Microsoft Small Business Server 2003 & 2000 > Exchange Server 2003 > OWA and ActiveSync broken with ASP.NET 2.0


ActiveForums 3.7
Forum policy    
These Discussion Forums are dedicated to the discussion of the Small Business Server and related server and client software. For the benefit of the community please observe the following posting guidelines:
  1. No Advertising. This includes promotion of commercial products and non-commercial products which are not directly related to Small Business Server and related server and client software.
  2. No Flaming or Trolling.
  3. No Profanity, Racism, or Prejudice.
  4. Site Moderators have the final word on approving/removing a thread or post or comment.
Copyright 2002-2008 Concentrix b.v.    :   Page generated in 0.3281271 seconds.   :   Terms Of Use   :   Privacy Statement