The Network Information Service (NIS) service stops responding on a Windows Server 2003 R2-based computer

On a Windows Server 2003 R2-based Server, the Network Information Service (NIS) service stops responding. Additionally, the following events are logged:

Event Type: Error
Event Source: nissvc
Event Category: None
Event ID: 8208
Date: date
Time: time
User: N/A
Computer: computer name
Description: The service has exited because it was unable to register RPC service YP. Use the rpcinfo utility to delete the port registrations for YPSERV and YPPASSWD.

Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Date: date
Time: time
User: N/A
Computer: computer name
Description: The application, C:\WINDOWS\idmu\nis\nissvc.exe, generated an application error The error occurred on <time & date> The exception generated was c0000005 at address 000007FF7FC53198 (msvcrt!strncpy)

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: date
Time: time
User: N/A
Computer: computer name
Description: Faulting application nissvc.exe, version 9.0.3790.2075, faulting module msvcrt.dll, version 7.0.3790.3959, fault address 0x0000000000053198.
Data:

The issue causes authentications on UNIX clients to stop responding. This issue also leaves users unable to run applications or to access data on UNIX-based computers.

Note This issue occurs predominantly on computers that are running x64 versions of Windows Server 2003.

This issue occurs because the Nissvc.exe process incorrectly uses the strncpy function. When a string that is not terminated by using the value NULL passes as a source, this function encounters an access violation. Therefore, the NIS service stops responding.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 R2 Service Pack 1 or Windows Server 2003 R2 Service Pack 2 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 R2 with SP2, x86-based versions

Windows Server 2003 R2 with SP2, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Server for NIS integrates Windows and Network Information Service (NIS) networks by enabling a Windows�based Active Directory domain controller to act as a master NIS server for one or more NIS domains. Server for NIS stores both standard and non-standard NIS map data in the Active Directory directory service. Standard maps consist of the following NIS mapnames:

• aliases
• bootparams
• ethers
• hosts
• group
• netgroup
• netid
• netmasks
• networks
• passwd
• protocols
• rpc
• services
• pservers
• shadow

All other maps are non-standard.

For more information about NIS, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base: