Object reference not set to an instance of an object.

H

Hennie

I Get the following error all of a sudden:
I do not know what is wrong or where to start looking.
I added the Debug="true" directive at the top of the page, but it does not
help at all.

What can the problem be?
This is the complet error message:

Server Error in '/MailListManager' 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:

The source code that generated this unhandled exception can only be
shown when compiled in debug mode. To enable this, please follow one of the
below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated
the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your
application:

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

Note that this second technique will cause all files within a given
application to be compiled in debug mode. The first technique will cause
only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a
memory/performance overhead. You should make sure that an application has
debugging disabled before deploying into production scenario.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an
object.]
System.Web.UI.Control.AddedControl(Control control, Int32 index) +2
ASP.Login_aspx.FrameworkInitialize()
System.Web.UI.Page.ProcessRequest() +85
System.Web.UI.Page.ProcessRequest(HttpContext context) +18

System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionSte
p.Execute() +179
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +87
 
J

Joseph MCAD

April 6, 2005

Could you post the source code that you think might have caused the
exception? You will get more exception details if you are running the
application in debug mode, than if you ran it in release mode. I'll be happy
to help if you can post some more details! :)

Joseph MCAD
 
H

Hennie

Hi

Thanks for your post.
I created a new project, and copy all my files to it and now it is working
fine. I did not make any changes to any code, but now it is resolved. What
could have caused this, as it can't be the code of any page.

Hennie

Joseph MCAD said:
April 6, 2005

Could you post the source code that you think might have caused the
exception? You will get more exception details if you are running the
application in debug mode, than if you ran it in release mode. I'll be
happy to help if you can post some more details! :)

Joseph MCAD


Hennie said:
I Get the following error all of a sudden:
I do not know what is wrong or where to start looking.
I added the Debug="true" directive at the top of the page, but it does
not
help at all.

What can the problem be?
This is the complet error message:

Server Error in '/MailListManager' 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:

The source code that generated this unhandled exception can only be
shown when compiled in debug mode. To enable this, please follow one of
the
below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that
generated
the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your
application:

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

Note that this second technique will cause all files within a given
application to be compiled in debug mode. The first technique will cause
only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a
memory/performance overhead. You should make sure that an application has
debugging disabled before deploying into production scenario.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an
object.]
System.Web.UI.Control.AddedControl(Control control, Int32 index) +2
ASP.Login_aspx.FrameworkInitialize()
System.Web.UI.Page.ProcessRequest() +85
System.Web.UI.Page.ProcessRequest(HttpContext context) +18

System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionSte
p.Execute() +179
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +87



----------------------------------------------------------------------------
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top