Failed to register to settings change notifications in the Active Directory for virtual directory “%1” under web site “%2″. Exception message:”%3”.

Details
Product: Exchange
Event ID: 50
Source: MSExchange OWA
Version: 8.0
Symbolic Name: ADNotificationsRegistration
Message: Failed to register to settings change notifications in the Active Directory for virtual directory “%1” under web site “%2″. Exception message:”%3”.
   
Explanation

Outlook Web Access detects the updates the administrator makes to its settings in the Active Directory directory service by registering to receive notification of changes. This Error event indicates that Outlook Web Access was unable to register to receive notifications.

   
User Action

To resolve this error, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The time service detected a time difference of greater than %1 milliseconds for %2 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.

Details
Product: Windows Operating System
Event ID: 50
Source: w32time
Version: 5.2
Symbolic Name: MSG_LOCALCLOCK_UNSET
Message: The time service detected a time difference of greater than %1 milliseconds for %2 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
   
Explanation

A problem in Microsoft Windows Server 2003 typically causes the Windows Time service (W32Time) to log this error every time the service attempts to synchronize with an external clock.

You might also receive W32Time event log messages 38, 47, and 29 along with this message.

   
User Action
A supported hotfix to correct this specific problem will be included in the next Windows Server 2003 service pack. For additional information, see article 830092, “W32Time frequently logs Event ID 50 and poor time synchronization occurs on Windows Server 2003” in the Microsoft Knowledge Base.

Related:

{Delayed Write Failed}Windows was unable to save all the data for the file %1. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Details
Product: Windows Operating System
Event ID: 50
Source: ntfs
Version: 5.2
Symbolic Name: IO_LOST_DELAYED_WRITE
Message: {Delayed Write Failed}Windows was unable to save all the data for the file %1. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
   
Explanation

Windows could not save data from memory to a disk because of problems with network connections or with hardware. The data has been lost.

   
User Action

If the data is still in memory, try to save it again.
To determine the root cause of the problem, look in Event Viewer for messages that indicate problems with your disk or network connection.

Related:

The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client.

Details
Product: Windows Operating System
Event ID: 50
Source: TermDD
Version: 5.2
Symbolic Name: STATUS_RDP_PROTOCOL_ERROR
Message: The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client.
   
Explanation

This error can occur if a terminal server receives packets over a Remote Desktop Protocol (RDP) connection that it cannot process.

   
User Action

To diagnose the specific problem, in the Event Viewer system log, review the Data section in the Event Properties dialog box for event ID 50, Source: TermDD.

If the message description displayed in the Event Properties dialog box indicates that data encryption is the problem, see articles 323497, 307454, and 811770 in the Microsoft Knowledge Base. These articles provide information on how to resolve problems with RDP data encryption.

If the message description indicates that X.224 is the problem, see article 312313 in the Microsoft Knowledge Base. This article provides more information on how to resolve problems with X.224.

Related:

NTFS – Delayed Write Lost

Details
Product: Windows Operating System
Event ID: 50
Source: ntfs
Version: 5.2.3790.1830
Message: NTFS – Delayed Write Lost
   
Explanation

Microsoft® Windows® was unable to write the data cache from memory to the disk. This error might have been caused by a failure of your computer hardware or network connection.

Cause

Possible causes include:

  • If you were writing to removable media (such as a floppy disk or CD-R), the media might have been taken away before the data cache could be cleared.
  • The disk resource that you were writing to went offline.
  • You were writing to a remote disk and the network connection between your computer and the remote disk was severed.
   
User Action

Do one or more of the following:

  • Check the network connection.
  • Check the disk integrity. For disks that are formatted with the NTFS file system, you should examine the disk because it might be nearing failure.
  • Review the application log in Event Viewer for the file name.
  • Check the system or application logs for entries related to the disk stack. If there are entries in the logs related to the disk stack, it is likely that the event occurred because of a hardware failure.

Related Resources

For more information about Event ID 50, see Knowledge Base article 816004 “Description of the Event ID 50 Error Message,” at http://go.microsoft.com/fwlink/?LinkId=25977.

Related: