Home All Groups Group Topic Archive Search About

Trace is causing exception

Author
9 Sep 2006 9:38 AM
Aryan
Hi All,
    My application was working fine and giving me proper trace
messages, but now all of sudden it started showing expcetion as

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

"

What could be the cause of this problem,as I didnt change my code any
ways, but when I set trace=false, it does work fine, so what is
actually causing problem???is there anything worng in my application's
trace messages (some trace messages are not getting proper input) or
some configuration issue with DOT NET Framework

Thanks in advance,
Manoj Singh.

Author
9 Sep 2006 2:04 PM
Carl Daniel [VC++ MVP]
Aryan wrote:
> What could be the cause of this problem,as I didnt change my code any
> ways, but when I set trace=false, it does work fine, so what is
> actually causing problem???is there anything worng in my application's
> trace messages (some trace messages are not getting proper input) or
> some configuration issue with DOT NET Framework

Have you tried attaching a debugger to the process and breaking on exception
throw?

I would suspect that there's a problem with some expression that you're
using in the parameter list of a trace call.  When trace is turned off, the
call and the evaluation of it's parameter list is skipped by the compiler,
so errors in the parameter list wouldn't cause exceptions.

-cd
Author
11 Sep 2006 4:45 AM
Aryan
Hi Daniel,
    I comment all the Trace information, but then too I am getting this
wired problem

Regards,
Manoj


Carl Daniel [VC++ MVP] wrote:
Show quote
> Aryan wrote:
> > What could be the cause of this problem,as I didnt change my code any
> > ways, but when I set trace=false, it does work fine, so what is
> > actually causing problem???is there anything worng in my application's
> > trace messages (some trace messages are not getting proper input) or
> > some configuration issue with DOT NET Framework
>
> Have you tried attaching a debugger to the process and breaking on exception
> throw?
>
> I would suspect that there's a problem with some expression that you're
> using in the parameter list of a trace call.  When trace is turned off, the
> call and the evaluation of it's parameter list is skipped by the compiler,
> so errors in the parameter list wouldn't cause exceptions.
>
> -cd

AddThis Social Bookmark Button