Re: Companyweb unable to access
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Sat, 10 May 2008 11:46:31 +1000
www.sbsbpa.com (has a link to MS)
"gpm25" <gpm25@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3D750FA0-9A50-43AE-98BD-A67AB97C284D@xxxxxxxxxxxxxxxx
Thanks for that tip, where can I find the BPA Utility? TIA
"Geoff Schaller" wrote:
Yes,
Until you do something clever later, your ASP version for your SBS
websites must 1.1.x.x
Run the BPA utility - it is great. It will point out all these
inconsistencies (it did for us) and then re-run the install to pick up
the things you missed.
Good luck
Geoff
"gpm25" <gpm25@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FFB1BE66-7A86-4288-B939-3B0880F6A9E1@xxxxxxxxxxxxx:
In trying to resolve this issue I noticed in some other postings a
reference
to the ASP.Net ver needing to be 1.1.xxxx but not 2.0.xxxx which is
what mine
was set to only now I get the following error;
Server Error in '/' Application.
--------------------------------------------------------------------------------
Runtime Error
Description: An application error occurred on the server. The current
custom
error settings for this application prevent the details of the
application
error from being viewed.
Details: To enable the details of this specific error message to be
viewable
on the local server machine, please create a <customErrors> tag within
a
"web.config" configuration file located in the root directory of the
current
web application. This <customErrors> tag should then have its "mode"
attribute set to "RemoteOnly". To enable the details to be viewable on
remote
machines, please set "mode" to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a
custom
error page by modifying the "defaultRedirect" attribute of the
application's
<customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Are you able to shed some light on this? TIA
"Geoff Schaller" wrote:
Reinstall.
You are definitely missing some components because assuming a clean
install right out of the box on a virgin HDD, it will just work. If
any
installed components fail to install you need to sort out the reason.
There will be a failure somewhere, assuming you actually completed
the
install.
Geoff
"gpm25" <gpm25@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C620BF1-E2A3-4B0F-888E-544D327A5C77@xxxxxxxxxxxxx:
Hi there
I have done some searching on this forum and have found similar
posts but
not exactly the same as my own situation.
I have a SBS2003 R2 server newly installed which displays 'Page
cannot be
displayed' in the
following:
- Companyweb
- Monitoring (Server Management)
- Backup ( Server Management)
Is there a single factor that could cause all of these to fail?
Any help would be very much appreciated.
.
- References:
- Companyweb unable to access
- From: gpm25
- Re: Companyweb unable to access
- From: Geoff Schaller
- Re: Companyweb unable to access
- From: gpm25
- Re: Companyweb unable to access
- From: Geoff Schaller
- Re: Companyweb unable to access
- From: gpm25
- Companyweb unable to access
- Prev by Date: Re: ISA - Security camera - open port
- Next by Date: Re: General Certificate Question
- Previous by thread: Re: Companyweb unable to access
- Next by thread: Re: Companyweb unable to access
- Index(es):
Relevant Pages
|