Hi,
I signed up with webhost4life.com to host my Personal Web Starter Kit and I have a few issues to resolve. I hope this article is appropriate here. If not, please let me know which forum is good. My questions are:
1. My website uses ASPNET membership, roles and etc.... I know the asp.net runtime uses the ASPNET account to gain access to Sqlserver for the Sqlserver membership stuff. I use sql2000 at webhost4life. Do they need to add the ASPNET account to the Sqlserver which houses my db? When I posted this question to their helpdesk, they asked I setup this up in my local db; then upload the db; then it will have it everything I need. I can't do this because the ASPNET account is under my domain. Can someone let me know how this account works when the site is hosted by an outside company?
2. I have this line in my root web.config <customErrors mode="Off"/> as a child element under <system.web>. When my page encounters an error, I don't get the actual error. Why? My default homepage produces the error below.
If you are a member with webhost4life.com and had some issues setting up the site or encounter similar issues like I have, I'd greatly appreciate any help you can provide. Again, I already have tickets opened with them but they seem to be slow on weekends.
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>
|