Windows was unable to load the registry. This is often caused by insufficient memory or insufficient security rights. DETAIL – %1 for %2

Details
Product: Windows Operating System
Event ID: 1508
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_REGLOADKEYFAILED
Message: Windows was unable to load the registry. This is often caused by insufficient memory or insufficient security rights. DETAIL – %1 for %2
   
Explanation

Windows could not load the user’s registry information.

Possible reasons include:

  • The registry hive is corrupt.
  • You no longer have adequate privileges to the registry hive.
   
User Action

Monitor Event Viewer for additional profile events that might indicate why this occurred.

Related:

Unable to initialize due to a damaged SCT.INP or a damaged registry. Contact Microsoft Technical Support. [ ] (16)

Details
Product: Exchange
Event ID: 81
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: Unable to initialize due to a damaged SCT.INP or a damaged registry. Contact Microsoft Technical Support. [<value> <value> <value> <value>] (16)
   
Explanation

The message transfer agent (MTA) reads the default configuration from a Sct.inp file and it reads configurable information from the registry. One or both of these sources were corrupted.

   
User Action

Copy a new Sct.inp file from the Exchange CD.

Related:

Machine Check Event reported is a fatal PCI bus Parity error during a transaction type %3 at address %4 on PCI bus %5 reported to CPU %1. %2 additional error(s) are contained within the record.

The backup data in ‘%ls’ is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable.

Details
Product: SQL Server
Event ID: 3266
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: The backup data in ‘%ls’ is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable.
   
Explanation
A filemark in the backup device specified in the BACKUP or RESTORE operation could not be read. Possible reasons include:

  • A media failure on the device where the backup is located.
  • A write failure during the creation of the backup, for example, a loss of connectivity during a network backup.
  • Often an operating system error will also be reported, such as when the disk is out of space or the path is not found. If so, this will indicate the underlying cause of the error.

For more information about this message, see Microsoft Knowledge Base article 290787.

   
User Action
Follow these steps:

  • Check the output from your BACKUP or RESTORE command as well as the SQL Server error log for related errors and troubleshoot them.
  • Verify that the specified backup file is not damaged.
  • If the backup device specified in the BACKUP or RESTORE command is on a remote server, retry the operation when connectivity between the machines will not be a problem, or move the backup device to the local server.
  • You can not add more backups to a disk file in this condition. If you want to back up to this disk file, use WITH FORMAT to overwrite it. If you want to restore from the damaged backup file, and there is more than one backup set in the file, some of those backup sets may be usable. Use RESTORE HEADERONLY or RESTORE VERIFYONLY to find out what is in that backup file and whether any of the backup sets are usable.

Related:

Could not connect to server ‘%ls’ because ‘%ls’ is not defined as a remote login at the server.

Details
Product: SQL Server
Event ID: 18483
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Could not connect to server ‘%ls’ because ‘%ls’ is not defined as a remote login at the server.
   
Explanation
Setting up security for executing remote procedure calls (RPC) against a remote server involves setting up login mappings in the remote server and possibly in the local server running an instance of Microsoft SQL Server. The mapping is specific to a given server\instance name, usually the NetBIOS name for a default instance and the NetBIOS name plus the instance name for a named instance. If the login mapping does not exist or if the name of the server specified in the connection string does not match the exact name in the sysremotelogins table, and the guest account does not have a mapping in sysremotelogins, you will receive this error. You will also see this error if the remote user is found to have a null or empty login name.

Special Considerations for Replication

Replication uses remote server definitions to connect to the Distributor, Publisher, and Subscriber. At the time you enable and configure replication, you implicitly create remote servers and add login mappings for those remote SQL Server instances. Replication connection strings will always specify the NetBios name for a default instance and the NetBIOS name plus the instance name for a named instance. Therefore replication will not find or use remote server names that were defined for IP addresses or for fully qualified domain names. When the replication connection attempt cannot find the NetBIOS name in sysremotelogins, you will receive the above error.

Microsoft SQL Server replication is supported when the servers involved are registered by NetBIOS (network) name, but not when the servers involved are registered by IP address or fully qualified domain name. For more information about how to replicate between computers running SQL Server in non-trusted domains or across the internet, see Microsoft Knowledge Base article 321822.

Note Support for remote servers is provided for backward compatibility only. New applications that must execute stored procedures against remote instances of SQL Server should use linked servers instead.

   
User Action
If any of the servers involved in the query or used in replication have ever been renamed or were created from an image, you must ensure that the NetBIOS (network) name matches the machine portion of SQL Server’s @@SERVERNAME. If they do not match, you can follow the steps in the Books Online (Updated – SP3) topic, “Renaming a Server,” to update the value of @@SERVERNAME. This change does require that you restart the SQL Server instance. For more information about why replication setup is not successful when SQL Server 2000 is deployed by using a disk image, see Microsoft Knowledge Base article 818334.

If this error occurs during replication, verify that you configured the Distributor, Publisher, and Subscriber using the NetBIOS (network) name, not the IP address or fully qualified domain name.

Related:

Enlist of MSDTC transaction failed: %hs.

Details
Product: SQL Server
Event ID: 8510
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Enlist of MSDTC transaction failed: %hs.
   
