Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

System Message 6900, 6906 or SQL Server messsage 62, 63, 67 or 93 when you save or release a batch in Microsoft Dynamics SL 2011


View products that this article applies to.

Symptoms

When you save or release a batch in various modules in Microsoft Dynamics SL 2011, you may receive one or more of the following error messages:
System Message 6900 - Another process has updated the %s table. The system will automatically cancel your changes.
System Message 6906 - Another process has deleted the %s item. The system will automatically cancel your changes.
SQL Server Message 93 - [Microsoft][SQL Server Native Client 10.0] Connection is busy with results for another command.

SQL Server Message 62 - [Microsoft][SQL Server Native Client 10.0] Invalid Cursor State.

SQL Server Message 63 - [Microsoft][SQL Server Native Client 10.0]Query timeout expired.

SQL Server message 67 - Invalid transaction state.


↑ Back to the top


Cause

This problem occurs if the Microsoft Dynamics SL Application database contains SQL triggers.  

↑ Back to the top


Resolution

To correct this issue, add the following line of code to the beginning of any SQL triggers or of any stored procedures that you apply to the database.

set nocount on

↑ Back to the top


Keywords: kbmbsmigrate, kbmbspartner, kbsurveynew, kbsolomon, kb

↑ Back to the top

Article Info
Article ID : 2551478
Revision : 2
Created on : 2/3/2017
Published on : 2/3/2017
Exists online : False
Views : 591