{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:

The DNS server will send requests to other DNS servers on a port other than its default port (TCP port 53). This is done to accommodate configuration changes you have made at the DNS server and prevent it from failing to receive DNS queries it makes to other servers. You might want to change this behavior. For more information, see “DNS server log reference” in the online Help. This DNS server is multi-homed (running on multiple IP addresses), but has been configured NOT to run on ALL IP addresses available on the machine. Under these conditions it is impossible to guarantee that a DNS query to a remote DNS server will be sent with one the IP addresses the DNS server is using, and hence, whether the response to that IP address, will be received on the DNS port. To avoid this problem, sends to other DNS servers will be done on a arbitrary (non-DNS) port, and the response will be received regardless of the IP address used. If you wish to use the DNS port for sends to other DNS servers, then you must change your configuration to either: 1) use all IP addresses on the machine for DNS (i.e. eliminate the listen address list) or 2) limit the DNS server to use a single IP address.

Details
Product: Windows Operating System
Event ID: 413
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_NON_DNS_PORT
Message: The DNS server will send requests to other DNS servers on a port other than its default port (TCP port 53). This is done to accommodate configuration changes you have made at the DNS server and prevent it from failing to receive DNS queries it makes to other servers. You might want to change this behavior. For more information, see “DNS server log reference” in the online Help. This DNS server is multi-homed (running on multiple IP addresses), but has been configured NOT to run on ALL IP addresses available on the machine. Under these conditions it is impossible to guarantee that a DNS query to a remote DNS server will be sent with one the IP addresses the DNS server is using, and hence, whether the response to that IP address, will be received on the DNS port. To avoid this problem, sends to other DNS servers will be done on a arbitrary (non-DNS) port, and the response will be received regardless of the IP address used. If you wish to use the DNS port for sends to other DNS servers, then you must change your configuration to either: 1) use all IP addresses on the machine for DNS (i.e. eliminate the listen address list) or 2) limit the DNS server to use a single IP address.
   
User Action

To verify and reset the IP addresses on which the DNS server should listen:

1. In DNS Manager, right-click the DNS server in the server list.
2. Click Properties.
3. On the Interface tab, use Add and Remove to edit the list of IP addresses. Use Move Up and Move Down to prioritize the list of IP addresses.
4. When you are finished, click OK.

Related:

process name (process id) error codeUnable 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 %4.

Details
Product: Exchange
Event ID: 413
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) error codeUnable 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 %4.
   
Explanation
A new log file could not be created because the database cannot write to the log file drive.

The drive may be read-only, out of disk space, misconfigured, or corrupted. 

The cause depends on the Error number in the Description section of the Event. 

The most common error codes for Event 413 are listed below.

  • Error -1032 =  0xfffffbf8 =  4294966264 = JET_errFileAccessDenied = Cannot

    access file – the file is locked or in use. Another process has “stolen” the

    file. A virus checker may mistakenly quarantine a file, or a backup process

    may temporarily deny access.  A flat file backup system or anti-virus

    software may be running against the information store, the SRS database file

    directories, or the M: drive.  This error can also occur if the permissions on

    the folder that contain the files for the information stores or the SRS are

    not sufficient for the databases to function properly.  The hardware

    device drivers may be out of date.

  • Error -1811 = 0xfffff8ed = JET_errFileNotFound = File not found. The

    log file may actually be missing or there may be other causes for this error. 

    For example, the current logfile (e.g., E00.log) may have a mismatching

    signature between the log and the database. Another reason for Error -1811

    is that the Exchange database and log files may have been put on Network
    Storage, which is not supported. Also, the checkpoint file may be corrupt, or

    the log drive itself may have failed.  The current log file may have been

    seized and deleted by anti-virus software running on the server. There have

    also been problems seen creating the temp log file for the storage group

    (e.g., e00tmp.log ).  The temp log file itself may become corrupt.

  • 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 413 Event. This issue may occur because the path for the check

    file (such as E00.chk) is not correct, which may be caused by a drive failure.

   
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.

  • For Error -1811, make sure the anti-virus software is not running against

    the Information Store, the SRS database directories, or the Exchange M: drive. 

    Ensure the log file drive has not run out of space.

  • For Error

    -1032, change the permissions on the folders that contain the information

    store files to the default

    permissions.  Configure the flat file backup and anti-virus software to not scan the Exchange server Information Store subdirectories, or the M: drive. 

    Use Exchange-aware online backup and anti-virus software.

  • For Error -1022,  Ensure the drive for the information store

    files is accessible and that the path for the information store 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. Ensure that SYSTEM has full control of Exchsrvr

    and all subfolders on each partition that contains 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. Check and correct the path for

    the check file (such as E00.chk).

  • After correcting the root cause, if the database is inconsistent, restore

    from online backup. If there is no valid backup, you can restore the database

    to consistency using the “hard repair” (/p) functionality of the Eseutil

    utility, run isinteg -fix until all fixes are removed, and then mount the

    database and then ExMerge to a new, blank database. NOTE: Before doing this,
    you should always back up all information store files in a Storage Group

    (*.log files, *.edb files and *.stm files).

Related:

() 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 .

Details
Product: Exchange
Event ID: 413
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>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>.
   
Explanation

A new log file could not be created because the database cannot write to the log file drive.

