WinMgmt could not initialize the core parts. This could be due to a badly installed version of WinMgmt, WinMgmt repository upgrade failure, insufficient disk space or insufficient memory.

Details
Product: Windows Operating System
Event ID: 28
Source: WinMgmt
Version: 5.2
Symbolic Name: WBEM_MC_WBEM_CORE_FAILURE
Message: WinMgmt could not initialize the core parts. This could be due to a badly installed version of WinMgmt, WinMgmt repository upgrade failure, insufficient disk space or insufficient memory.
   
Explanation

Windows Management Instrumentation (WMI) could not start. The startup process creates many Component Object Model (COM) objects, allocates memory, accesses registry keys, etc. A failure in any one of these steps can cause WMI not to start.

   
User Action

To determine why WMI could not start

  1. Open the log located at %windir%\system32\wbem\logs\wbemcore.log.
  2. In the log, look for messages containing the word “error” and examine these messages for information about failures in CoCreateInstance (when constructing a COM object), missing registry keys for COM objects, and so forth.

If the problem is with a COM component, reregister the DLLs.

To reregister the DLLs

  • At the command prompt, type:

for /f %s in (‘dir /b /s %windir%\system32\wbem\*.dll’) do regsvr32 /s %s

If the problem is insufficient memory, close some programs.

To close programs while WMI is running

  1. At the command prompt, type net stop winmgmt, and then press ENTER.
  2. Confirm that you want to stop WMI and any dependent services.
  3. Close any unnecessary programs.
  4. At the command prompt, type net start winmgmt, and then press ENTER.
  5. Restart any dependent service that you stopped in Step 2.

If the problem is insufficient hard disk space, free up some space on the system drive.

If you have tried the preceding solutions and WMI still does not start, some files in the %SystemRoot%\System32\Wbem\Repository folder might be corrupted. Correct this condition by restoring the WMI repository. Possible ways to restore the repository are:

  • If you have a good backup of the WMI repository, restore the repository from that backup. This is the preferred method.
  • Force WMI to rebuild the WMI repository from the original Managed Object Format (MOF) file. To see this procedure, go to the Microsoft Knowledge Base search page and search for a KB article by ID number 319101.

Note: If you force WMI to rebuild the repository, all static data or other changes to the repository that are not captured in the original MOF file will be lost. You should keep a copy of the corrupted file in case you need to either restore it or have Microsoft Product Support Services evaluate the corrupted files.

Related:

Windows cannot access the registry policy file, %1. (%2).

Details
Product: Windows Operating System
Event ID: 1096
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_REGISTRY_TEMPLATE_ERROR
Message: Windows cannot access the registry policy file, %1. (%2).
   
Explanation

This error indicates that there is a missing file in a Group Policy Object (GPO). GPOs reside on the domain controller’s Sysvol share, and a local GPO also resides on the local computer’s system drive.
The event indicates that the Administrative Templates client side extension was trying to access the registry.pol file. This file might be corrupt. The Event log indicates the location of the corrupted registry.pol file.

This error can also occur if the registry configuration is incorrect. Group Policy stores registry-based policy settings in the registry. If these registry keys have access control lists (ACLs) that prevent the system from writing to those values, this failure can occur.

   
User Action

To troubleshoot this problem, try the following:

  1. Make sure that the registry.pol file location is accessible.
  2. If the registry.pol file is present, it might be corrupt. To determine this, use Group Policy Object Editor to edit the GPO in which the file resides. If the Administrative Templates node under either User Configuration or Computer Configuration displays an error, you can safely assume that the registry.pol file is corrupted.
  3. To recover from corruption or a missing registry.pol file, use the Group Policy Management Console (GPMC) to restore the GPO from a backup.
  4. If the file is missing due to replication errors, the replication issue with DFS/FRS must be addressed; once the replication problems have been resolved, the error condition is resolved as well. The File Replication Service (FRS) Status Viewer tool, Sonar.exe, can be used to diagnose FRS problems. Sonar.exe is a command-line tool that allows administrators to monitor key statistics and status about members of a file replication service (FRS) replica set. Administrators can use Sonar to watch key statistics on a replica set to monitor traffic levels, backlogs, and free space.
  5. If an improper registry configuration caused the error, examine the policy registry keys of the trees HKEY_LOCAL_MACHINE (and HKEY_CURRENT_USER if the problem occurred with a specific user logged on). Deleting these subtrees can fix the problem, but be aware that any edits to the registry can cause unexpected problems and must never take place without backup precautions.

