Jump to content
Sign in to follow this  
bazzer747

MSSQL Busy

Recommended Posts

A client has several of the applications I've written over the past several years and all work OK, They all connect (with FireDac) to a Microsoft SQL Server.

 

However, I've just loaded a newer application (compiled in Delphi 10.3.3) and when I run it on this PC I get the following FireDac error message immediately (see attached):

 

Exception EMSSQLNativeException in module ... at .....

[FireDAC][Phys][ODBC][Microsoft][ODBC SQL Server Driver]Connection

is busy with results for another hstmt

 

The PC is not running any other application that could be accessing the MS SQL Server, so I'm at a loss as to why it is busy at all. This application works fine on my development machine. 

 

Would this be a driver issue, maybe a newer driver is needed (is there one)? Or does Delphi 10.3.3/FireDAC do something differently to what it did in earlier versions?

 

Any thoughts would be much appreciated.

FiredacError.jpg

Share this post


Link to post

Could this be due to a setting of isolation level on this client? I remember when you had to switch between named pipes and TCP to get the connection working, there's a lot of other settings you can tweak and change. Perhaps there's one that is causing this.

Share this post


Link to post

it's a recurring problem

 

 

most likely no ODBC driver installed

Edited by Attila Kovacs

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×