> I'm getting the following message on an ASP page (win2k/iis5 web server) 

> calling a stored procedure on a sql2000 database server.  The sproc runs 

> fine in query analyser and enterprise manager.

> 

> error '8007000e'

> Not enough storage is available to complete this operation.

> 

> 'asp snippet:

> strSQL = "exec my_procedure"

> Set rsSet = dbConn.Execute(strSQL)

> if not (rsSet.bof and rsSet.eof) then

> 	arrResults = rsSet.GetRows() '<-- error refers to this line

> 	rsSet.close

> end if

> set rsSet = nothing

> 

> This error seems to be a memory bug in ADO/MDAC 2,5 or earlier, but I've 

> confirmed we're using MDAC 2.6.  I fixed it in one case by specifying 

the 

> resultant getrows size, i.e. rsSet.getRows(1000), but this didn't work 

> elsewhere.  Smaller amounts of data don't throw up an error.

> 

> Other links for reference:

> http://www.adodb.com/errors_new_result.asp?errors_id=49

> (suggests one other cause is AppendChunk method)

> http://support.microsoft.com/support/kb/articles/Q248/6/68.ASP

> (this last one's for Oracle, but a similar issue)

> 

> Has anyone also experienced this on sql2000?  Any advice?

> The queries only retrieve varchar, int, decimal datatypes - no image/ or 

> text BLOBs.

> 

> 

> Graeme

> 

I have seen this error also.  We are using IIS 4.0 with ADO 2.5 SP2 

though.  We tried making a registry entry for maxblocks at 16K, but we are 

still running out of memory.



If anyone has any information about this, I would really appreciate it.  

The web machine has 4GB of memory on it, memory never really gets 

touched.  Yet after a day or two, we get Providoer error '8007000e' Not 

enough storage is available to complete this operation. And then we must 

reboot the web server.



Thanks,

Scott Emick

semick@p...