Article ID: 236110
Article Last Modified on 11/8/2003
APPLIES TO
- Microsoft SNA Server 4.0 Service Pack 2
This article was previously published under Q236110
SYMPTOMS
When a Windows 95 or Windows 98 client isn't participating in the same Windows NT domain (or trusted domain) as the SNA Server, and you choose the Test Connection option through the Microsoft OLE DB Provider for DB2, the Data Link Properties dialog box may stop responding (hang).
To Reproduce the Problem
- Install the SNA Server 4.0 Service Pack 2 (SP2) Windows 95 or Windows 98 client on a Windows 95 or Windows 98 computer.
- In the Windows 95 or Windows 98 Control Panel, double-click Network, click the Configuration tab, click Client for Microsoft Network, and click Properties.
- Click to clear the Log on to Windows NT Domain check box, which causes Windows 95 or Windows 98 to not participate in any domain, and restart the computer.
- Create a new Data Link to connect to DB2.
- Click Test Connection. This causes the SNA Windows 95 or Windows 98 SnaBase logon dialog box to appear (if SnaBase is not already running), prompting you to enter your Windows NT user ID, password, and domain. Enter the logon information, and click OK.
- The Data Link Property dialog box hangs.
CAUSE
The SNA Server 4.0 SP2 version of the OLE DB Provider for DB2 supports connectivity over APPC (over SNA LU6.2) or TCP/IP, while previous versions only supported APPC. As part of this change, Db2wappc.dll (the APPC transport for the OLE DB Provider for DB2) was modified so that the APPC interface (Wappc32.dll) is loaded and initialized within its DLL_PROCESS_ATTACH entry point, which causes a deadlock under certain timing conditions.
RESOLUTION
To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
WORKAROUND
Change the Windows 95 or Windows 98 networking configuration so that the computer is participating in the same Windows NT domain as the SNA Server.
STATUS
Microsoft has confirmed that this is a problem in Microsoft SNA Server 4.0 SP2. This problem was first corrected in SNA Server version 4.0 Service Pack 3.
Keywords: kbbug kbfix kbsna400sp3fix kbqfe KB236110
