Error message when you try to offer Remote Assistance from an expert computer that is running Windows Server 2008 or Windows Vista: “Windows Remote Assistance is closing”

Symptoms
On an expert computer that is running Windows Server 2008 or Windows Vista, you try to offer Remote Assistance to a novice computer. However, the operationfails, and you receive the following error message:

Windows Remote Assistance is closing. An unknown error occurred so the session was disconnected.
Try restarting your session. If you continue to get this message, contact your administrator or technical support. Additionally, the following event is logged in the Application log on the expert computer:
Source: Microsoft-Windows-RemoteAssistance
Date: Time
Event ID: 3
Task Category: None
Level: Critical
Keywords:
User: User
Computer: Computer
Description: Application will terminate, a critical error was detected in File Path
Resolution
Remote Assistance (Msra.exe) uses the RDP collaboration component (Rdpencom.dll) to establish a connection between the expert computer and the novice computer. When it tries toestablish the connection, Remote Assistance uses an IPv4 address to fill a buffer that is intended to hold an IPv6 address. This behavior breaks the connection.

You cannot perform certain disk-related operations after a VSS hardware provider fails to create a snapshot on a computer that is running Windows Server 2008 or Windows Vista

Symptoms
Consider the following scenario:You create a volume that covers one or more disks on a computer that is running Windows Vista or Windows Server 2008.A Volume Shadow Copy Service (VSS) hardware provider tries tocreate a snapshot of the volume. However,an exception occurs and the action is unsuccessful. In this scenario, you are cannot perform certain operations on the disks. The following common disk-related operations that you perform may fail:You back up one of these disks by using a backup application such as System Center Date Protection Manager (DPM).One of these disks isused as a shared disk in a Windows failover cluster. However, you cannot bring the shared disk online.You run an application that calls the ResourceControl callback function together with the CLUSCTL_RESOURCE_STORAGE_GET_DISK_INFO_EX resource control code against these disks. Then, the application returns error code 1168.
Resolution
As the snapshot of a volume is being created, VSS sets the disks that are covered by the volume to a special state. When the snapshot is finished, VSS resets the disks to the normal state. If a VSS hardware provider fails tocreate a snapshot of a volume, VSS never sets the disks back to the normal state. This causes the disks to be in an incorrect state.

Troubleshooting AD Replication error 8446: The replication operation failed to allocate memory

Symptoms
This article describes the symptoms, cause, and resolution steps for issues when Active Directory replication fails with error 8446: β€œThe replication operation failed to allocate memory”
1. REPADMIN.exe reports that replication attempt has failed with error β€œ8446” – The Replication operation failed to allocate memory
DC=Contoso,DC=com
    Default-First-Site-Name\DomainController via RPC
        DC object GUID: <source DCs ntds settings object object guid>
        Last attempt @ <Date Time> failed, result 8446 (0x20fe):
            The replication operation failed to allocate memory.
        1359 consecutive failure(s).
        Last success @ <Date & Time>.
 CN=Configuration,DC=Contoso,DC=com
    Default-First-Site-Name\DomainController via RPC
        DC object GUID: <source DCs ntds settings object object guid>
        Last attempt @ <Date Time> failed, result 8446 (0x20fe):
            The replication operation failed to allocate memory.
        1358 consecutive failure(s).
        Last success @ <Date & Time>.
Source: Default-First-Site-Name\DomainController
******* 1359 CONSECUTIVE FAILURES since <Date Time>
Last error: 8446 (0x20fe):
  The replication operation failed to allocate memory.
2. DCPROMO fails with error 1130
06/05 09:55:33 [INFO] Error – Active Directory could not replicate the directory partition CN=Configuration,DC=contoso,DC=com from the remote domain controller 5thWardDC1.contoso.com. (1130)
06/05 09:55:33 [INFO] NtdsInstall for domain.net returned 1130
06/05 09:55:33 [INFO] DsRolepInstallDs returned 1130
06/05 09:55:33 [ERROR] Failed to install to Directory Service (1130)
Non critical replication returned 1130
err.exe 1130 
ERROR_NOT_ENOUGH_SERVER_MEMORY / Not enough server storage is available to process this command.
3. NTDS Replication, NTDS General Events with the 8466 status are logged in the directory service event log.
Event Source
Event ID
Event String
NTDS Replication
1699
The local domain controller failed to retrieve the changes requested for the following directory partition. As a result, it was unable to send the change requests to the domain controller at the following network address.
 
8446 The replication operation failed to allocate memory
 
NTDS General
1079
Active Directory could not allocate enough memory to process replication tasks. Replication might be affected until more memory is available
 
Increase the amount of physical memory or virtual memory and restart this domain controller
 
 
 
 
 
4. When you try to manually initiate replication using Repadmin or Active Directory Sites and Services you get the following error message:
The following error occurred during the attempt to synchronize naming context Contoso.com from domain controller <Source DC > to domain controller <Destination DC>:
The replication Operation failed to allocate memory. This operation will not continue.
 
5. The domain controller may become unresponsive and a reboot will provide a temporary workaround. 
Resolution
The 8446 (operation failed to allocate memory. This operation will not continue) status can occur when the Active Directory replication engine cannot allocate memory to perform Active directory replication.
These events can occur due to the following conditions:
Low available physical memory 
Low available paging file size versus physical memory (Wrong configuration of paging file) : Paging file should be 1.5 times the size of physical memory
Paged Pool or Non-Paged pool exhaustion in the kernel
LSASS Virtual memory depletion on 32 bit domain controllers. This is where the Virtual Memory of LSASS reaches the 2 GB limit of virtual memory available for a process running in user mode.
The Virtual Memory depletion could be a leak inside the LSASS User mode Process, or the Database Cache (ESE Cache) may be consuming all the available memory.
The following information is important to understand:
Lsass.exe memory usage on domain controllers has two major components: one fixed and one variable.                                         
The fixed component is made up of the code, the stacks, the heaps, and various fixed size data structures (for example, the schema cache). The amount of memory that LSASS uses may vary, depending on the load on the computer. As the number of running threads increases, so does the number of memory stacks. Lsass.exe usually uses 100 MB to 300 MB of memory. Lsass.exe uses the same amount of memory no matter how much RAM is installed in the computer.  
The variable component is the database buffer cache. The size of the cache can range from less than 1 MB to the size of the entire database. Because a larger cache improves performance, the database engine for AD (ESENT) attempts to keep the cache as large as possible. While the size of the cache varies with memory pressure in the computer, the maximum size of the cache is limited by both the amount of physical RAM installed in the computer and by the amount of available virtual address space (VA). AD uses only a portion of total VA space for the cache.

Activation Error Code 0x8004FE92

Symptoms
When attempting to activate Windows you encounter error code 0x8004FE92
Resolution
Microsoft has identified three potential causes of this error code.Incorrect KMS Client product key is being used.
Insufficent number of KMS Clients on the network to allow KMS Activation.
Internet Activation process is unable to contact Microsoft’s Internet Activation Server.

SQL Server Questions and Answers, SQL QA