Event ID 59 — ADAP Base Class Availability

Event ID 59 — ADAP Base Class Availability

Updated: December 6, 2007

Applies To: Windows Server 2008

AutoDiscovery/AutoPurge (ADAP) is a process that transfers performance libraries into WMI classes.

Event Details

Product: Windows Operating System
ID: 59
Source: Microsoft-Windows-WMI
Version: 6.0
Symbolic Name: WBEM_MC_ADAP_UNABLE_TO_ADD_WIN32PERFRAWDATA
Message: WMI ADAP was unable to create the Win32_PerfRawData base class %1

Resolve
Manually create abstract WMI performance classes

The abstract WMI performance classes Win32_Perf, Win32_PerfRawData, and Win32_PerfFormatedData are created by the ADAP process. Under low memory or other extreme conditions, it is possible that these classes might not be created.

To resolve this issue, type wmiadap /f at a command prompt. Then type echo %errorlevel% and verify that it is zero (0), which indicates that the wmiadap tool ran correctly.

Verify

To verify that the WMI Performance classes are in the WMI Repository:

  1. Open a command prompt window under administrative credentials and type wbemtest.
  2. Click Connect.
  3. Verify that root\cimv2 appears in the Namespace box and click Connect.
  4. Click Open Class, type Win32_Perf and click OK. If wbemtest does not display an error, then the Win32_Perf class is present in the repository.
  5. Click Close and repeat Step 4 for classes Win32_PerfRawData and Win32_PerfFormattedData.

Related Management Information

ADAP Base Class Availability

Management Infrastructure

Related:

Event ID 59 — Jobs

Event ID 59 — Jobs

Updated: December 13, 2007

Applies To: Windows Server 2008

A BITS job represents one application’s request to transfer a set of files from a server or to a server. A job contains one or more files to transfer, and properties that specify how BITS transfers the files and interacts with an application (such as the priority of the job, the number of files allowed, and the network credentials used to authenticate to a server).

Event Details

Product: Windows Operating System
ID: 59
Source: Microsoft-Windows-Bits-Client
Version: 7.0
Symbolic Name: EVT_START_DOWNLOAD
Message: BITS is starting to transfer “%4” for job “%2”.

Resolve

This is a normal condition. No further action is required.

Related Management Information

Jobs

BITS Infrastructure

Related:

Unable to allocate memory for entity . Reboot the computer. If that does not work, Contact Microsoft Technical Support. [ ] (14)

Details
Product: Exchange
Event ID: 59
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: Unable to allocate memory for entity <object name>. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [<value> <value> <value> <value>] (14)
   
Explanation

The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system.

   
User Action

Free up the memory in use by closing any nonessential applications. Increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow.

Related:

A corrupted calendar configuration was detected for user %1. Microsoft Exchange is resetting the configuration.

Details
Product: Exchange
Event ID: 59
Source: MSExchange OWA
Version: 8.0
Symbolic Name: CorruptCalendarConfiguration
Message: A corrupted calendar configuration was detected for user %1. Microsoft Exchange is resetting the configuration.
   
Explanation

This Error event indicates that the user’s calendar is corrupted or has been infected by a virus.

   
User Action

To resolve this error, 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:

An unexpected network error occurred.

Details
Product: Windows Operating System
Event ID: 59
Source: Kernel
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_UNEXP_NET_ERR
Message: An unexpected network error occurred.
   
Explanation

Your computer received an error from the network that was not expected in this situation.

   
User Action

Retry the operation. If you continue to have problems, contact your network administrator.

Related:

Unable to allocate memory for entity {object name}. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 59
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA00059
Message: Unable to allocate memory for entity {object name}. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14)
   
Explanation
The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system.
   
User Action
Free up the memory in use by closing any nonessential applications. Increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow.

Related:

Unable to allocate memory for entity object name. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [valuevaluevaluevalue] (14)

Details
Product: Exchange
Event ID: 59
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: Unable to allocate memory for entity object name. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [valuevaluevaluevalue] (14)
   
Explanation
The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system.
   
User Action
Free up the memory in use by closing any nonessential applications. Increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow.

Related:

%1 failed for %2. Reference error message: %3.

Details
Product: Windows Operating System
Event ID: 59
Source: SideBySide
Version: 5.2
Symbolic Name: MSG_SXS_FUNCTION_CALL_FAIL
Message: %1 failed for %2. Reference error message: %3.
   
Explanation

A component or manifest could not be activated.

Possible causes include:

  • The component or manifest depends on another program or component that is not installed.
  • The manifest contains XML content that is not valid.
  • The user does not have the correct permissions.
   
User Action

To resolve this problem, do one or all of the following:

  • Review the event logs to see whether any related events are logged.
  • Verify that all dependent components or programs are installed.
  • Review the XML content, and correct any that is not valid.
  • Verify that the user has the correct permissions on the computer.

Related: