Article ID: 953374 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you use Microsoft Dynamics AX 2009, Microsoft Dynamics AX 4.0, or Microsoft Dynamics AX 3.0, you receive a warning message that resembles the following in the Application log on the AOS server:
This problem may occur if an SQL SPID is still active in the database but no active client session is associated with the SQL SPID. This situation is usually caused by an abnormal client disconnection or by a task on a process that is ended by an end-user. The SPID number in the warning message is an orphaned SPID in Microsoft SQL Server.
If you experience this situation, the AOS server is waiting for SQL to return, and the AOS cannot kill the SPID because of security restrictions. In this case, when a user starts a second client that touches the same table that you use in the Microsoft Dynamics AX database, a block occurs.
To resolve this problem, end the client session that is still in the online user's form. Or, kill the orphaned SPIDs in SQL Server. To do this, follow these steps to monitor and to clean up orphaned SQL SPIDs:
In the "Resolution" section, you can verify the actual client computer, and you can verify the end-user account name that is associated with the orphaned SPID. Make sure that you try to understand the business process and the sequence of events that caused the SPID to be orphaned in the Microsoft Dynamics AX database. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/953375/ )How to find a user ID that is associated with a session ID of an "RPC error: RPC exception 1726 occurred in session [SessionID]" error message in the Application log on the AOS server in Microsoft Dynamics AX
Article ID: 953374 - Last Review: January 16, 2015 - Revision: 6.0