Re: .net 2.0 set up error
- From: "Brian Williams" <williamsb@xxxxxxxxxxxx>
- Date: Sun, 14 Jan 2007 22:19:32 -0800
Try running
C:\WINDOWS\Microsoft.Net\Framework\v2.0.50727\aspnet_regiis.exe -i
If this doesn't fix it, look at your weblog see if you have any pages being
called with a 500 error.
Also, you should probably change your customErrors to RemoteOnly the add a
defaultRedirect. Then when you wish to see the error just check it on that
local server. You wouldn't want to check in customErrors = Off into
SourceSafe it could make it to a production server.
Regards,
Brian K. Williams
"c676228" <bettys@xxxxxxxxxxxxxxxx> wrote in message
news:93FD2F9C-BC0C-4FFC-BCB0-ECB76CA2076D@xxxxxxxxxxxxxxxx
Hi all,
Our corporate development server hosts many web sites. And I tried to set
up
one .net 2.0 web site on that server and I can run it on my personal
computer. (apsnet tab in virtual directory already set 2.0 since there are
two versions of the framework overthere ).
But it still doesn't work on our corporate server. The page keeps display
the message even I put the "<customErrors mode="Off"/>" in the web.config
file already.
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 remotely (for security reasons). It could,
however,
be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be
viewable
on remote machines, 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 "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</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="RemoteOnly"
defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Is that possible that some default machine config file or parent directory
has web.config file already which will not allow
--
Betty
.
- Prev by Date: persisting login not working when session times out
- Next by Date: Access to the path " is denied
- Previous by thread: persisting login not working when session times out
- Next by thread: RE: .net 2.0 set up error
- Index(es):
Relevant Pages
|