Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

SQL Sever Message 93 and 67.

(0) ShareShare
ReportReport
Posted on by

SL 2011

SQL 2008

Not running FRx and never have

Running MR2012

 

We have recently run into an Issue where we receive SQL Server Message 93 when trying to release an AP batch. Now all the AP batches are suspended and we cannot release them.

 

Microsoft Sql Sever Native client 10.0] Connection busy with results for another command.

Debugging info:Batch_mod_rlsed '030224', 'AP'

Cursor(c_batch) Batch_Mod_Rlsed'030224', 'AP'

optional info: SqlState = HY000 Native Error = 0 ErrorMsg = Microsoft Sql Sever Native client 10.0] Connection busy with results for another command.  pcbErrorMsg = 93

ODBCRowNumber =-1 Column =-1 SSrvrLine = 0 SSrvrMsgState=0 SsrvrSeverity  = 0 SsrverProcname = SsrvrSrvname =

===========================================================

SQL Server Message 67: [Microsoft][SQL Server Native Client 10.0]Invalid transaction state

 Debugging info: DeleteDbConnections - SQLFreeHandle Failed   Optional info: SqlState = 25000 NativeError = 0 ErrorMsg = [Microsoft][SQL Server Native Client 10.0]Invalid transaction state pcbErrorMsg = 67

=============================================================

 

Running the script from B2551470_FRx_SL2011 will not help as we are not running FRx nor did the Below scrip help and I have checked that all custom triggers are "SET NO COUNT ON" and they are.

 

alter Proc Batch_Mod_Rlsed @parm1 varchar ( 10), @parm2 varchar ( 2) as

Select * from Batch with (nolock)

where BatNbr = @parm1

and Module = @parm2

and Rlsed = 1

*This post is locked for comments

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: SQL Sever Message 93 and 67.

    Hi Warendbzgt,

    For the issue that you are seeing it will not be the Set nocount on that will cause the issue, it will be the Set nocount off that causes the issue.

    What you will need to do:

    1) get a SQL profiler trace of the error

    2) Save the trace

    3) Close the trace

    4) open the trace back up

    5) search the trace for Set nocount off

    6) Within the trigger you will need to comment out that line

    Template that you will need to use for the SQL Profiler trace:

    967955 How to use SQL Profiler in SQL Server 2008, 2008 R2 or 2012 to trace database events in Microsoft Dynamics SL

    https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;967955

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >

Featured topics

Product updates

Dynamics 365 release plans