Sql stored procedure not releasing from .NET

Question

1.00/5 (1 vote)

See more:

I have a stored procedure that runs correctly from SQL. However, when I call the procedure from VB.Net it completes all the process but doesn't release and move on the the next line of code.

I am calling the procedure like I all the others I am using. Could this be a deadlock problem. There is nothing else accessing the database. I do have two cursors inside my procedure.

Thanks in advance for the help.

What I have tried:

calling the procedure differently and modifying the procedure

Posted 7-Feb-24 5:54am

whistle1973

Add a Solution

Comments

Richard MacCutchan 7-Feb-24 12:13pm

Since we cannot see either your VB or SQL code, it is anyone's guess what is the problem. Please use the Improve question link above, and add complete details of what is not working.

Dave Kreskowiak 7-Feb-24 12:37pm

That would tell me the stored procedure is still running, but, like Richard said, since you haven't posted the procedure and the VB.NET code setting up the call and calling it, there's very little anyone can tell you.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Answer 1 · 2024-02-07T20:32:00

If the code doesn't appear to be following the correct code flow after calling the stored procedure, it could well be that you have encountered an exception that is interrupting the flow. To test this, wrap the call to the stored procedure in a Try/Catch block and put a breakpoint inside the exception handler to see if this is the case. Beyond that, as Richard and Dave said in response to your question, you have given us nothing to go on as we can't see your code.

Sidenote: Adding that extra bit of exception handling is only there for your quick diagnosis of the problem. You should only add exception handling to the flows of your code that actually need it, e.g. top level exception handling or to aid retry failed operations if appropriate.