Event ID 8230 — Server for NIS Service Availability

Event ID 8230 — 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: 8230
Source: Microsoft-Windows-IDMU-ServerForNIS
Version: 6.0
Symbolic Name: MSG_PREFETCHUSERNETID_FAILURE
Message: Prefetch of User and Netid maps to cache failed.

Resolve
Make sure that Server for NIS configuration is present in AD

Server for NIS is unable to start. Initial copying of User and Netid maps to the Server for NIS cache failed. It is possible that configuration information is missing from Active Directory® Domain Services.

Try running niscnfg.exe, typically found in the directory %windir%\idmu\setup\niscnfg.exe, to restore the Server for NIS configuration in Active Directory Domain Services.

To run niscnfg.exe:

  1. Open a Command Prompt window.
    • Click Start, type cmd in the Start Search text box, and then press Enter.
  2. Change to the directory %windir%\idmu\setup by typing the following, and then pressing Enter.
    • cd%windir%\idmu\setup
  3. Type niscnfg.exe, and then press Enter. When the prompt returns, the utility has completed its restoration.

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:

An inconsistency was detected in %2: file name. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.

Details
Product: Exchange
Event ID: 8230
Source: EXCDO
Version: 6.5.6940.0
Component: Microsoft Exchange Collaboration Data Objects
Message: An inconsistency was detected in %2: file name. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
   
Explanation

This Warning event is logged when a problem with a Calendar item is detected. This indicates that Exchange detected data corruption and is trying to rebuild the calendaring data for Web client viewing.

The most common cause of calendar item corruption is scanning the Exchange Installable File System (IFS) drive with file system-based antivirus software. By default, the Exchange IFS drive is drive M. Corruption can also occur when you try to back up drive M. The following articles in the Microsoft Knowledge Base may apply:

Other events in the Application log may give you more information about why this event was logged and where the corruption exists. The following events may help you discover the underlying cause of this error:

    EXCDO Event 8199: Calendaring agent failed in message save notification with error 0x80040219 on %2: %3.

    EXCDO Event 8206: Calendaring agent failed with error code 0x8004010f (MAPI_E_NOT_FOUND) while saving appointment.

    EXCDO Event 8206: Calendaring agent failed with error code 0x80040229 while saving appointment.

    EXCDO Event 8206: Calendaring agent failed with error code 0x80070057 while saving appointment.

    EXCDO Event 8207: Calendaring agent failed with error code 0x8004010f while deleting appointment.

    EXCDO Event 8208: Calendaring agent failed with error code 0xfffffae2 while expanding recurring appointments.

    EXCDO Event 8217: The processing of the recurring appointment with the subject %1 in mailbox: %2 failed with error code 0x8000ffff. This appointment will not be visible in the web client or other non-MAPI client.

    EXCDO Event 8219: The calendaring agent could not publish the free/busy information for %1 because it failed reading the registry with Error code 0x80070002. The save/delete calendar operation for %2 will not be completed. Please ensure that MSExchangeFBPublish agent is started.

    EXCDO Event 8241: An existing appointment with the subject %1 in mailbox %2 was modified. The start time, or both the duration and end time of the existing appointment were missing.

    EXCDO Event 8243: The calendaring agent cannot bind to the appointment with the subject %1 in mailbox %2 because the appointment is missing a start time. The calendaring agent will not publish free/busy information for this appointment. To correct this, please delete the appointment and recreate it.

    EXCDO Event 8255: The background calendaring agent failed to logon to the MDB, or create a session object on the MDB:%1. The error code is 0x000003ef. The rendering of large calendars with the web client or Microsoft Internet Explorer for the mailbox %2 with GUID:%3 will be slower.

    EXCDO Event 8263: The recurring appointment expansion in mailbox %1 has taken too long. Some recurring appointment instances may not be visible at this time. To ensure that the calendar view is correct, please refresh the calendar view in Microsoft Outlook Web Access.

   
User Action

To resolve this error, try one or more of the following:

  • After Exchange rebuilds the data, verify whether Exchange was able to correctly display the calendaring data on the Web client.
  • Examine the Application log for relevant EXCDO source event messages. These events may provide additional information about the underlying issue.
  • Make sure that a file system-based antivirus program running on the Exchange Server is not scanning the Exchange IFS drive (M drive). Additionally, make sure that any backup software used is not backing up the Exchange IFS drive. If the corruption cannot be isolated or corrected, restore the data from a backup. For more information, see the Microsoft Knowledge Base articles referenced earlier in this article.

Related:

An inconsistency was detected in %2: %3. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.

Details
Product: Exchange
Event ID: 8230
Source: EXCDO
Version: 6.5.7596.0
Message: An inconsistency was detected in %2: %3. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
   
Explanation

This Warning event is logged when a problem with a Calendar item is detected. This indicates that Microsoft® Exchange Server has detected data corruption and is trying to rebuild the calendar data for Web client viewing.

