MSSQL: Connection is busy with results for another hstmt

I have run MSSQL server  on different 3 computer.
(just same data and log files)
client code is same too,
but one of the server return me error:
---Connection is busy with results for another hstmt ---

obviously problem is with database setting but I cant locate which one is guilty
please help
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


Most likely you are using a still open recordet. You expected only ONE row but the querry actually returned 2 rows and this causes your program to fail. Make sure you really only get one record here.

Another option can be that you return a rowcount for an operation where you dont return a record. Thiscan mess up your recordsets also. turn rowcount off in your stored procedure.

Hope this helps

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.