Consider the following scenario:
You use the IP-DLC link service to connect to an IBM mainframe in a Microsoft Host Integration Server environment.
You replace the Snaipdlc.dll file by using the Trcipdlc.dll file to capture additional trace data while you troubleshoot an IP-DLC link service-related problem.
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 2010
The 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:
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.
Stop the SNA Server service.
Rename or back up the Snaipdlc.dll file. This file is located in the %SNAROOT% folder.
Rename the Trcipdlc.dll file as Snaipdlc.dll. The Trcipdlc.dll file is also located in the %SNAROOT% folder.
Start the SNA Server service.