Explanation
This message occurs when an attempt is made to enlist a new or existing Microsoft Distributed Transaction Coordinator (MS DTC) transaction and that attempt fails.

The cause of the failure to enlist varies. The state of the error, the specific result code returned with the error, as well as any other errors that occurred around the same time can help to determine why the enlistment failed in your environment. The failure to enlist is often a sign of a communications problem such as failed name resolution. It can also be the result of the way the calling application is coded or a result of blocking or performance issues on the SQL Server side.

Under certain very specific conditions, when a second server process ID (SPID) attempts a new enlistment or makes a call to the sp_reset_connection stored procedure while the Microsoft Distributed Transaction Coordinator (MS DTC) transaction is being successfully interrupted or committed, the second SPID encounters a changing MS DTC transaction and generates the 8510 error message. The 8510 error message is considered unnecessary in these circumstances because the state of the transaction is already resolved before the error message occurs. For more information about this particular set of circumstances, see Microsoft Knowledge Base article 307802.

   
User Action
  • Check that the MS DTC is started on both machines involved in the MS DTC transaction. If the MS DTC service is clustered, verify that it is online in Cluster Administrator.
  • Review the event logs for the servers involved in the MS DTC transaction to see if there are other errors at the same time as this message. If there are other errors, troubleshoot them first, because this error is often a side effect of other errors.
  • By default, network MS DTC access is disabled on Windows Server 2003. If any computer involved is running Windows 2003, verify that MS DTC has been enabled. For more information about how to enable network MS DTC access in Windows 2003, see Microsoft Knowledge Base article 817064.
  • Verify that RPC communications between the servers involved is working correctly.
  • Reboot the servers involved in the MS DTC transaction to flush all IP address information.
  • Verify that the transaction timeout settings for the calling COM+ component are long enough to avoid a timeout that results in a separate component trying to enlist in a transaction that has already timed out.
  • If you have turned on the SQL Server configuration option “lightweight pooling” (also known as “fiber mode”) turn it back off. Test whether the error still occurs.
  • If you have turned on the SQL Server configuration option “priority boost,” turn it back off. Test whether the error still occurs.
  • Review the Microsoft Knowledge Base article 307802 to see if your environment is an exact match for the environment in the article. If it is an exact match, test changing one of the environmental factors to see if the message stops occurring. If it stops once the environment no longer matches the article, you know the message can be safely ignored.

Related:

Self-update is not working.

Details
Product: .NET Framework
Event ID: 13042
Source: Windows Server Update Services
Version: 2.0.50727
Symbolic Name: HealthClientsSelfUpdateRed
Message: Self-update is not working.
   
Explanation
WSUS uses IIS to install the WSUS-compatible Automatic Updates (WSUS client) on most computers. This process is called client self-update. The WSUS setup process creates a virtual directory under the WSUS Web site named Selfupdate, which holds the WSUS-compatible Automatic Updates files. This virtual directory is called the self-update tree.
   
User Action
Self Update

Client self-update is not working correctly. WSUS creates a virtual
directory “SelfUpdate” on port 80 that is used by Automatic Update (AU)
clients. The AU client checks its version, and if the version is found to be out of date, the AU client downloads and installs a new version. This requires downloading a file used to check the version and then downloading the client binaries appropriate for that computer and OS.  The static content in this directory and its subdirectories is available via anonymous access.  Note:
A second SelfUpdate virtual directory will be created if the “WSUS Administration”
Web site is created on port 8530.

Possible resolutions include:

  • Check network connectivity on the WSUS client computer.
    1. Open Internet Explorer.
    2. In the address bar, type http://<WSUSServerName>/iuident.cab where <WSUSServerName> is the name of your WSUS server. Ensure that you are prompted to download or open iuident.cab. This verifies network connectivity from the WSUS client computer and the availability of the iuident.cab file on the WSUS server.
    3. If there are any boxes prompting you to download or save, click Cancel.
  • Check for the existence of the self-update tree on port 80, which is typically the default Web site.
    1. Open a command window.
    2. Type cscript <WSUSInstallDir>\setup\InstallSelfupdateOnPort80.vbs
  • Check permissions on the client Web service directory.
    1. Open a command window.
    2. Type cd <WSUSInstallDir>\SelfUpdate
    3. Type cacls
    4. The following ACEs should be set:
      • BUILTIN\Users:(OI)(CI)R
      • BUILTIN\Administrators:(OI)(CI)F
      • NT AUTHORITY\SYSTEM:(OI)(CI)F
  • Check the IIS configuration of the reporting Web service using the IIS script adsutil.vbs (or use the IIS Administration UI Tool). For more information, see “Appendix C: IIS Settings for Web Services” in the WSUS 3.0 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=81072
  • If ServerBindings or SecureBindings contains entries of the form X.X.X.X:80, remove the IP address and leave only the port address, or add another binding to the local machine 127.0.0.1:80. Type the command <InetpubDir>\AdminScripts\adsutil.vbs set W3SVC/1/ServerBindings “127.0.0.1:80”

Related:

Mailing List parsing complete: {value} lists.

Details
Product: Exchange
Event ID: 80
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_DIRSYNC_PARSE_ML
Message: Mailing List parsing complete: {value} lists.
   
User Action
No user action is required.

Related: