{process name} ({process id}) An attempt to read from the file “{file name}” at offset {value} for {value} bytes failed with system error {error code}: “{error message}”. The read operation will fail with error {error code}. If this error persists then the file may be damaged and may need to be restored from a previous backup.

Details
Product: Exchange
Event ID: 481
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: OSFILE_READ_ERROR_ID
Message: {process name} ({process id}) An attempt to read from the file “{file name}” at offset {value} for {value} bytes failed with system error {error code}: “{error message}”. The read operation will fail with error {error code}. If this error persists then the file may be damaged and may need to be restored from a previous backup.
   
Explanation
An unexpected error was encountered while reading the file specified in the message.
   
User Action
Review the disk and file which you are trying to read. Use the Error.exe utility to resolve system errors. For more information about the error code reference specified in the message, go to www.reskit.com.

Related:

() Unable to write to section 3 while flushing logfile . Error .

Details
Product: Exchange
Event ID: 417
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Unable to write to section 3 while flushing logfile <file name>. Error <error code>.
   
Explanation

This is an unexpected error that usually occurs during runtime and may indicate that the log drive has failed.

   
User Action

Check the system event log for indications of hardware problems. If a media failure has occurred, restore the database.

Related:

{process name} ({process id}) Unable to write to section 2 while flushing logfile {file name}. Error {error code}.

Details
Product: Exchange
Event ID: 416
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: LOG_FLUSH_WRITE_2_ERROR_ID
Message: {process name} ({process id}) Unable to write to section 2 while flushing logfile {file name}. Error {error code}.
   
Explanation
This is an unexpected error that usually occurs during runtime and may indicate that the log drive has failed.
   
User Action
Check the system event log for indications of hardware problems. If a media failure has occurred, restore the database.

Related:

() Unable to write to section 2 while flushing logfile . Error .

Details
Product: Exchange
Event ID: 416
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Unable to write to section 2 while flushing logfile <file name>. Error <error code>.
   
Explanation

This is an unexpected error that usually occurs during runtime and may indicate that the log drive has failed.

   
User Action

Check the system event log for indications of hardware problems. If a media failure has occurred, restore the database.

Related:

process name (process id) file nameUnable to write to section 2 while flushing logfile error code. Error %5.

Details
Product: Exchange
Event ID: 416
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) file nameUnable to write to section 2 while flushing logfile error code. Error %5.
   
Explanation
This is an unexpected error that usually occurs during runtime and may indicate that the log drive has failed.
   
User Action
Check the system event log for indications of hardware problems. If a media failure has occurred, restore the database.

Related:

process name (process id) file nameUnable to write to section 1 while flushing logfile error code. Error %5.

Details
Product: Exchange
Event ID: 415
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) file nameUnable to write to section 1 while flushing logfile error code. Error %5.
   
Explanation
This is an unexpected error that usually occurs during runtime and may indicate that the log drive has failed.
   
User Action
Check the system event log for indications of hardware problems. If a media failure has occurred, restore the database.

Related:

{process name} ({process id}) Unable to write to section 1 while flushing logfile {file name}. Error {error code}.

Details
Product: Exchange
Event ID: 415
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: LOG_FLUSH_WRITE_1_ERROR_ID
Message: {process name} ({process id}) Unable to write to section 1 while flushing logfile {file name}. Error {error code}.
   
Explanation
This is an unexpected error that usually occurs during runtime and may indicate that the log drive has failed.
   
User Action
Check the system event log for indications of hardware problems. If a media failure has occurred, restore the database.

Related:

{process name} ({process id}) Unable to write to section 0 while flushing logfile {file name}. Error {error code}.

Details
Product: Exchange
Event ID: 414
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: LOG_FLUSH_WRITE_0_ERROR_ID
Message: {process name} ({process id}) Unable to write to section 0 while flushing logfile {file name}. Error {error code}.
   
Explanation
This is an unexpected error that usually occurs during runtime and may indicate that the log drive has failed.
   
User Action
Check the system event log for indications of hardware problems. If a media failure has occurred, restore the database.

Related:

() An attempt to read from the file “” at offset for bytes failed after seconds with system error : “”. The read operation will fail with error . If this error persists then the file may be damaged and may need to be restored from a previous backup.

Details
Product: Exchange
Event ID: 481
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>An attempt to read from the file “<file name>” at offset <value> for <number> bytes failed after <number> seconds with system error <error code>: “<error message>“. The read operation will fail with error <error code>. If this error persists then the file may be damaged and may need to be restored from a previous backup.
   
Explanation

An unexpected error occurred while reading the file specified in the message.

You will receive the following message in the Description of Event ID 481: An attempt to read from the file [database file name such as priv1.edb or priv1.stm] failed.

NOTE: An Event ID 481 refers to a failed read attempt from the database. For comparison, an Event ID 482 refers to a failed write operation to a log file or a database.

The cause depends on the error number in the Description of the Event. The most common error codes for Event 481 are as follows:

  • Error -1022 = 0xfffffc02 = 4294966274 = JET_errDiskIO = Disk IO error. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. The controller software or firmware may be out of date. Check the system log for I/O or drive errors near the time of the 481 Event. This issue may occur because the path for the check file (such as E00.chk) is not correct, which could be caused by a drive failure.
  • Error -1811 = 0xfffff8ed = JET_errFileNotFound = File not found. The database may actually be missing or there may be other causes for this error. Another reason for Error -1811 could be that the Exchange Database and log files may have been put on Network Storage, which is not supported. Also, the checkpoint file may be corrupted, or the log drive itself may have failed. Exchange will dismount the storage group due to an inability to locate the database files. Typically this is due to a hardware problem.
  • Error -1011 = 0xfffffc0d = JET_errOutOfMemory = Out of Memory. Basically, this error indicates that there is no more available memory and the read operation has failed. Other Jet Event IDs with out-of-memory errors in the Description section for reading the header of a database, recovery/restore, and starting a storage group are often seen in the application log at the same time. Review these events for further information.
  • Error -1003 = 0xfffffc15 = JET_errInvalidParameter = Invalid API parameter. This error generally means that the file size of the database is not a multiple of 4,096 bytes.
   
User Action

Review the disk and file that you are trying to read. Check the integrity of the file system. Check the memory usage. Check the system portion of the event log for related entries. Review and change the access permissions properties, and then note the disk space available. Check the file size of the database in bytes.

  • For Error -1022, check to make sure the drive for the Exchange database files is accessible and that the path for the files is specified correctly. If it is, run “chkdsk /f /r” (without the quotation marks). If chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure. Make sure that SYSTEM has full control of Exchsrvr and all subfolders on each partition that contain Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server. Check the system log for I/O or drive errors near the time of the 413 Event.
  • For Error -1811, make sure the antivirus software is not running against the Exchange database, the SRS database directories, or drive M: of Exchange. Ensure that the database drive has not run out of space. Ensure that the database file is actually where it is supposed to be.
  • For Error -1011, check the memory usage of the server. Check the settings for the page file. Check for memory-related events in the application and system logs and check the Microsoft Knowledge Base for troubleshooting of the events found.

  • For Error -1003, check the size of the database in bytes. It must be a multiple of 4,096 bytes, or 1 page. If it is not, contact Microsoft Product Support Services.

Related:

{process name} ({process id}) Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error {error code}.

Details
Product: Exchange
Event ID: 413
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: NEW_LOG_ERROR_ID
Message: {process name} ({process id}) Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error {error code}.
   
User Action
Check the integrity of the file system. Check the system portion of the event log for related entries. Review and change the access permissions properties, and then note the disk space available.Review the disk and log file you are trying to write to. Use the Error.exe utility to resolve system errors. For more information about the error code reference specified in the message, go to www.reskit.com.

Related: