ASP.net and MSSQL

Hi All,

I am working with a windows server and trying to set up something with asp.net
using the asp.net VB in Applications Window. I can get dreamweaver mx version
6.1 (not 2004) to access the MSSQL server and I can test the connection and it
works great. I can even do a query using the bindings (dataset).

My problem is that when I create the page and put data on it and upload it I
get this:

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>


__________________________________________________ ______________________________
________

My hosting provider says that Dreamweaver is coding wrong.. Any help?

Thanks

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".

As the above message tells you, you want to turn on detailed error messages
first. To do that, modify your web.config file. Then, run it again, and read
the more detailed error message.

-Darrel

Don't forget to switch custom errors back on when you've debugged though -
asp.net error messages are very detailed and could thus give out too much
information to your users if it' left in place.

Normally in production you'd want
<customErrors mode="RemoteOnly" defaultRedirect="ErrorPage.aspx"/>
to debug
<customErrors mode="Off" />

Jon

"darrel" <notreal (AT) hotmail (DOT) com> wrote

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".

As the above message tells you, you want to turn on detailed error
messages
first. To do that, modify your web.config file. Then, run it again, and
read
the more detailed error message.

-Darrel