The information in this article applies to:
SYMPTOMSWindows 95 clients using Remote Procedure Calls (RPCs) to connect to an endpoint over named pipes may receive the following error message:
CAUSEThe named pipe connection code in the Windows 95 RPC run-time libraries does not make any retry attempts after a failed named pipe connect. RESOLUTIONThis issue is resolved by the following updated file for Windows 95 and OSR2, and later versions of this file:
A version of this file that resolves this problem is included in DCOM95 for Windows 95, version 1.3, and can be downloaded from the following Microsoft Web site:
http://www.microsoft.com/com/dcom/dcom95/dcom1_3.asp STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95 and
OEM Service Release 2 (OSR2). An update to address this problem is now
available, but is not fully regression tested and should be applied only
to computers experiencing this specific problem. Unless you are severely
impacted by this specific problem, Microsoft does not recommend
implementing this update at this time. Contact Microsoft Technical Support
for additional information about the availability of this update.
MORE INFORMATION
The updated RPC stub code has been modified to retry failed named pipe
connects up to 20 times. This is identical to the method used in Microsoft
Windows NT.
Q161020 Implementing Windows 95 Updates Additional query words:
Keywords : kberrmsg kbnetwork osr1 osr2 win95 kbAPI kbRPC kbSDKPlatform kbGrpNet |
Last Reviewed: July 15, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |