Operation is not allowed when the object is closed...

First, let me apologize for not knowing where to post this question...I hope
I've found the proper forum.
Up until three days ago, we've had a native-windows application (dot net)
connecting to a SQL (2000) back-end working with absolutely no problems for
the better part of five years now. Unfortunately, now, upon launching the
client-side applications, we are receiving this error message:
Operation is not allowed when the object is closed.
And, of course, we have no one on staff that knows SQL any more.
Is there any way I can troubleshoot this issue and restore service to my
clients?
Thanx.This looks to me like a .NET error instead of a SQL Server error.
Linchi
"Steven Sinclair" wrote:
> First, let me apologize for not knowing where to post this question...I hope
> I've found the proper forum.
> Up until three days ago, we've had a native-windows application (dot net)
> connecting to a SQL (2000) back-end working with absolutely no problems for
> the better part of five years now. Unfortunately, now, upon launching the
> client-side applications, we are receiving this error message:
> Operation is not allowed when the object is closed.
> And, of course, we have no one on staff that knows SQL any more.
> Is there any way I can troubleshoot this issue and restore service to my
> clients?
> Thanx.|||Okay.
Is there a way I can determine that for sure?
Thanx.
"Linchi Shea" wrote:
> This looks to me like a .NET error instead of a SQL Server error.
> Linchi
> "Steven Sinclair" wrote:
> > First, let me apologize for not knowing where to post this question...I hope
> > I've found the proper forum.
> >
> > Up until three days ago, we've had a native-windows application (dot net)
> > connecting to a SQL (2000) back-end working with absolutely no problems for
> > the better part of five years now. Unfortunately, now, upon launching the
> > client-side applications, we are receiving this error message:
> >
> > Operation is not allowed when the object is closed.
> >
> > And, of course, we have no one on staff that knows SQL any more.
> >
> > Is there any way I can troubleshoot this issue and restore service to my
> > clients?
> >
> > Thanx.|||Is there more to the error message than that?|||Unfortunately, no. Just that message window with an [OK] button.
I'm thinking now, since I can access the DB directly, that it is a .Net
issue, not a DB issue.
Thanx.
"cappjr@.gmail.com" wrote:
> Is there more to the error message than that?
>|||Just Google for this error and you'll see lots of threads about this error
in various forums.
It looks like this is an error that occurs because of wrong coding... It's
not directly about SQL Server, it's about the codes in your app.
--
Ekrem Ã?nsoy
"Steven Sinclair" <StevenSinclair@.discussions.microsoft.com> wrote in
message news:F7E013EA-4A2F-4FB8-A1DF-B1A71A9AEB0A@.microsoft.com...
> First, let me apologize for not knowing where to post this question...I
> hope
> I've found the proper forum.
> Up until three days ago, we've had a native-windows application (dot net)
> connecting to a SQL (2000) back-end working with absolutely no problems
> for
> the better part of five years now. Unfortunately, now, upon launching the
> client-side applications, we are receiving this error message:
> Operation is not allowed when the object is closed.
> And, of course, we have no one on staff that knows SQL any more.
> Is there any way I can troubleshoot this issue and restore service to my
> clients?
> Thanx.|||Yes, I did find a whole lot of information relating to this error through
Google. However, unfortunately, we don't have access to any of the source
code. All we have to deal with is the SQL server and EXE applications that
connect to the SQL server.
Thanx.
"Ekrem Ã?nsoy" wrote:
> Just Google for this error and you'll see lots of threads about this error
> in various forums.
> It looks like this is an error that occurs because of wrong coding... It's
> not directly about SQL Server, it's about the codes in your app.
> --
> Ekrem Ã?nsoy
>
> "Steven Sinclair" <StevenSinclair@.discussions.microsoft.com> wrote in
> message news:F7E013EA-4A2F-4FB8-A1DF-B1A71A9AEB0A@.microsoft.com...
> > First, let me apologize for not knowing where to post this question...I
> > hope
> > I've found the proper forum.
> >
> > Up until three days ago, we've had a native-windows application (dot net)
> > connecting to a SQL (2000) back-end working with absolutely no problems
> > for
> > the better part of five years now. Unfortunately, now, upon launching the
> > client-side applications, we are receiving this error message:
> >
> > Operation is not allowed when the object is closed.
> >
> > And, of course, we have no one on staff that knows SQL any more.
> >
> > Is there any way I can troubleshoot this issue and restore service to my
> > clients?
> >
> > Thanx.
>|||I'd start by adding SET NOCOUNT ON to the relevant procedures.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Steven Sinclair" <StevenSinclair@.discussions.microsoft.com> wrote in message
news:F7E013EA-4A2F-4FB8-A1DF-B1A71A9AEB0A@.microsoft.com...
> First, let me apologize for not knowing where to post this question...I hope
> I've found the proper forum.
> Up until three days ago, we've had a native-windows application (dot net)
> connecting to a SQL (2000) back-end working with absolutely no problems for
> the better part of five years now. Unfortunately, now, upon launching the
> client-side applications, we are receiving this error message:
> Operation is not allowed when the object is closed.
> And, of course, we have no one on staff that knows SQL any more.
> Is there any way I can troubleshoot this issue and restore service to my
> clients?
> Thanx.|||> Operation is not allowed when the object is closed.
As the others have mentioned, this is an application error rather than a SQL
error. This error is often raised when the application tries to use an
object for data retrieval without first checking to ensure it is in a valid
state. My guess is that the application expects at least one row of data
but either no rows were returned or no results were returned at all.
Perhaps a recent data change introduced this error. I suggest you reproduce
the error with a Profiler trace running and examine the last SQL statements
executed on the connection. That might provide a clue in lieu of debugging
the application code.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Steven Sinclair" <StevenSinclair@.discussions.microsoft.com> wrote in
message news:F7E013EA-4A2F-4FB8-A1DF-B1A71A9AEB0A@.microsoft.com...
> First, let me apologize for not knowing where to post this question...I
> hope
> I've found the proper forum.
> Up until three days ago, we've had a native-windows application (dot net)
> connecting to a SQL (2000) back-end working with absolutely no problems
> for
> the better part of five years now. Unfortunately, now, upon launching the
> client-side applications, we are receiving this error message:
> Operation is not allowed when the object is closed.
> And, of course, we have no one on staff that knows SQL any more.
> Is there any way I can troubleshoot this issue and restore service to my
> clients?
> Thanx.