| Event Id | 8198 |
| Source | Microsoft-Windows-IDMU-ServerForNIS |
| Description | Server for NIS yppush service has stopped. |
| Event Information | "According to Microsoft : Cause This event is logged when Windows failed to uninstall the update with error. Diagnose An error occured while the Server for NIS service was running. Server for NIS service failures typically occur for one or more of the following reasons: Cannot communicate with Lightweight Directory Access Protocol (LDAP) service Insufficient memory The following procedures can help you diagnose the cause of the problem. Cannot communicate with LDAP service To verify LDAP health: 1.Open the Services snap-in. 2.Verify that the LDAP service is running. 3.If the service is running, refer to the resolver, ""Start the domain controller service."" Insufficient memory To verify virtual memory: 1.Right-click My Computer and then click Properties. 2.On the Advanced tab, in the Performance area, click Settings. 3.On the Advanced tab of the Performance Options dialog box, in the Virtual Memory area, view the amount of virtual memory allocated on the machine. 4.Click Change to view the maximum allowable virtual memory. 5.If necessary, change allocated virtual memory to the size recommended in the Total paging file size for all drives area of the Virtual Memory dialog box. 6.If virtual memory use is set to maximum, perform the steps in the resolver ""Correct memory error."" ResolutionTo resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly. Cause 1.Cannot communicate with LDAP service 2.Insufficient memory Resolution 1.Start the domain controller service 2.Correct memory allocation error Start the domain controller service Server for NIS was unable to communicate with the LDAP service. Possible causes of this error can be either of the following: The server on which Server for NIS is running is no longer an Active Directory Domain Services domain controller. The LDAP service is not running. To resolve this problem: 1.Open the Services MMC snap-in (Services.msc) by clicking Start, pointing to Administrative Tools, and then clicking Services. 2.Verify that the Active Directory Domain Services domain controller service is running. If the domain controller service does not exist, the computer is probably not a domain controller. Server for NIS can run only on an Active Directory Domain Services domain controller. To promote the computer to a domain controller, see the Active Directory Domain Services Help. Run the dcpromo utility and view the Help available with the dcpromo wizard. 3.If the service is not running, double-click the service in the results pane. 4.On the General tab of the Properties dialog box, set Startup type to Automatic. 5.Click OK. Correct memory allocation error Memory allocation has failed in Server for NIS. This can occur if the Windows Server operating system has insufficient virtual memory. Try closing some applications and programs that are not required and are using large amounts of virtual memory, and then restart Server for NIS. If this fails to correct the problem, try restarting the computer. If the problem persists, verify that the computer is not configured to use the maximum amount of virtual memory: 1.Right-click My Computer and then click Properties. 2.On the Advanced tab, in the Performance area, click Settings. 3.On the Advanced tab of the Performance Options dialog box, in the Virtual Memory area, view the amount of virtual memory allocated on the machine. 4.Click Change to view the maximum allowable virtual memory. 5.If necessary, change allocated virtual memory to the size recommended in the Total paging file size for all drives area of the Virtual Memory dialog box. 6.If you have changed the allotted virtual memory amount, click Set, and then click OK. Verify Server for NIS push service functionality can be verified by pushing maps to subordinate servers. To test the functionality of the push service, change a map entry for an NIS user (you can use the users nisadmin or AdminUI for the purposes of your test). Wait for the refresh interval to elapse, and then view the NIS map stored on a UNIX-based subordinate of the master server. If your changed values are reflected in the NIS map stored on the UNIX-based NIS subordinate server, then the Server for NIS master server is functioning as expected. In the absence of any of the following error messages, the push service is functioning normally. If any of these messages occur, the push service can continue working, but warning conditions exist. IDMU Server for NIS event 8198 IDMU Server for NIS event 12288 IDMU Server for NIS event 12289 " |
| Reference Links | Event ID 8198 from Microsoft-Windows-IDMU-ServerForNIS |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.