Monday, March 26, 2012

this is the asp.net code

Sub BindDropBox()
conPos.Open()
oSevenIssuesCMD = New SqlCommand("SevenIssues", conPos)
oSevenIssuesCMD.CommandType = CommandType.StoredProcedure
oSevenIssuesCMD.Parameters.Add(New SqlParameter("@dotnet.itags.org.productName", SqlDbType.Va
rChar, 50))
oSevenIssuesCMD.Parameters("@dotnet.itags.org.productName").Value = "TESTPRODUCT"
oSevenIssuesReader = oSevenIssuesCMD.ExecuteReader
DropDownList1().DataSource = oSevenIssuesReader
DropDownList1.DataTextField = "Cover_Date"
DropDownList1.DataValueField = "Cover_Date"
DropDownList1.DataBind()
conPos.Close()
End Sub
This is the error
Server Error in '/TEST_application' 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 runni
ng 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 applic
ation. This <customErrors>
tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File --><configuration><system.web><customErro
rs mode="Off"/></system.web></configuration>
Notes: The current error page you are seeing can be replaced by a custom err
or page by modifying the "defaultRedirect" attribute of the application's <c
ustomErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File --><configuration><system.web><customErro
rs mode="RemoteOnly" defaultRedirect="mycustompage.htm"/></system.web></conf
iguration>All that error message says, is that you are not allowed to see the actual
error due to your Web.config settings. Change your settings to see the
actual error, as it could be happening anywhere, not necessarily in the
snippet you provided.
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:0715C212-605A-4162-904F-CBBD5021B896@.microsoft.com...
> Sub BindDropBox()
> conPos.Open()
>
> oSevenIssuesCMD = New SqlCommand("SevenIssues", conPos)
>
> oSevenIssuesCMD.CommandType = CommandType.StoredProcedure
>
> oSevenIssuesCMD.Parameters.Add(New SqlParameter("@.productName",
SqlDbType.VarChar, 50))
> oSevenIssuesCMD.Parameters("@.productName").Value = "TESTPRODUCT"
>
> oSevenIssuesReader = oSevenIssuesCMD.ExecuteReader
>
> DropDownList1().DataSource = oSevenIssuesReader
> DropDownList1.DataTextField = "Cover_Date"
> DropDownList1.DataValueField = "Cover_Date"
>
> DropDownList1.DataBind()
>
> conPos.Close()
>
> End Sub
>
> This is the error
>
> Server Error in '/TEST_application' 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>
change it to what?
Did you read the error message? It said to change the mode attribute to
'Off'.
Alternatively, it said you could view the real error by running the page
from the server itself.
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C9D4F429-9192-4F60-8812-8FFEDA62FBD1@.microsoft.com...
> change it to what?

0 comments:

Post a Comment