Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 sql error?

Author  Topic 

SHARDIK-GUARDIAN
Starting Member

20 Posts

Posted - 2009-05-04 : 05:45:10
Hi all,

I'm new to SQL and need help with an error that keeps coming and going on my site.

Every now and then I get this error on my site. It usually fixes itself within a minute.

My host recently moved my site to VMWare. My site/DB is really not heavy and (as far as I can imagine) should not have any issues with queries etc.

Error message:
Err = The connection cannot be used to perform this operation. It is either closed or invalid in this context.

ADODB.Recordset error '800a0e78' Operation is not allowed when the object is closed. ... line 101


Line 101:
oRecSearch.close


I need to know why this is happening. My site didn;t have any problem like this for 5 years and now it's happening alarmingly frequently.

Please help, I beg you.

Thanks all :-D

------------------------------------------------------------
Was there ever a trap to match the trap of love?

senthil_nagore
Master Smack Fu Yak Hacker

1007 Posts

Posted - 2009-05-04 : 05:59:07
Check your ASP code where the EHC_SQLDBRecordset is referenced and check that it gets "open" before any action is taken on it.


Senthil.C
------------------------------------------------------
[Microsoft][ODBC SQL Server Driver]Operation canceled
Go to Top of Page

ashishashish
Constraint Violating Yak Guru

408 Posts

Posted - 2009-05-04 : 06:02:02
this error is due to your coding problem in ,,,,, VB
i think you working on VB...
so take a look at your coding part in your application there must be you may be use something like that

oRecSearch.open "your_query"




iF theRe iS a wAy iN tHen theRe iS a wAy oUt..
Go to Top of Page

SHARDIK-GUARDIAN
Starting Member

20 Posts

Posted - 2009-05-04 : 06:02:36
quote:
Originally posted by senthil_nagore

Check your ASP code where the EHC_SQLDBRecordset is referenced and check that it gets "open" before any action is taken on it.




I will check now. But I feel I must tell you that this problem appears on every page that uses a query, and they all stop working at the same time. I will look now but could it really be a problem with the code on one page?

Thanks :)

------------------------------------------------------------
Was there ever a trap to match the trap of love?
Go to Top of Page

SHARDIK-GUARDIAN
Starting Member

20 Posts

Posted - 2009-05-04 : 06:10:38
quote:
Originally posted by senthil_nagore

Check your ASP code where the EHC_SQLDBRecordset is referenced and check that it gets "open" before any action is taken on it.




Can't find "EHC_SQLDB" anywhere.

------------------------------------------------------------
Was there ever a trap to match the trap of love?
Go to Top of Page

SHARDIK-GUARDIAN
Starting Member

20 Posts

Posted - 2009-05-04 : 06:13:12
quote:
Originally posted by ashishashish

this error is due to your coding problem in ,,,,, VB
i think you working on VB...
so take a look at your coding part in your application there must be you may be use something like that

oRecSearch.open "your_query"




I have a file that every page looks at to pull DB connection details. The code in the file looks like this:

	Const CONNECTIONSTRING = "Provider=SQLOLEDB.1;Persist Security Info=False;User ID=*****;Password=*****;Initial Catalog=Website;Data Source=10.80.***.***"


Is that any help?

Thanks :)

------------------------------------------------------------
Was there ever a trap to match the trap of love?
Go to Top of Page

senthil_nagore
Master Smack Fu Yak Hacker

1007 Posts

Posted - 2009-05-04 : 06:28:37
I Think you try to execute a query before the connection is established! i.e(Before linking the DB Connection file)

Check weather the file is linked properly..


Senthil.C
------------------------------------------------------
[Microsoft][ODBC SQL Server Driver]Operation canceled
Go to Top of Page

SHARDIK-GUARDIAN
Starting Member

20 Posts

Posted - 2009-05-04 : 06:41:38
quote:
Originally posted by senthil_nagore

I Think you try to execute a query before the connection is established! i.e(Before linking the DB Connection file)

Check weather the file is linked properly..




I think it's linked properly. It works perfectly 99% of the time. But how can I check that it is "properly linked"? If it was not properly linked then it would never work right?

Does anyone think the VMWare could be an issue here?

Thanks.

------------------------------------------------------------
Was there ever a trap to match the trap of love?
Go to Top of Page

senthil_nagore
Master Smack Fu Yak Hacker

1007 Posts

Posted - 2009-05-04 : 06:44:29
Sorry i did't have much front end exposure to solve your problem


Senthil.C
------------------------------------------------------
[Microsoft][ODBC SQL Server Driver]Operation canceled
Go to Top of Page

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2009-05-04 : 09:19:32
Check the version of VMWare. We had an issue when running the "free" version (sorry, I don't know the version #) where a SQL process would stop running for a moment and then pickup again without issue. Once we upgraded, our issue went away.

Terry

-- Procrastinate now!
Go to Top of Page

SHARDIK-GUARDIAN
Starting Member

20 Posts

Posted - 2009-05-05 : 03:36:00
quote:
Originally posted by senthil_nagore

Sorry i did't have much front end exposure to solve your problem




No need to say sorry :) I appreciate every letter you have taken the time to type to help me!

Have a great day. Sat cool

------------------------------------------------------------
Was there ever a trap to match the trap of love?
Go to Top of Page

SHARDIK-GUARDIAN
Starting Member

20 Posts

Posted - 2009-05-05 : 09:56:04
quote:
Originally posted by tosscrosby

Check the version of VMWare. We had an issue when running the "free" version (sorry, I don't know the version #) where a SQL process would stop running for a moment and then pickup again without issue. Once we upgraded, our issue went away.



I am told that it's running on VMWARE esx 3.5.2 update 4.

Is that any help?

------------------------------------------------------------
Was there ever a trap to match the trap of love?
Go to Top of Page
   

- Advertisement -