Mike,
Unless you're telling me that this never happens except in a Terminal
Server session I'd very much doubt it has anything to do with Terminal
Server. Even if you did tell me that, I'd still doubt it.
To be of any help we'd need to know something about the c$ language
(just kidding, I'm sure you meant C#), some context about what kind of
app it is (WinForms, console, service, ASP.NET, etc) and what it does,
and the line of code where this error occurs, along with some of the
code in context around it. In truth if you isolate the offending line
of code and use the debugger or trace statements, etc to examine its
runtime condition at the point of error, you will probably solve the
problem yourself.
The error you're getting is a very generic and common error and just
means you're referencing some member of an object that is currently
null. Somewhere you've failed to initialize something or to anticipate
that some object reference could potentially be uninitialized, say, in
some boundary condition.
--Bob
mwolf wrote:
I have an application written in c$ that needs to be run in 3 different
terminal server sessions on a windows 2003 server. Everything will
work fine for about an hour, after this point the applications thread
will no longer be able to create an custom object.
I will continually get the error
"Object reference not set to an instance of an object"
any ideas? It always seems to happen around an hour of run, and if I
have 3 terminal server sessions running the app, they will all fail
about 10 minutes after one another...
mike