For more information about the Windows Server 2003 Sonar.exe tool, see “Sonar.exe: File Replication Service (FRS) Status Viewer” on the Windows Server 2003 Tools Web page.

For information about the layout of Group Policy information on domain controllers, see the “Group Policy Infrastructure White Paper” at the Microsoft Web site.

For information about managing distributed resources with DFS, see the “Simplifying Infrastructure Complexity with Windows Distributed File System” white paper at the Microsoft Web site.

Related:

OALGen encountered an error while generating the %1 file for version 2 and 3 differential downloads of address list ‘%2’. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error. If the cause of the problem was intentional or cannot be resolved, OALGen can be forced to post a full offline address list by creating the DWORD registry key ‘HKEY_LOCAL_MACHINE\\%3\\%4’ and setting it to 1 on this server. When OALGen next generates the offline address list, clients will perform a full OAB download. After that time, the registry key should be removed to prevent further full downloads. %5

Details
Product: Exchange
Event ID: 9360
Source: MSExchangeSA
Version: 8.0
Symbolic Name: evtOALGenDiffErrorNoPost
Message: OALGen encountered an error while generating the %1 file for version 2 and 3 differential downloads of address list ‘%2’. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error.
If the cause of the problem was intentional or cannot be resolved, OALGen can be forced to post a full offline address list by creating the DWORD registry key ‘HKEY_LOCAL_MACHINE\%3\%4’ and setting it to 1 on this server. When OALGen next generates the offline address list, clients will perform a full OAB download. After that time, the registry key should be removed to prevent further full downloads.
– %5
   
Explanation

For Microsoft Outlook clients that are running Office Outlook 2003 Service Pack 1 (SP1) or earlier, if a Microsoft Exchange server that is running Exchange Server 2003 Service Pack 2 (SP2) determines that a differences download is more efficient, and if a differences file cannot be generated on a server that is running Exchange 2003 SP2, Exchange Server will not automatically force a full offline address book (OAB) download. Instead, Exchange logs MSExchangeSA event 9360. MSExchangeSA event 9360 indicates that it was unable to produce a differences file and will not produce a full OAB file.

When this event is logged, the users running Outlook 2003 SP1 or earlier will not be able to receive OAB updates until the problem is corrected.

The offline address list has not been updated, so clients will not be able to download the current set of changes.

   
User Action

To resolve this error, do one of the following:

  • In Event Viewer, examine the Application log for events that occur before and after MSExchangeSA event 9360. These related events may help you discover the reason that Exchange cannot generate a differences file for your Outlook clients that are running Outlook 2003 SP1 or earlier.

  • Generate a full OAB download file when a differences file cannot be generated:

    Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.

  • Perform the following procedure to edit the registry.

    1. On the Exchange server, start Regedit.exe.

    2. Open the following registry key:

    3. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters

    4. Right-click Parameters, point to New, and then click DWORD Value.

    5. For the new value name, type OAL post full if diff fails.

    6. Double-click OAL post full if diff fails. In Value data, type 1. Click OK.

    7. Close Regedit.exe.

Before you edit the registry, and for information about how to edit the registry, see Microsoft Knowledge Base article 256986, Description of the Microsoft Windows Registry.

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.

   
   
Version: 6.5.7596.0
Message: OALGen encountered an error while generating the %1 file for version 2 and 3 differential downloads of address list ‘%2’. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error. If the cause of the problem was intentional or cannot be resolved, OALGen can be forced to post a full offline address list by creating the DWORD registry key ‘HKEY_LOCAL_MACHINE\\%3\\%4’ and setting it to 1 on this server. When OALGen next generates the offline address list, clients will perform a full OAB download. After that time, the registry key should be removed to prevent further full downloads. %5
   
Explanation

For Microsoft® Outlook® clients that are running Office Outlook 2003 Service Pack 1 (SP1) or an earlier version, if an Exchange server that is running Exchange Server 2003 Service Pack 2 (SP2) determines that a differences download is more efficient, and if a differences file cannot be generated on a server that is running Exchange Server 2003 SP2, Exchange Server will not automatically force a full offline address book download. Instead, Exchange logs MSExchangeSA event 9360. MSExchangeSA event 9360 indicates that it was unable to produce a differences file and will not produce a full offline address book file.

When this event is logged, the users running Outlook 2003 SP1 or an earlier version will not be able to receive offline address book updates until the problem is corrected.

   
User Action

