Article ID: 2621019 - View products that this article applies to.
Consider the following scenario:
In this scenario, the IP-DLC link service may experience an access violation in the snaipdlc!nds_next_fsm_action function, and the mainframe connection is disconnected.
This issue occurs because of an internal trace statement that is trying to examine a field in a control block that has already been released from memory.
Microsoft Host Integration Server 2010The hotfix that resolves this issue is included in cumulative update package 2 for Host Integration Server 2010.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2616519/ )Cumulative update package 2 for Host Integration Server 2010
To work around this issue, restore the original Snaipdlc.dll file that you previously replaced by the Trcipdlc.dll file.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The Trcipdlc.dll file is a debug version of the Snaipdlc.dll file. Typically, the Trcipdlc.dll file is only used when Microsoft Support requires additional trace data that is not captured with the standard Snaipdlc.dll file. The following steps are used when the Trcipdlc.dll file is needed for troubleshooting.
Article ID: 2621019 - Last Review: December 21, 2011 - Revision: 1.0
Contact us for more help