The drive may be read-only, out of disk space, misconfigured, or corrupted. The cause depends on the error number in the Description section of the event. The most common error codes for Event 413 are listed below.

  • Error -1032 = 0xfffffbf8 = 4294966264 = JET_errFileAccessDenied = Cannot access file – the file is locked or in use. Another process has “stolen” the file. A virus checker may mistakenly quarantine a file, or a backup process may temporarily deny access. A flat file backup system or antivirus software may be running against the information store, the SRS database file directories, or drive M. This error can also occur if the permissions on the folder that contain the files for the information stores or the SRS are not sufficient for the databases to function properly. The hardware device drivers may be out of date.
  • Error -1811 = 0xfffff8ed = JET_errFileNotFound = File not found. The log file may actually be missing or there may be other causes for this error. For example, the current logfile (e.g., E00.log) may have a mismatching signature between the log and the database. Another reason for Error -1811 is that the Exchange database and log files may have been put on Network Storage, which is not supported. Also, the checkpoint file may be corrupt, or the log drive itself may have failed. The current log file may have been seized and deleted by antivirus software running on the server. There have also been problems encountered in creating the temp log file for the storage group (e.g., e00tmp.log ). The temp log file itself may become corrupt.
  • 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 413 Event. This issue may occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.
   
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.

  • For Error -1811, ensure that the antivirus software is not running against the Exchange Information Store, the SRS database directories, nor drive M. Ensure the log file drive has not run out of space.
  • For Error -1032, change the permissions on the folders that contain the information store files to the default permissions. Configure the flat file backup and antivirus software to not scan the Exchange server Information Store subdirectories, nor drive M. Use Exchange-aware online backup and antivirus software.
  • For Error -1022, ensure that the drive for the information store files is accessible and that the path for the information store 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. Ensure that SYSTEM has full control of Exchsrvr and all subfolders on each partition that contains 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. Check and correct the path for the check file (such as E00.chk).
  • After correcting the root cause, if the database is inconsistent, restore from online backup. If there is no valid backup, you can restore the database to consistency using the “hard repair” (/p) functionality of the Eseutil utility, run isinteg -fix until all fixes are removed, and then mount the database and then ExMerge to a new, blank database. NOTE: Before doing this, you should always back up all information store files in a storage group (*.log files, *.edb files and *.stm files).

Related:

%1 (%2) %3Unable 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 %4.

Details
Product: Exchange
Event ID: 413
Source: ESE
Version: 08.01.0106.000
Symbolic Name: NEW_LOG_ERROR_ID
Message: %1 (%2) %3Unable 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 %4.
   
Explanation

This Warning event indicates that a new log file could not be created because the database cannot write to the log file drive.

The event may be logged if the drive is read-only, out of disk space, configured incorrectly, or corrupted. The cause depends on the error number in the Description section of the event. The most common error codes for event 413 are listed below.

  • Error -1032 = 0xfffffbf8 = 4294966264 = Jet_errFileAccessDenied = Cannot access file – the file is locked or in use. Another process has locked the file. A virus checker may mistakenly quarantine a file, or a backup process may temporarily deny access.

  • Error -1811 = 0xfffff8ed = Jet_errFileNotFound = File not found. The following are possible causes for this error:

    • The current log file (such as E00.log) may have a mismatching signature between the log and the database.

    • The checkpoint file may be corrupted, or the log drive itself may have failed.

    • The current log file may have been deleted by antivirus software running on the server.

    • There may have been problems creating the temp log file for the storage group (such as e00tmp.log ). For example, the temp log file itself may become corrupted.

  • Error -1022 = 0xfffffc02 = 4294966274 = Jet_errDiskIO = disk I/O error. The -1022 error is a generic error that appears whenever a disk 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. This issue may also occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.

   
User Action

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

  • Check the integrity of the file system.

  • Check the System log for related entries.

  • Review and change the access permissions properties, and then note the disk space available.

  • Review the disk and log file to which you are trying to write.

  • For error -1811, ensure that the antivirus software is not running against the Exchange store, the Site Replication Service (SRS) database directories. Ensure that the log file drive has not run out of space.

  • For error -1032, change the permissions on the folders that contain the information store files to the default permissions. Configure the flat file backup and antivirus software to not scan the Exchange store subdirectories. Use Exchange-aware online backup and antivirus software.

  • For error -1022, ensure that the drive for the Exchange store files is accessible and that the path for the Exchange store files is specified correctly. If it is, run chkdsk /f /r. If the Chkdsk tool does not resolve the issue, examine the permissions on the Exchange Server folder structure. Ensure that System has full control of Exchange Server (install path for Exchange) and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any 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. Check and correct the path for the check file (such as E00.chk).

After correcting the root cause, if the database is inconsistent, restore from online backup. If there is no valid backup, you can restore the database to consistency using the hard repair (/p) functionality of the Eseutil utility. Run isinteg -fix until all fixes are removed. Mount the database and use Move Mailbox to move to a new, blank database. Before doing this, you should always back up all Exchange store files in a storage group (*.log files, *.edb files and *.stm files).

For information about ESE error -1022, see Microsoft Knowledge Base article 314917

Understanding and analyzing -1018, -1019, and -1022 Exchange database errors.

For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

For information about properly configuring your antivirus software, see Microsoft Knowledge Base article 328841 Exchange and antivirus software.

Related: