Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2006-09-07 : 16:22:40
|
Hello All -I created a simple data entry form on VS 2005 and it works fine on my machine, I deployed to the server, the form loads ok when I hit the url, but I get "Server Error in '/' Application." error message when I click the submit records button, any ideas ?---"There's no sexy way to carry a lunch bag." My boss |
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2006-09-07 : 19:00:01
|
Is the directory you deployed to setup as a virtual directory? Usually that's what most people forget to do when deploying an ASP.net app for the first time.Michael<Yoda>Use the Search page you must. Find the answer you will. Cursors, path to the Dark Side they are. Avoid them, you must. Use Order By NewID() to get a random record you will.</Yoda>Opinions expressed in this post are not necessarily those of TeleVox Software, inc. All information is provided "AS IS" with no warranties and confers no rights. |
 |
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2006-09-07 : 19:35:49
|
Hey Michael -Thanks for your reply, actualy not, I just used the "Publish to Server" option by right clicking on the solution. I'm home now but I'll try that tomorrow. And yes, that's actualy my first asp.net application.---"There's no sexy way to carry a lunch bag." My boss |
 |
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2006-09-07 : 21:13:48
|
Hmmm.... Well I'm thinking that should create the directory as a Virtual Directory.Now that I re-read your post, it looks like ASP.net is able to run since you are able to get your form to load. It just fails upon postback eh? Tracking down what the error is can be a bit tricky, esp. since I can't see the code.You've got a few ways of handling this:1. Add some error handling in the Page_load and button_click events.In the "catch" statement, log the error to a trace.warn, a text file, and e-mail, etc. 2. Impliment global error handling (a catch all)I've done something very similar in my applications and it's very handy.http://www.developer.com/net/asp/article.php/961301Once you know what the error is, we can go from there. The first step of problem solving is figuring out what the problem is.Michael<Yoda>Use the Search page you must. Find the answer you will. Cursors, path to the Dark Side they are. Avoid them, you must. Use Order By NewID() to get a random record you will.</Yoda>Opinions expressed in this post are not necessarily those of TeleVox Software, inc. All information is provided "AS IS" with no warranties and confers no rights. |
 |
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2006-09-08 : 07:19:42
|
How about reading and/or posting here the rest of the error information that is returned ? Sometimes reading the *entire* error message carefully is helpful when troubleshooting. - Jeff |
 |
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2006-09-08 : 12:06:28
|
Sure, 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> ---"There's no sexy way to carry a lunch bag." My boss |
 |
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2006-09-08 : 13:18:08
|
OK, what is all that jibber jabber telling us? It says that for security, the specific error details are not being displayed. To see the actual error, you need to alter your web.config file to allow error reporting. Why don't you do that so you can see the actual error message. The actual error message will probably help you troubleshoot the problem.Makes sense, right? All of the instructions and information you need is right there.- Jeff |
 |
|
|
|
|
|
|