Calendar item corruption is usually caused when file system-based antivirus software scans the Exchange Installable File System (IFS) drive. By default, the Exchange IFS drive is drive M. Corruption can also occur when you try to back up drive M. The following articles in the Microsoft Knowledge Base may apply:

Other events in the Application log may give you more information about why this event was logged and where the corruption exists. The following events may help you discover the underlying cause of this error:

  • EXCDO Event 8199

  • EXCDO Event 8206

  • EXCDO Event 8206

  • EXCDO Event 8206

  • EXCDO Event 8207

  • EXCDO Event 8208

  • EXCDO Event 8217

  • EXCDO Event 8219

  • EXCDO Event 8241

  • EXCDO Event 8243

  • EXCDO Event 8255

  • EXCDO Event 8263

   
User Action

To resolve this error, try one or more of the following:

  • After Exchange rebuilds the data, verify whether Exchange was able to correctly display the calendar data on the Web client.

  • In Event Viewer, examine the Application log for relevant EXCDO source event messages. The descriptions of these related events may provide additional information about the underlying issue. For more information about the cause and resolution of these related events, click the “http://www.microsoft.com/contentredirect.asp” URL at the end of the description of each related event. Alternatively, you can search for more information about these related events at the Events and Errors Message Center Web site.

  • Make sure that a file system-based antivirus program running on the Exchange Server is not scanning the Exchange IFS drive (M drive). Additionally, make sure that any backup software that is used is not backing up the Exchange IFS drive. If the corruption cannot be isolated or corrected, restore the data from a backup. For more information, see the Microsoft Knowledge Base articles referenced earlier in this article.

Related:

An inconsistency was detected in : . The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.

Details
Product: Exchange
Event ID: 8230
Source: EXCDO
Version: 6.5.7638.0
Component: Microsoft Exchange Collaboration Data Objects
Message: An inconsistency was detected in <%2>: <file name>. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
   
Explanation

This Warning event is logged when a problem with a Calendar item is detected. This indicates that Exchange detected data corruption and is trying to rebuild the calendaring data for Web client viewing.

The most common cause of calendar item corruption is scanning the Exchange Installable File System (IFS) drive with file system-based antivirus software. By default, the Exchange IFS drive is drive M. Corruption can also occur when you try to back up drive M. The following articles in the Microsoft Knowledge Base may apply:

Other events in the Application log may give you more information about why this event was logged and where the corruption exists. The following events may help you discover the underlying cause of this error:

    EXCDO Event 8199: Calendaring agent failed in message save notification with error 0x80040219 on %2: %3.

    EXCDO Event 8206: Calendaring agent failed with error code 0x8004010f (MAPI_E_NOT_FOUND) while saving appointment.

    EXCDO Event 8206: Calendaring agent failed with error code 0x80040229 while saving appointment.

    EXCDO Event 8206: Calendaring agent failed with error code 0x80070057 while saving appointment.

    EXCDO Event 8207: Calendaring agent failed with error code 0x8004010f while deleting appointment.

    EXCDO Event 8208: Calendaring agent failed with error code 0xfffffae2 while expanding recurring appointments.

    EXCDO Event 8217: The processing of the recurring appointment with the subject %1 in mailbox: %2 failed with error code 0x8000ffff. This appointment will not be visible in the web client or other non-MAPI client.

    EXCDO Event 8219: The calendaring agent could not publish the free/busy information for %1 because it failed reading the registry with Error code 0x80070002. The save/delete calendar operation for %2 will not be completed. Please ensure that MSExchangeFBPublish agent is started.

    EXCDO Event 8241: An existing appointment with the subject %1 in mailbox %2 was modified. The start time, or both the duration and end time of the existing appointment were missing.

    EXCDO Event 8243: The calendaring agent cannot bind to the appointment with the subject %1 in mailbox %2 because the appointment is missing a start time. The calendaring agent will not publish free/busy information for this appointment. To correct this, please delete the appointment and recreate it.

    EXCDO Event 8255: The background calendaring agent failed to logon to the MDB, or create a session object on the MDB:%1. The error code is 0x000003ef. The rendering of large calendars with the web client or Microsoft Internet Explorer for the mailbox %2 with GUID:%3 will be slower.

    EXCDO Event 8263: The recurring appointment expansion in mailbox %1 has taken too long. Some recurring appointment instances may not be visible at this time. To ensure that the calendar view is correct, please refresh the calendar view in Microsoft Outlook Web Access.

   
User Action

To resolve this error, try one or more of the following:

  • After Exchange rebuilds the data, verify whether Exchange was able to correctly display the calendaring data on the Web client.
  • Examine the Application log for relevant EXCDO source event messages. These events may provide additional information about the underlying issue.
  • Make sure that a file system-based antivirus program running on the Exchange Server is not scanning the Exchange IFS drive (M drive). Additionally, make sure that any backup software used is not backing up the Exchange IFS drive. If the corruption cannot be isolated or corrected, restore the data from a backup. For more information, see the Microsoft Knowledge Base articles referenced earlier in this article.

Related: