General ODBC Error when opening record

Kirbie Dockery

We're getting an uptick in ODBC errors when trying to open a record.

General ODBC error [Microsoft][ODBC Driver 11 for SQL Server] Connection is busy with results for another command Native Error:0

KB 53118 solves the problem just fine by creating another record and merging the corrupted one into the new record, but it's happening more and more frequently so I'd love to figure out why it happens so I can address that rather than just fixing it every time it does. I thought when I researched this before someone had attributed it to leaving a record open before RE closes, but now I can't find any documentation about that. Do you have any evidence that it's true or is there another explanation? I'd love to be able to give our users instructions that would help us avoid the error!

Faith Murray

Honestly I'd contact Support with that question. Sometimes the causes for issues are the oddest little quirks. Just last week I learned that the Pledge Reminders excel export won't function if you don't have a default printer set up. Counter-intuitive, as excel exports don't output to printers!

Tom Klimchak

We've had the same experience with ODBC errors in the past few months. Today I had a few while we were adding actions and last week our gift processors had them while trying to post gifts. We've also had a lot of unexplained pauses when working with database view… but all the issues seem to come and go at random so we really haven't had a chance to work with support much.

But, yeah, it's not just you… ?