Error message when you review the Application log on the computer that is running Microsoft Dynamics AX 4.0 AOS services: "RPC exception 1726 occurred in session 10"

Applies to: Microsoft Dynamics AX 4.0Axapta Object Server

Symptoms


When you review the Application log on a computer that is running Microsoft Dynamics AX 4.0 Application Object Server (AOS) services, you may see error messages that resemble the following:
Error message 1
Event Type:Information
Event Source:Dynamics Server 17
Date:7/4/2007
Time:12:30:14 PM
Event Category:None
Description:
Object Server 01: RPC error: RPC exception 1726 occurred in session 10
Error message 2
Event Type:Information
Event Source:Dynamics Server 01
Event Category:None
Event ID:110
Date:7/4/2007
Time:12:30:33 AM
User:N/A
Computer:ComputerName
Description:
Object Server 01: No ping from 10. Terminating the session.
The first error message may be associated with the second error message. Until the AOS server ends session 10, each session that returns RPC error messages will stop responding. If too many sessions stop responding and return RPC error messages, the AOS server may shut down.

Cause


This problem may occur because users exit Microsoft Dynamics AX ungracefully. For example, users end the Microsoft Dynamics AX process by using Task Manager.

RPC 1726 is a general connection error message. However, the RPC 1726 error message may be associated with the "No ping from 10. Terminating the session" error message. In this case, the problem is typically caused by users exiting Microsoft Dynamics AX ungracefully.

Resolution


If you experience this problem on the Microsoft Dynamics AX client, do not exit the client by pressing CTRL+ALT+DEL. We recommend that you use CTRL+Break and then wait for the system to become responsive again or contact the Microsoft Dynamics AX administrator or another user who has rights to the online users form. The administrator or the other user can click End Session to shut down the client session.

More Information


If you experience this problem on the AOS server, it is important to determine which session is the cause and what the users are doing to cause the problem.

To do this, run the following script:
select * from sysuserlog where logouttime = 0 and sessionid = <X> 
Note Replace <X> with the session that is indicated in the RPC error message. From the results of the query, note the USERID and COMPUTERNAME columns. The column values indicate who is logging in and from where.

Typically, RPC exceptions are caused by ungracefully exiting the application. However, the exceptions may also indicate that a business process is hanging or taking a long time.

References


For more information, click the following article number to view the article in the Microsoft Knowledge Base:

953375 How to find a user ID that is associated with a session ID of a "RPC error: RPC exception 1726 occurred in session [SessionID]" error message in the Application log on the AOS server in Microsoft Dynamics AX

953374 You receive a warning message in the Application log on the AOS server in Microsoft Dynamics AX: "SPID [SPID_number] for Session Id [SessionID], is still present in the database. Please delete the SPID from the database"