Event ID 8210 — Server for NIS Functionality — YP Response Service

Event ID 8210 — Server for NIS Functionality — YP Response Service

Updated: November 14, 2007

Applies To: Windows Server 2008

Server for NIS is responsible for servicing YP-based Network Information Service (NIS) calls from UNIX-based NIS clients. Server for NIS Functionality — YP Response Service provides information to help you interpret system messages indicating the operability of the YP response service.

Event Details

Product: Windows Identity Management for UNIX
ID: 8210
Source: Microsoft-Windows-IDMU-ServerForNIS
Version: 6.0
Symbolic Name: MSG_INCREMENTAL_SEARCH_FAIL
Message: Incremental search on Active Directory Domain Services failed.

Resolve
Restart Server for NIS (LDAP error)

The push thread that updates maps on subordinate (sometimes known as “slave”) servers has failed. This failure is typically the result of an unexpected failure of LDAP routines.

  1. Verify in the Service Control Manager (SCM) that the LDAP service is running and that the host computer is a domain controller. The error message should have more details on the exact nature of the failure.
  2. Try restarting the Server for NIS service.

    To restart Server for NIS by using the Windows interface:

    1. Open the Identity Management for UNIX management console.
    2. If necessary, connect to the computer you want to manage.
    3. Right-click Server for NIS, and then click Stop.
    4. Right-click Server for NIS again, and then click Start.

    To restart Server for NIS by using a command line:

    1. Open a Command Prompt window.
    2. Type the following, and then press ENTER.
      • nisadmin [server] stop [–u user [–p password]]
    3. Type the following, and then press ENTER.
      • nisadmin [server] start [–u user [–p password]]

    For more information, see the topic “Start or stop Identity Management for UNIX components” in the Identity Management for UNIX Help.

  3. If this fails, restart the computer on which Server for NIS is running.
    • To restart the computer, click Start, click the arrow next to the Lock button, and then click Restart.

Verify

Server for NIS YP response functionality can be verified by observing the following.

  • On a UNIX-based NIS client computer, try logging on as an NIS user. If the Windows-based NIS server that is running Server for NIS is functioning properly, logging on should be successful.
  • If none of the following error messages occur in Event Viewer, Server for NIS is operating normally. If any of the following error messages occur in Event Viewer, warning conditions exist that could prevent the Server for NIS YP Response Service from operating normally.
    • IDMU Server for NIS event 8210
    • IDMU Server for NIS event 8226

Related Management Information

Server for NIS Functionality — YP Response Service

Identity Management for UNIX

Related:

Event ID 8233 — Server for NIS Service Availability

Event ID 8233 — Server for NIS Service Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Server for NIS service availability indicates the functional state of the Server for NIS service. When Server for NIS is available, it updates NIS maps on all subordinate servers in the domain if it is running as an NIS master server, and accepts NIS replication data from Active Directory if it is running as a subordinate server.

Event Details

Product: Windows Identity Management for UNIX
ID: 8233
Source: Microsoft-Windows-IDMU-ServerForNIS
Version: 6.0
Symbolic Name: MSG_ERROR_WINSOCK_INIT_FAILED
Message: Failure initializing Windows Sockets: %1.

Resolve
Fix possible failures for Win32 socket initialization API

Server for NIS is closing because it experienced a failure attempting to initialize the Windows socket layer. The full text of the error message in Event Viewer contains the exact Windows error code.

To correct the error, try the following steps in order, moving on to the next step only if the current action failed to clear the error condition:

  1. Free virtual memory by closing unused applications.
  2. Restart the Server for NIS service.
  3. Restart the computer on which the error was generated.

Verify

Open the Services MMC and verify that Server for NIS is operational. If the Server for NIS service properties show that the service is not running, errors are preventing Server for NIS from operating normally.

To verify that Server for NIS is running

  1. Click Start, point to Administrative Tools, and then click Services.
  2. In the Results pane of the Services MMC, double-click Server for NIS.
  3. In the Service status area of the Server for NIS Properties dialog box, verify that the Server for NIS service shows as Started.

Use the ypcat command on a client computer in the domain on which the error was generated to verify that the Server for NIS service is available.

To use the ypcat command to verify Server for NIS service availability:

  1. On a client computer in the domain on which the error was generated, open a Windows Command Prompt with elevated privileges. To do this, right click Command Prompt on the Start menu, and then click Run as administrator.
  2. Type the following command, and then press Enter: ypcat -hNISServer-dDomain Mapname. NISServer represents the name of the server on which you want to verify that the Server for NIS Service is available. Domain represents the domain name on which you want to verify that the Server for NIS service is available. Mapname represents the name or nickname of a specific NIS map that the server on which you want to verify Server for NIS availability is expected to update.
  3. If you are prompted to provide the domain administrator account name and password, type the account name and password, and then press Enter.
  4. The ypcat Windows command-line utility prints the values of all keys from the NIS database specified by Mapname, which can be a map name or a map nickname. If the ypcat utility returns a list of key values for the maps you specified, the Server for NIS service is available.

Related Management Information

Server for NIS Service Availability

Identity Management for UNIX

Related: