Re: multiple-step ole db operation generated errors? (Member of pr

Dan Guzman (guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I have found the problem. My user rights within SQLServer were not
granting access to execute stored procs.

The fact that the proper exception didn't get thrown is an issue. You
might try adding SET NOCOUNT ON to your stored procedures to see if the
proper exception bubbles up.

If I understood Hidarisei's post correctly, he had simply failed to
assign permissions to execute the stored procedure. In that case, it
probably does not matter what's in those procedures. :-)

My guess is that he is not checking for errors in the right place,
but jogs alone, and tries to get a result set which is not there,
and that's why he get the multi-step error.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.