MMC cannot create the snap-in because of current user policy

I do not need a solution (just sharing information)

I was getting this error when after installing Endpoint Encryption 11.2 on a brand new server.  I got the error on the Software Setup and the Management password.

The problem is with Microsoft Management Console and requires a registry fix.

Make sure you export your registry before trying the following:

MMC Cannot create the snap-in because of current user policies.

         

1.         Start Registry Editor (regedit.exe).

2.         Move to HKEY_CURRENT_USERSoftwarePoliciesMicrosoftMMC

3.         Open the CLSID number giving the error

4  .      Double click RestrictToPermittedSnapins or something close to this

5.         Set to 0 and click OK

6.         Close the registry editor

0

Related:

  • No Related Posts

The server’s Registry key %1 was not present. The server could not start.

Details
Product: Windows Operating System
Event ID: 2501
Source: NCP Server
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SRV_KEY_NOT_FOUND
Message: The server’s Registry key %1 was not present. The server could not start.
   
Explanation

The registry is corrupted.

   
User Action

Ask the person with administrative rights on your computer to reinstall the registry from the Emergency Repair Disk that was made when Windows 2000 was installed.

Related:

Process %1 (PID=%2). The ‘PreloadBaseDNs’ and ‘PreloadFilters’ registry keys do not contain the same number of entries. ‘PreloadBaseDNs’ contains %3 strings and ‘PreloadFilters’ contains %4 strings. Only the first %5 preload filters will be used. Each entry in PreloadBaseDNs registry key must match an entry in PreloadFilters registry key. To resolve this error, make sure that number of entries in PreloadBaseDNs registry key equals the number of entries in PreloadFilters registry key.

Details
Product: Exchange
Event ID: 2076
Source: MSExchange ADAccess
Version: 8.0
Symbolic Name: DSC_EVENT_PRELOAD_MISCONFIG
Message: Process %1 (PID=%2). The ‘PreloadBaseDNs’ and ‘PreloadFilters’ registry keys do not contain the same number of entries. ‘PreloadBaseDNs’ contains %3 strings and ‘PreloadFilters’ contains %4 strings. Only the first %5 preload filters will be used. Each entry in PreloadBaseDNs registry key must match an entry in PreloadFilters registry key. To resolve this error, make sure that number of entries in PreloadBaseDNs registry key equals the number of entries in PreloadFilters registry key.
   
Explanation

This Error event indicates that the DSAccess search preload was configured in the Windows registry but the number of entries in the PreloadBaseDNs registry key does not match the number of entries in the PreloadFilters registry key. If you set appropriate values for the preload registry keys, you can enhance performance of the Exchange server and reduce load on the Active Directory® directory service.

A BaseDN is a starting point in the Active Directory hierarchy where any given search will start. The PreloadBaseDNs registry key contains multiple BaseDN entries. The PreloadFilters registry key specifies a search filter. The PreloadFilters registry key also contains multiple entries. Each entry in the PreloadBaseDNs registry key must match an entry in the PreloadFilters registry key.

   
User Action

To resolve this error, make sure that number of entries in the PreloadBaseDNs registry key equals the number of entries in the PreloadFilters registry key.

For more information, see Microsoft Knowledge Base article 250572, XCON: Preloading and the DSAccess Cache.

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 server’s Registry key %1 was not present and could not be created. The server could not start.

Details
Product: Windows Operating System
Event ID: 2502
Source: NCP Server
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SRV_KEY_NOT_CREATED
Message: The server’s Registry key %1 was not present and could not be created. The server could not start.
   
Explanation

The registry is corrupted.

   
User Action

Ask the person with administrative rights on your computer to reinstall the registry from the Emergency Repair Disk that was made when Windows 2000 was installed.

Related:

Windows cannot load your profile because it may be corrupted. Contact your administrator.

Details
Product: Windows Operating System
Event ID: 1510
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_FAILED_LOAD_1009
Message: Windows cannot load your profile because it may be corrupted. Contact your administrator.
   
Explanation

This error indicates that the profile registry hive is corrupt.

   
User Action

To troubleshoot this problem, try the following:

  • Replace the ntuser.dat file with a backup copy of this file.

Related:

Outlook Web Access was unable to initialize.Invalid forms registry file %1 Line number = %2 Position = %3. Message = %4.The forms registry is a critical component of Outlook Web Access. If this error is not addressed, users might not be able to access the Outlook Web Access client. For information about how to troubleshoot the forms registry, see the Help and Support Center.

Details
Product: Exchange
Event ID: 9
Source: MSExchange OWA
Version: 8.0
Symbolic Name: FormsRegistryParseError
Message: Outlook Web Access was unable to initialize.Invalid forms registry file %1 Line number = %2 Position = %3. Message = %4.The forms registry is a critical component of Outlook Web Access. If this error is not addressed, users might not be able to access the Outlook Web Access client. For information about how to troubleshoot the forms registry, see the Help and Support Center.
   
Explanation

This Error event indicates that there is an error in the specified forms registry.

   
User Action

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

  • Open the specified forms registry and try to determine the problem.

  • If you have difficulty resolving the issue, 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: