Newbie needs help with 2 simple questions
-
Here's what happened: I created an ASP.NET eCommerce site half year ago for a school assignment, it was deployed locally on my hard drive, and everything worked. However, I am planning to create a real eCommerce site now, so I had applied for a webhosting server that supports ASP.NET, and uploaded the assignment I did earlier and see how it would go. To my surprise :^), all I get is the message:
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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off". 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 configuration tag to point to a custom error page URL. configuration system.web customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/ /system.web /configurationIs there anything else I need to do when deploying an ASP.NET site to a real webhosting server? And another question, I was planning to store database information in an access database. Here's the question I'm wondering: I suppose I should password protect the directory where the access databases (*.mdb) are placed. I assume I have to insert the login id/password when retreiving/writing the information in the database. But where do I insert them? And if I insert them in the codes won't others will be able to see the login id/password by viewing the source codes? Or am I completely mistaken? :confused::confused::confused: Any advice would be greatly appreciated!!! :-D:-D:-D -
Here's what happened: I created an ASP.NET eCommerce site half year ago for a school assignment, it was deployed locally on my hard drive, and everything worked. However, I am planning to create a real eCommerce site now, so I had applied for a webhosting server that supports ASP.NET, and uploaded the assignment I did earlier and see how it would go. To my surprise :^), all I get is the message:
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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off". 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 configuration tag to point to a custom error page URL. configuration system.web customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/ /system.web /configurationIs there anything else I need to do when deploying an ASP.NET site to a real webhosting server? And another question, I was planning to store database information in an access database. Here's the question I'm wondering: I suppose I should password protect the directory where the access databases (*.mdb) are placed. I assume I have to insert the login id/password when retreiving/writing the information in the database. But where do I insert them? And if I insert them in the codes won't others will be able to see the login id/password by viewing the source codes? Or am I completely mistaken? :confused::confused::confused: Any advice would be greatly appreciated!!! :-D:-D:-DBrotha, you're first step ought to be following the instructions on that error message up there to find out what is causing this bug. If you follow the instructions in this error message, it will display a much more specific error message indicating exactly what caused this failure. There should be very little different about a hosting provider vs. your local machine, but you'll never know until you see the real error message. And as far as your MSAccess question, you set the connection properties in the web.config file. No one can download the web.config file, ASP.NET/IIS knows automatically to never serve up that file. If you need to find out how to setup the DNS within your web.config, you might wanna check out the this faq.