Unable to initialize value bytes of memory. Reboot the computer. If that does not work, call Microsoft Technical Support. [valuevaluevaluevalue] (16)

Details
Product: Exchange
Event ID: 104
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: Unable to initialize value bytes of memory. Reboot the computer. If that does not work, call Microsoft Technical Support. [valuevaluevaluevalue] (16)
   
Explanation
The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system.
   
User Action
Use Performance Monitor to determine if a particular item is taking up too much memory. To allocate more memory, close any nonessential applications. You may also increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow.

Related:

() The database page read from the file “” at offset for bytes failed verification due to a page checksum mismatch. The expected checksum was and the actual checksum was . The read operation will fail with error . If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Details
Product: Exchange
Event ID: 474
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The database page read from the file “<file name>” at offset <value> for <number> bytes failed verification due to a page checksum mismatch. The expected checksum was <number> and the actual checksum was <number>. The read operation will fail with error <error code>. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
   
Explanation

ESE Event ID 474 indicates that a database page read failed verification due to a page checksum mismatch. This essentially means that the particular database page referenced within the Microsoft Exchange Information Store service file named (such as priv1.edb) is corrupt. Possible symptoms are as follows:

  • Users cannot send or receive e-mail messages.
  • You cannot start Microsoft Outlook on your client computer.
  • Online backups fail to complete with a -1018 checksum error.
  • Online defragmentation reports a -1018 checksum mismatch error.

This error is typically the result of a hardware malfunction. The associated checksum mismatch -1018 error indicates some type of hardware error 99% of the time.

   
User Action

After a system administrator encounters a -1018 error, if the administrator runs diagnostic hardware tests against the server and these tests report no issues, the administrator might conclude that Exchange must be responsible for the issue because the hardware passed the initial analysis. However, in case after case, further investigation by Microsoft or hardware vendors uncovered subtle issues in hardware, firmware, or device drivers that are actually responsible for damaging the database file.

Ordinary diagnostic tests might not detect all of the transient faults for several reasons. Issues in firmware or driver software might fall outside the capabilities of diagnostic programs. Diagnostic tests might be unable to adequately simulate long run times or complex loads. Also, the addition of diagnostic monitoring or debug logging might change the system enough to prevent the issue from appearing again.

The first step is to use one of the three methods below to move the existing datbases to new hardware:

  • Obtain new hardware and install a second server in the Adminstrative Group and use Move Mailbox to move the mailboxes to the new server.
  • ExMerge the mailboxes out to .pst files and then ExMerge in to a new machine with the same name.
  • If there is no backup and Move Mailbox is not an option, the last resort will be to repair the database using Eseutil /P and Isinteg -fix. You will still need to ExMerge out all the data after the repair and ExMerge back into new hardware.

The second step is to diagnose and correct the original hardware problem by checking the system log, and running extensive tests from the hardware manufacturer on the hardware, firmware, raid controllers, and device drivers. Then you can use Move Mailbox to move the users back, or restore from online back to the repaired machine.

Definitely do not simply repair the existing database or restore from online backup until the hardware errors have been diagnosed and corrected. You must diagnose and correct the hardware errors before repairing, restoring, moving your mailboxes back, or ExMerging your data back or the ESE Event ID 474s and -1018 errors will come back because the root cause has not been fixed.

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:

The driver has detected that device %1 has old or out-of-date firmware. Reduced performance may result.

Details
Product: Windows Operating System
Event ID: 26
Source: Various
Version: 5.0
Component: System Event Log
Message: The driver has detected that device %1 has old or out-of-date firmware. Reduced performance may result.
   
Explanation

The device and driver could run at a faster rate if upgraded firmware were provided.

   
User Action

There is no user action. However, you might want to contact the hardware manufacturer for an upgrade to the firmware for this device.

Related:

%2: ACPI BIOS is attempting to write to an illegal IO port address (%3), which lies in the %4 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

Details
Product: Windows Operating System
Event ID: 5
Source: Acpi
Version: 5.2
Symbolic Name: ACPI_ERR_AMLI_ILLEGAL_IO_WRITE_FATAL
Message: %2: ACPI BIOS is attempting to write to an illegal IO port address (%3), which lies in the %4 protected
address range. This could lead to system instability. Please contact your system vendor for technical assistance.
   
Explanation

The system BIOS attempted to incorrectly access hardware resources concurrently with the operating system. This type of access cannot be synchronized and can cause system instability.

   
User Action

Contact the system vendor for an updated BIOS and follow the vendor’s instructions for installation.

Related:

%2: ACPI BIOS is attempting to write to an illegal PCI Operation Region (%3), Please contact your system vendor for technical assistance.

Details
Product: Windows Operating System
Event ID: 10
Source: Acpi
Version: 5.2
Symbolic Name: ACPI_ERR_ILLEGAL_PCIOPREGION_WRITE
Message: %2: ACPI BIOS is attempting to write to an illegal PCI Operation Region (%3), Please contact
your system vendor for technical assistance.
   
Explanation

The Advanced Configuration and Power Interface (ACPI) basic input output system (BIOS) software routines test hardware at startup and start the operating system. These routines incorrectly attempted to access hardware resources and the operating system at the same time. This type of access cannot be synchronized and could cause system instability.

This error is usually caused by an obsolete BIOS.

   
User Action

Contact the computer vendor for an updated BIOS and install it according to the vendor’s instructions.

Related:

Unable to get device object pointer for port object.

Details
Product: Windows Operating System
Event ID: 2
Source: parvdm
Version: 5.0
Symbolic Name: PAR_CANT_FIND_PORT_DRIVER
Message: Unable to get device object pointer for port object.
   
Explanation

ParVdm depends on previous naming conventions for identifying parallel ports, and in this case it cannot find a port with a name that matches.

Port names can be changed by the user or in response to basic input/output system (BIOS) settings.

   
User Action

No user action is required.

Related:

%1: The embedded controller (EC) hardware didn’t respond within the timeout period. This may indicate an error in the EC hardware or firmware, or possibly a poorly designed BIOS which accesses the EC in an unsafe manner. The EC driver will retry the failed transaction if possible.

Details
Product: Windows Operating System
Event ID: 1
Source: ACPIEC
Version: 5.2
Symbolic Name: ACPIEC_ERR_WATCHDOG
Message: %1: The embedded controller (EC) hardware didn’t respond within the timeout period. This may indicate an error in the EC hardware or firmware, or possibly a poorly designed BIOS which accesses the EC in an unsafe manner. The EC driver will retry the failed transaction if possible.
   
Explanation

The embedded controller (EC) hardware did not respond within the time limit. The EC driver will retry the failed transaction. If the EC continues to fail, the operating system might stop responding, or “hang.”

Possible causes include:

  • An error in the EC hardware or firmware.
  • A poorly designed basic input output system (BIOS) that accesses the EC incorrectly.
   
User Action

Contact the computer vendor for an updated BIOS and install it according to the vendor’s instructions.

If the problem is not with the BIOS, contact the computer vendor for help with the possible EC hardware or firmware failure.

Related: