Network Information Service is exiting: LDAP Error

Details
Product: Windows Operating System
Event ID: 8231
Source: Nissvc
Version: 5.2.3790.1830
Message: Network Information Service is exiting: LDAP Error
   
Explanation

Network Information Service (NIS) is closing due to a Lightweight Directory Access Protocol (LDAP) error. Client requests will fail.

Cause

Event 8231:  Server for NIS is unable to start. A Lightweight Directory Access Protocol (LDAP) error has occurred.

   
User Action

Event 8231:  Server for NIS is unable to start. A Lightweight Directory Access Protocol (LDAP) error has occurred. Server for NIS was unable to communicate with the LDAP server. Open Event Viewer and read the associated error message, which describes the root cause of this error.A possible cause of this error is that the server on which Server for NIS is running is no longer an Active Directory domain controller. Contact Support Options from Microsoft Services for specific resolution information.

Related:

NT to UNIX Password Sync Service Password propagation failed – Unix to Windows : Password syncronization not configured

Details
Product: Windows Operating System
Event ID: 8226
Source: NT to UNIX Password Sync Service
Version: 5.2.3790.1830
Message: NT to UNIX Password Sync Service Password propagation failed – Unix to Windows : Password syncronization not configured
   
Explanation

Password Synchronization failed when attempting to synchronize passwords from a UNIX environment to a Windows NT environment. Password propagation failed because Password Synchronization is not properly configured.

Cause

Event 8226:  The password change request from hostname is rejected because hostname is an untrusted host.

   
User Action

Event 8226:  The password change request from hostname has been rejected because hostname is an untrusted host. This typically occurs when Password Synchronization receives a synchronization request from a UNIX host that has not been added to the list of trusted UNIX hosts in the Identity Management for UNIX console. For more information about adding UNIX-based hosts to your Password Synchronization configuration, see Add and remove computers for synchronization (http://go.microsoft.com/fwlink/?LinkId=52921) in the Password Synchronization Help.

Related:

FSRM: File blocked by screening

Details
Product: Windows Operating System
Event ID: 8215
Source: srmsvc
Version: 5.2.3790.1830
Message: FSRM: File blocked by screening
   
Explanation

A user has attempted to save an unauthorized file to a directory under file screen management.

Cause

This alert is expected under normal operation.

   
User Action

These events just provide an alert that a user has attempted to save an unauthorized file. Normally, you do not need to take action and can just monitor the activity.

Related:

NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : LDAP Error

Details
Product: Windows Operating System
Event ID: 8209
Source: NT to UNIX Password Sync Service
Version: 5.2.3790.1830
Message: NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : LDAP Error
   
Explanation

Password Synchronization failed when attempting to synchronize passwords from a Windows NT environment to a UNIX environment. Password propogation failed due to a Lightweight Directory Access Protocol (LDAP) error.

Cause

Event 8209:  A failure searching Active Directory occurred. Password propagation failed.

   
User Action

Event 8209:  A failure searching Active Directory occurred. Password propagation failed.  If restarting Password Synchronization fails to correct this error, contact Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=52267) for specific resolution information.

Related:

NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : No Ports

Details
Product: Windows Operating System
Event ID: 8206
Source: NT to UNIX Password Sync Service
Version: 5.2.3790.1830
Message: NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : No Ports
   
Explanation

Password Synchronization failed when attempting to synchronize passwords from a Windows NT environment to a UNIX environment. Password propogation failed because all ports are in use.

Cause

Event 8206:  Password propagation failed. All ports are in use.

   
User Action

Event 8206:  Password propagation failed. All ports are in use. This is an extremely rare error; restarting the computer on which Password Synchronization is installed should clear the error.

Related:

Network Information Service is exiting: RPC Error

Details
Product: Windows Operating System
Event ID: 8202
Source: Nissvc
Version: 5.2.3790.1830
Message: Network Information Service is exiting: RPC Error
   
Explanation

Network Information Service (NIS) is closing due to an RPC error. Client requests will fail.

Cause

Event 8202:  Server for NIS closed because it was unable to register RPC service service_name. Use the rpcinfo utility to delete port registrations for YPSERV and YPPASSWD.

   
User Action

Event 8202:  Server for NIS stopped because it was unable to register RPC service service_name. Verify that the RPC service is installed and running, and then open the rpcinfo utility to delete port registrations for YPSERV and YPPASSWD. To delete port registrations, do the following:

  1. In a command window, enter rpcinfo -p server_name to list all port bindings. Locate the port bindings for YPSERV and YPPASSWD.
  2. Enter rpcinfo -d port_binding to delete port registration for YPSERV and YPPASSWD.
  3. Restart Server for NIS.
  4. If the RPC service is not running, start the RPC service.
  5. Contact Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=52267) if the problem persists.

Related:

NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : Unable to resolve hostname

Details
Product: Windows Operating System
Event ID: 8200
Source: NT to UNIX Password Sync Service
Version: 5.2.3790.1830
Message: NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : Unable to resolve hostname
   
Explanation

Password Synchronization failed when attempting to synchronize passwords from a Windows NT environment to a UNIX environment. Password propogation failed because Password Synchronization was unable to resolve a host name.

Cause

Event 8200:  Hostname is an unknown host. Verify that the host name is valid and that it resolves to a valid IP address.

   
User Action

Event 8200:  Hostname is an unknown host. Verify that the host name is valid and that it resolves to a valid IP address. Check the configuration setting on the UNIX host computer and run the ping command on the host to verify that a valid IP is granted. If you cannot obtain a valid IP, contact the administrator for your network.

Related:

NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : Undiagnosable failure

Details
Product: Windows Operating System
Event ID: 8196
Source: NT to UNIX Password Sync Service
Version: 5.2.3790.1830
Message: NT to UNIX Password Sync Service Password propagation failed – Windows to Unix : Undiagnosable failure
   
Explanation

Password Synchronization failed when attempting to synchronize passwords from a Windows NT environment to a UNIX environment. Password propogation failed.

Cause

Event 8196:  An error occurred during password propagation for user username on host hostname. This failure is undiagnosable.

   
User Action

Event 8196:  An error occurred during password propagation for user username on host hostname. This failure is undiagnosable, and no corrective recommendations are available; however, viewing preceding messages in the Event Viewer can help you identify the exact failure point. Contact Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=52267) for specific resolution information if the problem persists.

Related:

Network Information Service is exiting: Memory Access Error

Details
Product: Windows Operating System
Event ID: 8195
Source: Nissvc
Version: 5.2.3790.1830
Message: Network Information Service is exiting: Memory Access Error
   
Explanation

Network Information Service (NIS) is closing due to a memory allocation error. Client requests will fail.

Cause

Event 8195:  Memory allocation has failed in Server for NIS.

   
User Action

Event 8195:  Memory allocation has failed in Server for NIS. This can occur if the Windows Server operating system has insufficient virtual memory. Close idle applications to free as much virtual memory as possible, and contact Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=52267) if reducing the amount of virtual memory in use fails to correct the problem.

Related:

Volume Shadow Copy Service: Writers does not have enough privileges to create Shadow Copy

Details
Product: Windows Operating System
Event ID: 8213
Source: VSS
Version: 5.2.3790.1830
Message: Volume Shadow Copy Service: Writers does not have enough privileges to create Shadow Copy
   
Explanation

This event indicates that the writer user account has not been assigned the appropriate privileges. Volume Shadow Copy Service can interact with writers running under the Local System account, local Administrators or local Backup Operators accounts. It can also interact with writers not running under one of those accounts if the account is added to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl.

Cause

The causes for this event are:

  • The writer is not running under the Local System user account.
  • The writer is not running under an account that is a member of the local Administrators or Backup Operators group.
  • The writer account is not listed under the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl.
   
User Action

Do one of the following:

  • Run the writer under the Local System account.
  • Run the writer under an account that is a member of the local Administrators or Backup Operators group.
  • Add the writer user account to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControlCaution: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

Related: