Asp.net server error?

Hey all,
I'm trying to get an asp.net web site going (using godaddy.com as host), and when i use a template, it keeps giving me the following error:

Server Error in '/' Application.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

The guys at godaddy told me to change the code above (which has errors in it or something? to this:

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

But then it says that has errors as well. They also told me to put a medium trust tag ( <trust level="Medium" originUrl="" />) in the web.config but all of this gets me back to where i started. Any help? Has anyone had this same problem with the business/club/personal asp.net samples when uploading to a server? It works fine when I run it from my pc via virtual server though.

The server still says the same thing after adding that code. the web site is tysonfire.com . someone please help.

As I have understood, all the advice you got so far is some way to debug your code, and find the source of error not to fix the error. The changes in your web.config would not fix the error by itself.

There are times when the code works fine in a local web server, but not when it is published. As a simple example, when your local SQL engine has the right table (locally), but there is not an equivalent table in the remote SQL server database. Unfortunately the problem is too broad, and it is not possible to tell beforehand what would be the problem unless you allow debugging your code and quote the main error message. With your current web.config settings, the main error is not displayed for the security reasons.

Try this line
<compilation debug="true"/>

inside system.web in your web.config as:

<system.web>
...
<compilation debug="true"/>
...
</system.web>

run your application again, and make a new question quoting the ASP.NET error you get. For sure, it is safe for now. but you would eventually have to remove this line before you expose your web to public.

Good luck.

Have you tested it on your local machine? Is your default page named 'default.aspx'? I ask that because I'm sure that's what GoDaddy has IIS set up for. Is your default page trying to run code? I would switch it with a blank default page to see if you still get the same error. Btw, what error were you getting exactly before you threw the trust level tag in your web.config?

Btw, get rid of that trust level tag....

edit - feel free to email me