To resolve this error, use one of the following procedures:

  • In event viewer, examine the Application log for events that occur before and after MSExchangeSA event 9360. These related events may help you discover the reason that Exchange cannot generate a differences file for your Outlook clients that are running Outlook 2003 SP1 or an earlier version.

  • Change the default behavior of the offline address book (OAB) server so that full OAB downloads are generated when a differences download cannot be generated. For more information about how to configure Exchange to generate a full OAB download when a differences download cannot be generated, see How to Generate a Full Offline Address Book Download File When a Differences File Cannot Be Generated in the Offline Address Book Best Practices Guide.

For information about best practices for Exchange Server 2003 offline address books, see the Offline Address Book Best Practices Guide.

Related:

The %1 permission settings do not grant %2 %3 permission for the COM Server application with CLSID %4 to the user %5%6 SID (%7). This security permission can be modified using the Component Services administrative tool. %1 = machine-default, application-specific; %2 = local, remote; %3 = launch, activation; %4 = ; %5 = /; %6 = .

Details
Product: Windows Operating System
Event ID: 10016
Source: DCOM
Version: 5.2
Symbolic Name: EVENT_COM_ACCESS_DENIED_IN_SERVER_ACTIVATION_OR_LAUNCH_PERMISSION
Message:

The %1 permission settings do not grant %2 %3 permission for the COM Server application with CLSID %4 to the user %5\%6 SID (%7). This security permission can be modified using the Component Services administrative tool.

%1 = machine-default, application-specific; %2 = local, remote; %3 = launch, activation; %4 = ; %5 = /; %6 = .

   
Explanation

A program, the Clsid displayed in the message, tried to start the DCOM server by using the DCOM infrastructure. Based on the security ID (SID), this user does not have the necessary permissions to start the DCOM server.

   
User Action

Verify that the user has the appropriate permissions to start the DCOM server.

To assign permissions

  1. Using Regedit, navigate to the following registry value
    HKCR\Clsid\clsid value\localserver32
    The clsid value is the information displayed in the message.
  2. In the right pane, double-click Default.
    The Edit String dialog box is displayed. Leave this dialog box open.
  3. Click Start, and then click Control Panel.
  4. Double-click Administrative Tools, and then double-click Component Services.
  5. In the Component Services snap-in, expand Computers, expand My Computer, and double-click DCOM Config.
  6. In the right pane, locate the program by using its friendly name.
  7. Right-click the program name, and then select Properties.
  8. On the Security tab, in the Launch and Activation Permissions group box, select Customize, and then click Edit.

Add the user to the permissions list, and give the user the appropriate permissions.

Related:

DCOM got error “%%%1” from the computer %2 when attempting to activate the server:%3

Details
Product: Windows Operating System
Event ID: 10006
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_REMOTE_SIDE_ERROR
Message: DCOM got error “%%%1” from the computer %2 when attempting to activate the server:%3
   
Explanation

A program on this computer could not access a program on the remote computer.

   
User Action

Do one or all of the following:

  • Review the Windows error code displayed in the message.
  • Review the remote computer’s Event Viewer for any related events indicating that a program could not be started or that an access denied error occurred.
  • If this event log indicates an out-of-memory error, tell the user to save his work, close other programs, and then try to access the server again. Or, add more system RAM.
  • If the event log indicates an access-denied error, change the DCOM permissions.

To change permissions

  1. Using Regedit, navigate to the following registry valueHKCR\Clsid\clsid value\localserver32The clsid value is the information displayed in the message.
  2. In the right pane, double-click Default.The Edit String dialog box is displayed. Leave this dialog box open.
  3. Click Start, and then click Control Panel.
  4. Double-click Administrative Tools and then double-click Component Services.
  5. In the Component Services snap-in, navigate to Computers\My Computer\DCOM Config.
  6. In the right pane, locate the program by using its friendly name.
  7. Right- click the program name and then select Properties.
  8. On the Security tab, select Customize, and then click Edit.
  9. Add the user to the permissions list.

If these steps don’t solve the problem, contact your technical support provider.

Related:

Registry settings for disabling autocomplete options in IE8

I have a script that disables all the autocomplete settings in IE6 and IE7 but with IE8 there are new settings that aren’t disabled by the script. The settings are under Tools->Content->AutoComplete->Settings

The current registry keys I’m modifying are

HKCU\Software\Microsoft\Internet Explorer\Main\FormSuggest Passwords "no"
HKCU\Software\Microsoft\Internet Explorer\Main\FormSuggest PW Ask "no"
HKCU\Software\Microsoft\Internet Explorer\Main\Use FormSuggest "no"
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\AutoComplete\AutoSuggest "no"

The settings that are not unchecked by these keys are Browsing History and Favorites. Does anyone know the registry settings that are associated with these IE settings?

Related: