ADODB.Recordset error 800a0e78

quinnie · August 21st, 2007, 04:29 PM

I'm having some trouble debugging my code and I keep getting this error: Operation is not allowed when the object is closed.

This references line #58 in my code which is marked by the ** below

Any help debugging would be greatly appreciated.
__________________________________________________ ________________

   Server.ScriptTimeout = 60*5

   SET objConn = Server.CreateObject("ADODB.Connection")

   ' Open Connection...
   objConn.ConnectionTimeout = 240
   objConn.Open sAUDIT_DB_CONNECT

   ' Call Report...
   Set Cmd = Server.CreateObject("ADODB.Command")
   Cmd.ActiveConnection = objConn
   Cmd.CommandTimeout = 0
   Cmd.CommandText = sSQL
   Set objResults = Cmd.Execute

  ** If objResults.EOF Then

      bTrue = 1
   Else
      bTrue = 0
   End If

   If bTrue Then %>

      <html>
     <% Response.Write "Success"%>
      </html>

      <%
         objResults.Close
         SET objResults = NOTHING
         SET objConn = Nothing

   Else %>

      <html>

      <% Response.Write "Sorry, an error has occured."%>

<% End If

Else
%>
   <html>
   SECTION 3
   </html>
<%
End If
%>

Dharam Pal Sikhwal · September 26th, 2007, 02:23 AM

In your code u have no explanation fro objResults variable.

Add this code before using objResults

Dim objResults
Set objResults=Server.CreateObject("ADODB.RecordSet")

woodyz · October 1st, 2007, 11:59 PM

What is contained in sSQL?

Your code assumes that a recordset is being returned. However, your code (as shown) does not set sSQL to anything.

Woody Z
http://www.learntoprogramnow.com
How to use a forum to help solve problems

quinnie · October 2nd, 2007, 09:21 AM

sSQL is passed in when the page is called.
each variable will be defined in the asp call.

woodyz · October 2nd, 2007, 04:27 PM

So is sSQL a valid sql select statement in all cases?

Woody Z
http://www.learntoprogramnow.com
How to use a forum to help solve problems

quinnie · October 2nd, 2007, 04:31 PM

yes. It will always be valid. The problem comes about as this page is called multiple times in quick succession with different data fields each time. Some of these calls fail - while others succeed. I'm trying to troubleshoot the failures but can not pick out any distinct patterns as to what will fail and what will succeed.

woodyz · October 2nd, 2007, 05:13 PM

One thing to do is to make sure you are closing your db connections rather than just setting the connection to nothing.

It is possible that you are getting occasionally mal-formed sql statements, but that probably isn't the first place to look except that it is easy to include the sSQL statement in your display of the error page if you have the freedom to do that.

Is the database only being used for reading data, or are you inserting data as well interspersed with the reading? You might have some locking issues. Unlikely, perhaps, but possible.

What kind of database? Sql Server? Access?

Anyway - start with closing those connections.

Woody Z
http://www.learntoprogramnow.com
How to use a forum to help solve problems