CRT Conflict with Getservbyname

 Last reviewed: February 13, 1998
Article ID: Q177653
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

When you use the getservbyname() function, an error is returned and the Services file located in %SystemRoot\System32\Drivers\Etc cannot be processed.

CAUSE

When C runtimes (CRTs) are linked dynamically (/MD - use Msvcrt.dll), the modules share one copy of the _fmode global variable. A change from its default _O_TEXT to _O_BINARY affects all modules, causing getservbyname to fail because it expects _O_TEXT.

When the CRT is linked statically, there are multiple copies of the CRT (and, therefore, multiple copies of _fmode) involved, meaning that changing the value of _fmode in the program changes the default mode for fopen throughout the .exe, but the default mode for any calls to fopen from the sockets DLL accesses the _fmode variable in CRT DLL whose value is _O_TEXT; therefore, no failure.

RESOLUTION

To resolve this problem, obtain the following fix or wait for the next Windows NT service pack.

This fix should have the following time stamps: 

   09/02/97  08:32p                70,416 Mswsock.dll (Intel)
   09/02/97  08:32p                38,160 Rnr20.dll   (Intel)
   09/02/97  08:32p                59,664 Ws2_32.dll  (Intel)
   09/02/97  08:32p                20,240 Wsock32.dll (Intel)

   09/02/97  08:30p               111,376 Mswsock.dll (Alpha)
   09/02/97  08:30p                63,248 Rnr20.dll   (Alpha)
   09/02/97  08:30p               108,816 Ws2_32.dll  (Alpha)
   09/02/97  08:30p                24,848 Wsock32.dll (Alpha)

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. 

Keywords          : kbbug4.00 kbfix4.00 NTPROTOCOL NTSrvWkst
Version           : WinNT:4.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 13, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.