You are currently offline, waiting for your internet to reconnect

CRT Conflict with Getservbyname

This article was previously published under Q177653
This article has been archived. It is offered "as is" and will no longer be updated.
When you use the getservbyname() function, an error is returned and theServices file located in %SystemRoot\System32\Drivers\Etc cannot beprocessed.
When C runtimes (CRTs) are linked dynamically (/MD - use Msvcrt.dll), themodules share one copy of the _fmode global variable. A change from itsdefault _O_TEXT to _O_BINARY affects all modules, causing getservbyname tofail 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 thatchanging the value of _fmode in the program changes the default mode forfopen throughout the .exe, but the default mode for any calls to fopenfrom the sockets DLL accesses the _fmode variable in CRT DLL whose valueis _O_TEXT; therefore, no failure.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Note that a specific version of this hotfix is now available for customersseeing this issue on Windows NT Terminal Server. Please contact MicrosoftCustomer support to obtain this fix.
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Article ID: 177653 - Last Review: 10/07/2013 16:11:51 - Revision: 2.1

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB177653