TechTalkz.com Home

Go Back   Windows Help & Support > Windows Server
Home Register Forum Rules FAQ User Blogs Gallery

Configuring OWA on SBS 2003

Windows Server


Reply
 
LinkBack Thread Tools Display Modes
Old 05-20-2009, 11:30 PM   #11
Duncan McC
Guest
 
Posts: n/a
Default Re: Configuring OWA on SBS 2003

You may have to stop and re-start the Default website, for the 1.1
changes to be in effect. However, it does use (and needs to be) .NET
1.1.xx

--
Duncan

In article <#znsuLZ2JHA.3476@TK2MSFTNGP05.phx.gbl>, "Michael Salamone"
<mikesa_at_entrek_dot_com> says...
> FYI I broke my website by setting ASP.NET version to 1.1. So if that's a
> hard requirement for OWA to work, do I need to set up some new virtual
> directory (for either my website or OWA)?
>
> Thanks,
> Mike
>
>
> "Michael Salamone" <mikesa_at_entrek_dot_com> wrote in message
> news:%23nCN9wV2JHA.5772@TK2MSFTNGP02.phx.gbl...
> > Ok - did that. Still showing version 2.something in the new error
> > messages I'm getting from the browser (which I'll post in reply to Robbins
> > reply).
> >
> > I went one level deeper to ExchWeb (and a few others) which have
> > 2.something for ASP.NET and it's grayed out - can't change it.
> >
> > I went as far to reboot the server (sorry to the person who was in the
> > middle of 2GB transfer!) but still the same (1.1 setting for the Default
> > Web Site and 2.something grayed out for ExchWeb and a few others.
> >
> > Mike
> >
> > "Duncan McC" <hard@work.ok> wrote in message
> > news:MPG.247eac12d52602bd989a5f@news.microsoft.com ...
> >> Start the IIS Admin MMC console and drill into the Default Web Site.
> >>
> >> On that, go into it's properties. Click the ASP.NET tab, and change the
> >> .NET version to 1.1*** (not 2) in the drop down list.
> >>
> >> --
> >> Duncan
> >>
> >> In article <#qFozzQ2JHA.4412@TK2MSFTNGP06.phx.gbl>, "Michael Salamone"
> >> <mikesa_at_entrek_dot_com> says...
> >>> "Michael Salamone" <mikesa_at_entrek_dot_com> wrote in message
> >>> news:eQo6GlQ2JHA.1372@TK2MSFTNGP05.phx.gbl...
> >>> > "Lanwench [MVP - Exchange]"
> >>> > <lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in
> >>> > message news:uIeLinO2JHA.1416@TK2MSFTNGP04.phx.gbl...
> >>> >> Michael Salamone <mikesa_at_entrek_dot_com> wrote:
> >>> >>> When I browse to https://mysbsipaddr/exchange, I get "There is a
> >>> >>> problem with this website's security certificate." page.
> >>> >>>
> >>> >>> Then I click "Continue to this website (not recommended)" and get a
> >>> >>> "The page cannot be found" error.
> >>> >>>
> >>> >>> This happens from internal workstation, external (outside the
> >>> >>> firewall), and from the SBS server itself. It's never worked in the
> >>> >>> past from external workstation, but I *think* I've seen it work
> >>> >>> (albeit months and months and months ago) from internal workstation
> >>> >>> and from the server, but not sure what's changed there.
> >>> >>>
> >>> >>> I did follow the steps from this KB article:
> >>> >>> http://support.microsoft.com/default.aspx/kb/259240. For step 8 re:
> >>> >>> ephemeral ports, I followed the instructions here:
> >>> >>> http://support.microsoft.com/kb/812873. There were already a few
> >>> >>> reserved ports in the 1024-65535 range. I left those there, so
> >>> >>> after
> >>> >>> my change, the registry value looks like this:
> >>> >>>
> >>> >>> 1433-1434
> >>> >>> 3343-3343
> >>> >>> 1024-65535
> >>> >>>
> >>> >>> That ok?
> >>> >>>
> >>> >>> I also opened up port 443 for https.
> >>> >>>
> >>> >>> Any help?
> >>> >>>
> >>> >>> Thanks,
> >>> >>> Mike
> >>> >>
> >>> >> You don't need to do any of that other than opening up port 443. Use
> >>> >> the
> >>> >> SBS wizards. Run the CEICW to configure all of this.
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> > Thanks - I saw in some help that I should run the CEICW wizard but I
> >>> > was
> >>> > worried it would muck up something that's already configured and
> >>> > working
> >>> > (like DNS and Exchange notwithstanding the OWA issue I'm having).
> >>> >
> >>> > I ran it anyway. I told it to skip configuring the firewall. It
> >>> > failed
> >>> > to create / install certificate. And had some failure configuring
> >>> > Exchange. OWA still not working
> >>> >
> >>> > Please Let me know if you have any more suggestions.
> >>> >
> >>> > Here is the report from CEICW:
> >>> >
> >>> > Connection type: Do not change
> >>> >
> >>> > The firewall on your computer running Small Business Server could not
> >>> > be
> >>> > configured. You must configure a firewall to secure your local network
> >>> > from the Internet. For more information about configuring firewall
> >>> > settings for your Small Business Server network, see Help and Support.
> >>> > Web services on your server's default Web site to be available through
> >>> > the
> >>> > firewall to users on the Internet:
> >>> > None of the Web services
> >>> >
> >>> > The Web server certificate required for https:// will be created for
> >>> > the
> >>> > following Web server name: mysbsserver.myaddomain.local
> >>> >
> >>> > Email: Enable Exchange for Internet e-mail with the following
> >>> > settings:
> >>> > E-mail delivery:
> >>> > Route e-mail to the Internet by using DNS.
> >>> > E-mail retrieval:
> >>> > Use Exchange to retrieve SMTP e-mail.
> >>> > Email retrieval method:
> >>> > Route e-mail from the Internet directly to Exchange.
> >>> > Registered Internet e-mail domain name: myemaildomain.com.
> >>> > E-mail attachments: Remove e-mail attachments from Internet e-mail as
> >>> > specified in the wizard.
> >>> >
> >>> > For more detailed information about the configurations performed by
> >>> > this
> >>> > wizard, click the link at the bottom of this page to open
> >>> > Icwdetails.htm
> >>> > in C:\Program Files\Microsoft Windows Small Business
> >>> > Server\Networking\Icw.
> >>> > Note: each time the Configure E-mail and Internet Connection Wizard is
> >>> > run, a new .htm file is automatically generated to preserve the
> >>> > previous
> >>> > settings. For example, Icwdetails1.htm, Icwdetails2.htm, and so on.
> >>> >
> >>> >
> >>>
> >>> Sorry - I should mention that behavior has changed (but still fails).
> >>> Now
> >>> when I try to go to OWA URL, I get a popup asking for credentials (not
> >>> the
> >>> normal OWA login screen). I enter my domain\username (which has admin
> >>> priv
> >>> if that's important) and pwd. Then get this page:
> >>>
> >>> Server Error in '/' Application.
> >>> --------------------------------------------------------------------------------
> >>>
> >>> Configuration Error
> >>> Description: An error occurred during the processing of a configuration
> >>> file
> >>> required to service this request. Please review the specific error
> >>> details
> >>> below and modify your configuration file appropriately.
> >>>
> >>> Parser Error Message: An error occurred loading a configuration file:
> >>> Failed
> >>> to start monitoring changes to
> >>> '\\.\BackOfficeStorage\entrek.com\MBX\myusername' because access is
> >>> denied.
> >>>
> >>> Source Error:
> >>>
> >>>
> >>> [No relevant source lines]
> >>>
> >>>
> >>> Source File: \\.\BackOfficeStorage\entrek.com\MBX\mikesa\web.co nfig
> >>> Line:
> >>> 0
> >>>
> >>>
> >>> --------------------------------------------------------------------------------
> >>> Version Information: Microsoft .NET Framework Version:2.0.50727.3082;
> >>> ASP.NET Version:2.0.50727.3082
> >>>
> >>>
> >>>
> >>

> >

>
>



Advertisement

  Reply With Quote
Old 05-20-2009, 11:30 PM   #12
Duncan McC
Guest
 
Posts: n/a
Default Re: Configuring OWA on SBS 2003

Further to last post, you may need to reset .NET 1.1 ...

http://msdn.microsoft.com/en-us/libr...8h(VS.71).aspx

http://msdn.microsoft.com/en-us/kb/kb00306005.aspx

So, browse to:
"%windir%\Microsoft.NET\Framework

and dig into the 1.1.4322 folder

open a command prompt there.

and type aspnet_regis -i

This will re-reg/install the 1.1.4322 .NET - and perhaps you'll be all
go. Do ensure that the Default Website is using 1.1.4322 - as that's
what it needs, to run.

--
Duncan

In article <#znsuLZ2JHA.3476@TK2MSFTNGP05.phx.gbl>, "Michael Salamone"
<mikesa_at_entrek_dot_com> says...
> FYI I broke my website by setting ASP.NET version to 1.1. So if that's a
> hard requirement for OWA to work, do I need to set up some new virtual
> directory (for either my website or OWA)?
>
> Thanks,
> Mike
>
>
> "Michael Salamone" <mikesa_at_entrek_dot_com> wrote in message
> news:%23nCN9wV2JHA.5772@TK2MSFTNGP02.phx.gbl...
> > Ok - did that. Still showing version 2.something in the new error
> > messages I'm getting from the browser (which I'll post in reply to Robbins
> > reply).
> >
> > I went one level deeper to ExchWeb (and a few others) which have
> > 2.something for ASP.NET and it's grayed out - can't change it.
> >
> > I went as far to reboot the server (sorry to the person who was in the
> > middle of 2GB transfer!) but still the same (1.1 setting for the Default
> > Web Site and 2.something grayed out for ExchWeb and a few others.
> >
> > Mike
> >
> > "Duncan McC" <hard@work.ok> wrote in message
> > news:MPG.247eac12d52602bd989a5f@news.microsoft.com ...
> >> Start the IIS Admin MMC console and drill into the Default Web Site.
> >>
> >> On that, go into it's properties. Click the ASP.NET tab, and change the
> >> .NET version to 1.1*** (not 2) in the drop down list.
> >>
> >> --
> >> Duncan
> >>
> >> In article <#qFozzQ2JHA.4412@TK2MSFTNGP06.phx.gbl>, "Michael Salamone"
> >> <mikesa_at_entrek_dot_com> says...
> >>> "Michael Salamone" <mikesa_at_entrek_dot_com> wrote in message
> >>> news:eQo6GlQ2JHA.1372@TK2MSFTNGP05.phx.gbl...
> >>> > "Lanwench [MVP - Exchange]"
> >>> > <lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in
> >>> > message news:uIeLinO2JHA.1416@TK2MSFTNGP04.phx.gbl...
> >>> >> Michael Salamone <mikesa_at_entrek_dot_com> wrote:
> >>> >>> When I browse to https://mysbsipaddr/exchange, I get "There is a
> >>> >>> problem with this website's security certificate." page.
> >>> >>>
> >>> >>> Then I click "Continue to this website (not recommended)" and get a
> >>> >>> "The page cannot be found" error.
> >>> >>>
> >>> >>> This happens from internal workstation, external (outside the
> >>> >>> firewall), and from the SBS server itself. It's never worked in the
> >>> >>> past from external workstation, but I *think* I've seen it work
> >>> >>> (albeit months and months and months ago) from internal workstation
> >>> >>> and from the server, but not sure what's changed there.
> >>> >>>
> >>> >>> I did follow the steps from this KB article:
> >>> >>> http://support.microsoft.com/default.aspx/kb/259240. For step 8 re:
> >>> >>> ephemeral ports, I followed the instructions here:
> >>> >>> http://support.microsoft.com/kb/812873. There were already a few
> >>> >>> reserved ports in the 1024-65535 range. I left those there, so
> >>> >>> after
> >>> >>> my change, the registry value looks like this:
> >>> >>>
> >>> >>> 1433-1434
> >>> >>> 3343-3343
> >>> >>> 1024-65535
> >>> >>>
> >>> >>> That ok?
> >>> >>>
> >>> >>> I also opened up port 443 for https.
> >>> >>>
> >>> >>> Any help?
> >>> >>>
> >>> >>> Thanks,
> >>> >>> Mike
> >>> >>
> >>> >> You don't need to do any of that other than opening up port 443. Use
> >>> >> the
> >>> >> SBS wizards. Run the CEICW to configure all of this.
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> > Thanks - I saw in some help that I should run the CEICW wizard but I
> >>> > was
> >>> > worried it would muck up something that's already configured and
> >>> > working
> >>> > (like DNS and Exchange notwithstanding the OWA issue I'm having).
> >>> >
> >>> > I ran it anyway. I told it to skip configuring the firewall. It
> >>> > failed
> >>> > to create / install certificate. And had some failure configuring
> >>> > Exchange. OWA still not working
> >>> >
> >>> > Please Let me know if you have any more suggestions.
> >>> >
> >>> > Here is the report from CEICW:
> >>> >
> >>> > Connection type: Do not change
> >>> >
> >>> > The firewall on your computer running Small Business Server could not
> >>> > be
> >>> > configured. You must configure a firewall to secure your local network
> >>> > from the Internet. For more information about configuring firewall
> >>> > settings for your Small Business Server network, see Help and Support.
> >>> > Web services on your server's default Web site to be available through
> >>> > the
> >>> > firewall to users on the Internet:
> >>> > None of the Web services
> >>> >
> >>> > The Web server certificate required for https:// will be created for
> >>> > the
> >>> > following Web server name: mysbsserver.myaddomain.local
> >>> >
> >>> > Email: Enable Exchange for Internet e-mail with the following
> >>> > settings:
> >>> > E-mail delivery:
> >>> > Route e-mail to the Internet by using DNS.
> >>> > E-mail retrieval:
> >>> > Use Exchange to retrieve SMTP e-mail.
> >>> > Email retrieval method:
> >>> > Route e-mail from the Internet directly to Exchange.
> >>> > Registered Internet e-mail domain name: myemaildomain.com.
> >>> > E-mail attachments: Remove e-mail attachments from Internet e-mail as
> >>> > specified in the wizard.
> >>> >
> >>> > For more detailed information about the configurations performed by
> >>> > this
> >>> > wizard, click the link at the bottom of this page to open
> >>> > Icwdetails.htm
> >>> > in C:\Program Files\Microsoft Windows Small Business
> >>> > Server\Networking\Icw.
> >>> > Note: each time the Configure E-mail and Internet Connection Wizard is
> >>> > run, a new .htm file is automatically generated to preserve the
> >>> > previous
> >>> > settings. For example, Icwdetails1.htm, Icwdetails2.htm, and so on.
> >>> >
> >>> >
> >>>
> >>> Sorry - I should mention that behavior has changed (but still fails).
> >>> Now
> >>> when I try to go to OWA URL, I get a popup asking for credentials (not
> >>> the
> >>> normal OWA login screen). I enter my domain\username (which has admin
> >>> priv
> >>> if that's important) and pwd. Then get this page:
> >>>
> >>> Server Error in '/' Application.
> >>> --------------------------------------------------------------------------------
> >>>
> >>> Configuration Error
> >>> Description: An error occurred during the processing of a configuration
> >>> file
> >>> required to service this request. Please review the specific error
> >>> details
> >>> below and modify your configuration file appropriately.
> >>>
> >>> Parser Error Message: An error occurred loading a configuration file:
> >>> Failed
> >>> to start monitoring changes to
> >>> '\\.\BackOfficeStorage\entrek.com\MBX\myusername' because access is
> >>> denied.
> >>>
> >>> Source Error:
> >>>
> >>>
> >>> [No relevant source lines]
> >>>
> >>>
> >>> Source File: \\.\BackOfficeStorage\entrek.com\MBX\mikesa\web.co nfig
> >>> Line:
> >>> 0
> >>>
> >>>
> >>> --------------------------------------------------------------------------------
> >>> Version Information: Microsoft .NET Framework Version:2.0.50727.3082;
> >>> ASP.NET Version:2.0.50727.3082
> >>>
> >>>
> >>>
> >>

> >

>
>


  Reply With Quote
Old 05-21-2009, 12:31 PM   #13
Robbin Meng [MSFT]
Guest
 
Posts: n/a
Default Re: Configuring OWA on SBS 2003


Hi Mike,

Thanks for your response with detailed information.

As I can see from the configuration file you sent to me, yes, although the Default Website has 1.1 version, the others such as ExchWeb virtual directories
still were stuck on 2.0.xx. Based on my test, I changed my Default Website from 1.1v to 2.0v on my SBS server and run a IISreset command, however the
sub virtual directories still has version 1.1v listed and grayed out which mean they will inherit the Default Websit's configurations.

I also checked the Default Website configurations including all virtual directories, all settings are all right except the "Home Directory" tab and the
"ASP.NET" tab.

1. The default "Local path" under "Home Directory" tab should be "C:\inetpub\wwwroot", but yours is "C:\entrek\Entrek".
2. The default "File Location" under "ASP.NET" tab should be "C:\inetpub\wwwroot\web.config", but yours is "C:\entrek\web.config (Entrek)".

According to the error message "The system cannot find the file specified. (C:\entrek\Entrek\web.config line 85)", I suspect if the "Local path" under
"Home Directory" tab should be "C:\entrek" instead of current one "C:\entrek\Entrek"? Please check and adjust it. By the way, I would like to ask why you
changed the default path to "C:\entrek\Entrek"?


If the issue persist however, I agree with Duncan to first try ASP.NET IIS Registration Tool (Aspnet_regiis -I) to register the ASP.NET for 1.1v version and
then perform a IISreset command and see if it helps.

For more information, please refer to the links Duncan provided:

ASP.NET IIS Registration Tool (Aspnet_regiis.exe)
http://msdn.microsoft.com/en-us/libr...8h(VS.71).aspx

How to repair IIS mapping after you remove and reinstall IIS
http://msdn.microsoft.com/en-us/kb/kb00306005.aspx

Please have a try and let us know the results.

Thank you for your time!


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support


  Reply With Quote
Old 05-21-2009, 12:31 PM   #14
SuperGumby [SBS MVP]
Guest
 
Posts: n/a
Default Re: Configuring OWA on SBS 2003

his 'entrek' site should not (IMHO) be operating as a part of SBS' 'Defaut
Web Site'. I'd start with 'FORMAT C:' and set it up properly.

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org
""Robbin Meng [MSFT]"" <v-robmen@online.microsoft.com> wrote in message
news:KMJNr5g2JHA.2060@TK2MSFTNGHUB02.phx.gbl...
>
> Hi Mike,
>
> Thanks for your response with detailed information.
>
> As I can see from the configuration file you sent to me, yes, although the
> Default Website has 1.1 version, the others such as ExchWeb virtual
> directories
> still were stuck on 2.0.xx. Based on my test, I changed my Default Website
> from 1.1v to 2.0v on my SBS server and run a IISreset command, however the
> sub virtual directories still has version 1.1v listed and grayed out which
> mean they will inherit the Default Websit's configurations.
>
> I also checked the Default Website configurations including all virtual
> directories, all settings are all right except the "Home Directory" tab
> and the
> "ASP.NET" tab.
>
> 1. The default "Local path" under "Home Directory" tab should be
> "C:\inetpub\wwwroot", but yours is "C:\entrek\Entrek".
> 2. The default "File Location" under "ASP.NET" tab should be
> "C:\inetpub\wwwroot\web.config", but yours is "C:\entrek\web.config
> (Entrek)".
>
> According to the error message "The system cannot find the file specified.
> (C:\entrek\Entrek\web.config line 85)", I suspect if the "Local path"
> under
> "Home Directory" tab should be "C:\entrek" instead of current one
> "C:\entrek\Entrek"? Please check and adjust it. By the way, I would like
> to ask why you
> changed the default path to "C:\entrek\Entrek"?
>
>
> If the issue persist however, I agree with Duncan to first try ASP.NET IIS
> Registration Tool (Aspnet_regiis -I) to register the ASP.NET for 1.1v
> version and
> then perform a IISreset command and see if it helps.
>
> For more information, please refer to the links Duncan provided:
>
> ASP.NET IIS Registration Tool (Aspnet_regiis.exe)
> http://msdn.microsoft.com/en-us/libr...8h(VS.71).aspx
>
> How to repair IIS mapping after you remove and reinstall IIS
> http://msdn.microsoft.com/en-us/kb/kb00306005.aspx
>
> Please have a try and let us know the results.
>
> Thank you for your time!
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
>


  Reply With Quote
Old 05-22-2009, 07:30 AM   #15
Robbin Meng [MSFT]
Guest
 
Posts: n/a
Default Re: Configuring OWA on SBS 2003

Advertisement

Thank you for your attention Gumby . That's also what I think of to be clarified. :-)


Best regards,
Robbin Meng(MSFT)




Advertisement

  Reply With Quote

vBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright © 2005-2008, TechTalkz.com. All Rights Reserved - Privacy Policy
Valid XHTML 1.0 Transitional