WMI ADAP failed to connect to namespace %1 with the following error: %2

Details
Product: Windows Operating System
Event ID: 43
Source: WinMgmt
Version: 5.0
Symbolic Name: WBEM_MC_ADAP_CONNECTION_FAILURE
Message: WMI ADAP failed to connect to namespace %1 with the following error: %2
   
Explanation

The Windows Management Instrumentation (WMI) could not connect to the specified namespace. The default system locale was probably changed from the default for the product language to another locale.

WMI tries to connect to a namespace based on the code page of the system default locale. However, only the namespace for the language supported by the default installation of Windows is installed on the computer.

   
User Action

To correct the problem, see article 268881 in the Microsoft Knowledge Base.

Related:

The pipe has been ended.

Details
Product: Windows Operating System
Event ID: 109
Source: Kernel
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_BROKEN_PIPE
Message: The pipe has been ended.
   
Explanation

The using process has closed the pipe or, if you are trying to write to the pipe, there are no available readers.

   
User Action

End your requested operation. If this occurs often while running an application, contact the supplier of that application.

Related:

Error while redoing logged operation in database ‘%.*ls’. Error at log record ID %S_LSN.

Details
Product: SQL Server
Event ID: 3313
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Error while redoing logged operation in database ‘%.*ls’. Error at log record ID %S_LSN.
   
Explanation
The recovery process could not redo (roll forward) one or more transactions in the specified database. This error will be accompanied by a more specific error in the SQL Server error log or the event log.
   
User Action
HARDWARE FAILURE

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware-related problems.

If you have persistent data inconsistency problems, try to swap out different hardware components to isolate the problem. Check that your system does not have write caching enabled on the disk controller. If you suspect this to be the problem, contact your hardware vendor.

Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.

RESTORE FROM BACKUP

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

DBCC CHECKDB

If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

Related:

Client Access server “%1”, running Microsoft Exchange version “%2”, is proxying Outlook Web Access traffic to Client Access server “%3”, which runs Exchange version “%4”. To ensure reliable interoperability, the proxying Client Access server needs to be running a newer version of Exchange than the Client Access server it is proxying to. If the proxying Client Access server is running a newer version of Exchange than the Client Access server it is proxying to, the proxying Client Access server needs to have an Outlook Web Access resource folder (for example, “)\ClientAccess\owa\8.0.498.0” that contains all the same versioned resource files as the Client Access server it is proxying to. If you will be running Outlook Web Access proxying with mismatched server versions, you can manually copy this resource folder to the proxying Client Access server.

Details
Product: Exchange
Event ID: 46
Source: MSExchange OWA
Version: 8.0
Symbolic Name: ProxyErrorCASCompatibility
Message: Client Access server “%1”, running Microsoft Exchange version “%2”, is proxying Outlook Web Access traffic to Client Access server “%3”, which runs Exchange version “%4”. To ensure reliable interoperability, the proxying Client Access server needs to be running a newer version of Exchange than the Client Access server it is proxying to. If the proxying Client Access server is running a newer version of Exchange than the Client Access server it is proxying to, the proxying Client Access server needs to have an Outlook Web Access resource folder (for example, “<Exchange Server installation path>)\ClientAccess\owa\8.0.498.0” that contains all the same versioned resource files as the Client Access server it is proxying to. If you will be running Outlook Web Access proxying with mismatched server versions, you can manually copy this resource folder to the proxying Client Access server.
   
Explanation

This Error event indicates that a Microsoft Office Outlook Web Access proxy request failed when it was sent from one computer that is running the Client Access server role to another Client Access server. This error is logged when the version of the Outlook Web Access resources folders on one Client Access server does not match the version on the other Client Access server.

   
User Action

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

  • Make sure that both Client Access servers are running the same version of Microsoft Exchange Server 2007. Both Client Access servers should run the same Exchange 2007 service pack and also have the same software updates applied.

  • If it is required that you run versions of Exchange Server that are not identical on your Client Access servers, follow these steps:

    1. Locate the Outlook Web Access resources folder on the Client Access server that received the proxy request. The default location of the resources folder is C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\<Exchange Version>, where C:\ is the directory to which Exchange was installed.

    2. Copy the Outlook Web Access resources folder to the proxying Client Access server.

    3. Restart Internet Information Services (IIS) by using the command iisreset/noforce.

    Note   The name of the resources folder <Exchange Version> is indicated by the version of the Client Access server referenced in the event description.

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:

Unable to close the adapter “%2”. Appletalk protocol may be in an unstable state on the adapter.

Details
Product: Windows Operating System
Event ID: 42
Source: AppleTalk
Version: 5.0
Component: Services for Macintosh
Symbolic Name: EVENT_ATALK_CLOSEADAPTER
Message: Unable to close the adapter “%2”. Appletalk protocol may be in an unstable state on the adapter.
   
Explanation

The AppleTalk protocol failed to unbind to an adapter. The protocol stack might fail to stop.

   
User Action

Verify that the protocol stack has stopped. If not, restart the computer.

Related:

Failed to start due to failure to set the current working directory. The system error code is {error code}{error code}.

Details
Product: Exchange
Event ID: 42
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_STARTUP_CWD
Message: Failed to start due to failure to set the current working directory. The system error code is {error code}{error code}.
   
Explanation
The working directory, Exchsrvr\Bin, was not set.
   
User Action
Verify that the directory is available and the appropriate access privileges are set. If the problem persists, reinstall the connector.

Related:

NLB Cluster %2 %1: Enabled traffic handling for all port rules. %3 %4

Details
Product: Windows Operating System
Event ID: 42
Source: WLBS
Version: 5.2
Symbolic Name: MSG_INFO_PORT_ENABLED_ALL
Message: NLB Cluster %2 %1: Enabled traffic handling for all port rules. %3 %4
   
Explanation

This event is logged to inform you that, in response to a user-initiated action, this host will handle new load-balanced traffic for all port rules.

   
User Action

No user action is required.

Related:

Failed to initialize the internal configuration object. Ensure that the Microsoft Exchange Connector for Lotus cc:Mail has been configured correctly. Initialization problems could also be due to failure to bind to the Microsoft Active Directory. Ensure that the values for HomeDSA, Organization, OrgUnit, and CommonName are correct in the registry under the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeCCMC\Parameters.

Details
Product: Exchange
Event ID: 41
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_STARTUP_INIT_CONFIG
Message: Failed to initialize the internal configuration object. Ensure that the Microsoft Exchange Connector for Lotus cc:Mail has been configured correctly. Initialization problems could also be due to failure to bind to the Microsoft Active Directory. Ensure that the values for HomeDSA, Organization, OrgUnit, and CommonName are correct in the registry under the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeCCMC\Parameters.
   
User Action
If any configuration changes have been made to Active Directory recently (within the past few hours), you may need to restart Exchange server for the changes to take effect. If the problem persists, reinstall Connector for Lotus cc:Mail. Carefully follow the instructions in the online help for configuring the connector.

Related:

The PrintQueue could not be found on domain %1. It may have been deleted from the Directory. An attempt will be made to republish the PrintQueue. Error: %2

Details
Product: Windows Operating System
Event ID: 41
Source: Print
Version: 5.0
Component: Application Event Log
Symbolic Name: MSG_CANT_CRACK_GUID
Message: The PrintQueue could not be found on domain %1. It may have been deleted from the Directory. An attempt will be made to republish the PrintQueue. Error: %2
   
Explanation

The print spooler that published a printer cannot find the print queue object in Active Directory. This is usually because the published printer was deleted by other means. For example, an administrator could have deleted the print queue object directly using MMC on the Directory Controller.

   
User Action

No user action is required.

To stop logging this warning event

  1. In Control Panel, open Printers.
  2. On the File menu, click Server Properties.
  3. On the Advanced tab, clear the Log spooler warning events check box.

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: