Error when some stored procedures are called in a classic ASP Page

[Racer-D]

When some of the SQL Server stored procedures I have written are called via
my Classic ASP page I have written I get the following error in the cell that
is supposed to be retrieving a single result:

"ADODB.Recordse t error '800a0cc1'

Item cannot be found in the collection corresponding to the requested name
or ordinal.

/Default.asp, line 130"

I have no idea why this could be occuring. Some of the other stored
procedures work just fine. Any one have any ideas?

Thanks!!

dp

[Bob Barrows [MVP]]

Racer-D wrote:

When some of the SQL Server stored procedures I have written are
called via my Classic ASP page I have written I get the following
error in the cell that is supposed to be retrieving a single result:

"ADODB.Recordse t error '800a0cc1'

Item cannot be found in the collection corresponding to the requested
name or ordinal.

/Default.asp, line 130"

I have no idea why this could be occuring. Some of the other stored
procedures work just fine. Any one have any ideas?

Thanks!!

dp

You probably are getting spurious resultsets containing "x records affected"
messages. You can suppress these messages by adding
SET NOCOUNT ON
to the beginning of your stored procedures.

If that does not solve it, you should show us some code.

Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Racer-D]

I changed the proc to return named columns in brackets to see if that would
help. Still nothing.

On a separate effort, I changed the SELECTS to PRINT statements.. Still no
change. I still get the following error:
ADODB.Recordset error '800a0cc1'

Item cannot be found in the collection corresponding to the requested name
or ordinal.

/Default.asp, line 130


"Racer-D" wrote:

SET NOCOUNT ON didn't change anything. Here is the ASP calling the procedure:
<td> <%strSQL1 = "exec proc_dba_jobhis tory"
Set rs = aursql01.execut e(strSQL1)
Response.Write rs(0)%>

Thanks,

dp
"Bob Barrows [MVP]" wrote:

Racer-D wrote:

When some of the SQL Server stored procedures I have written are
called via my Classic ASP page I have written I get the following
error in the cell that is supposed to be retrieving a single result:

"ADODB.Recordse t error '800a0cc1'

Item cannot be found in the collection corresponding to the requested
name or ordinal.

/Default.asp, line 130"

I have no idea why this could be occuring. Some of the other stored
procedures work just fine. Any one have any ideas?

Thanks!!

dp

You probably are getting spurious resultsets containing "x records affected"
messages. You can suppress these messages by adding
SET NOCOUNT ON
to the beginning of your stored procedures.

If that does not solve it, you should show us some code.

Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Bob Barrows [MVP]]

There is nothing there that should cause that error, so it stands to reason
that the error is occurring elsewhere.

Why aren't you checking for an empty recordset?

<td> <%strSQL1 = "exec proc_dba_jobhis tory"
Set rs = aursql01.execut e(strSQL1)
if not rs.EOF the
Response.Write rs(0)
else
Response.Write "nothing returned"
end if
%>

Racer-D wrote:

I changed the proc to return named columns in brackets to see if that
would help. Still nothing.

On a separate effort, I changed the SELECTS to PRINT statements..
Still no change. I still get the following error:
ADODB.Recordset error '800a0cc1'

Item cannot be found in the collection corresponding to the requested
name
or ordinal.

/Default.asp, line 130


"Racer-D" wrote:

SET NOCOUNT ON didn't change anything. Here is the ASP calling the
procedure:
<td> <%strSQL1 = "exec proc_dba_jobhis tory"
Set rs = aursql01.execut e(strSQL1)
Response.Write rs(0)%>

Thanks,

dp
"Bob Barrows [MVP]" wrote:

Racer-D wrote:
When some of the SQL Server stored procedures I have written are
called via my Classic ASP page I have written I get the following
error in the cell that is supposed to be retrieving a single
result:

"ADODB.Recordse t error '800a0cc1'

Item cannot be found in the collection corresponding to the
requested name or ordinal.

/Default.asp, line 130"

I have no idea why this could be occuring. Some of the other
stored procedures work just fine. Any one have any ideas?

Thanks!!

dp

You probably are getting spurious resultsets containing "x records
affected" messages. You can suppress these messages by adding
SET NOCOUNT ON
to the beginning of your stored procedures.

If that does not solve it, you should show us some code.

Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap
so I don't check it very often. If you must reply off-line, then
remove the "NO SPAM"

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Bob Barrows [MVP]]

So try my suggestion and report back if it helps.

Racer-D wrote:

Because I am new to this and I am learning. I don't know what else
to show you.

"Bob Barrows [MVP]" wrote:

There is nothing there that should cause that error, so it stands to
reason that the error is occurring elsewhere.

Why aren't you checking for an empty recordset?

<td> <%strSQL1 = "exec proc_dba_jobhis tory"
Set rs = aursql01.execut e(strSQL1)
if not rs.EOF the
Response.Write rs(0)
else
Response.Write "nothing returned"
end if
%>

Racer-D wrote:

I changed the proc to return named columns in brackets to see if
that would help. Still nothing.

On a separate effort, I changed the SELECTS to PRINT statements..
Still no change. I still get the following error:
ADODB.Recordset error '800a0cc1'

Item cannot be found in the collection corresponding to the
requested name
or ordinal.

/Default.asp, line 130


"Racer-D" wrote:

SET NOCOUNT ON didn't change anything. Here is the ASP calling the
procedure:
<td> <%strSQL1 = "exec proc_dba_jobhis tory"
Set rs = aursql01.execut e(strSQL1)
Response.Write rs(0)%>

Thanks,

dp
"Bob Barrows [MVP]" wrote:

> Racer-D wrote:
>> When some of the SQL Server stored procedures I have written are
>> called via my Classic ASP page I have written I get the following
>> error in the cell that is supposed to be retrieving a single
>> result:
>>
>> "ADODB.Recordse t error '800a0cc1'
>>
>> Item cannot be found in the collection corresponding to the
>> requested name or ordinal.
>>
>> /Default.asp, line 130"
>>
>> I have no idea why this could be occuring. Some of the other
>> stored procedures work just fine. Any one have any ideas?
>>
>> Thanks!!
>>
>> dp
>
> You probably are getting spurious resultsets containing "x records
> affected" messages. You can suppress these messages by adding
> SET NOCOUNT ON
> to the beginning of your stored procedures.
>
> If that does not solve it, you should show us some code.
>
> Bob Barrows
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap
> so I don't check it very often. If you must reply off-line, then
> remove the "NO SPAM"

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get
a quicker response by posting to the newsgroup.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"