tecavüze uğramış kızla çıkılır mı nick6

server error in '/' application.

object reference not set to an instance of an object.

description: an unhandled exception occurred during the execution of the current web request. please review the stack trace for more information about the error and where it originated in the code.

exception details: system. nullreferenceexception: object reference not set to an instance of an object.

source error:

an unhandled exception was generated during the execution of the current web request. information regarding the origin and location of the exception can be identified using the exception stack trace below.

stack trace:

[nullreferenceexception: object reference not set to an instance of an object.]
kelebekgaleri2007.userspage. detay. page_load(object sender, eventargs e)
system.web.ui.control. onload(eventargs e) +67
system.web.ui.control. loadrecursive() +35
system.web.ui.control. loadrecursive() +98
system.web.ui.control. loadrecursive() +98
system.web.ui.control. loadrecursive() +98
system.web.ui.page. processrequestmain() +750

version information: microsoft .net framework version:1.1.4322.2407; asp.net version:1.1.4322.2407
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). ıt 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>server error in '/' application.

object reference not set to an instance of an object.

description: an unhandled exception occurred during the execution of the current web request. please review the stack trace for more information about the error and where it originated in the code.

exception details: system. nullreferenceexception: object reference not set to an instance of an object.

source error:

an unhandled exception was generated during the execution of the current web request. information regarding the origin and location of the exception can be identified using the exception stack trace below.

stack trace:

[nullreferenceexception: object reference not set to an instance of an object.]
kelebekgaleri2007.userspage. detay. page_load(object sender, eventargs e)
system.web.ui.control. onload(eventargs e) +67
system.web.ui.control. loadrecursive() +35
system.web.ui.control. loadrecursive() +98
system.web.ui.control. loadrecursive() +98
system.web.ui.control. loadrecursive() +98
system.web.ui.page. processrequestmain() +750

version information: microsoft .net framework version:1.1.4322.2407; asp.net version:1.1.4322.2407
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). ıt 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>server error in '/' application.

object reference not set to an instance of an object.

description: an unhandled exception occurred during the execution of the current web request. please review the stack trace for more information about the error and where it originated in the code.

exception details: system. nullreferenceexception: object reference not set to an instance of an object.

source error:

an unhandled exception was generated during the execution of the current web request. information regarding the origin and location of the exception can be identified using the exception stack trace below.

stack trace:

[nullreferenceexception: object reference not set to an instance of an object.]
kelebekgaleri2007.userspage. detay. page_load(object sender, eventargs e)
system.web.ui.control. onload(eventargs e) +67
system.web.ui.control. loadrecursive() +35
system.web.ui.control. loadrecursive() +98
system.web.ui.control. loadrecursive() +98
system.web.ui.control. loadrecursive() +98
system.web.ui.page. processrequestmain() +750

version information: microsoft .net framework version:1.1.4322.2407; asp.net version:1.1.4322.2407
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). ıt 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>