• Article

An error occurred when an attempt to write to a file failed because there is not enough space on a disk

 

Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this event, do one or more of the following:

  • Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.

  • Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.

Details

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

482

Event Source

ESE

Alert Type

Critical Error

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine

MOM Rule Name

An error occurred when an attempt to write to a file failed because there is not enough space on a disk. Review the error code for more information.

Explanation

This Error event indicates that an unexpected error was encountered while writing to the file specified in the message.

The most common error associated with event 482 is found in the Description section of the event. It is ESE error -1808, which means that the disk is full. One cause of receiving this error is that the disk may actually be full, and the database or the current transaction log cannot be written to because the disk is full. Another cause for ESE error -1808 is that the file system may be FAT32, which has a limit of 4 GB.

Another error that is found in the Description section of event 482 is ESE error -1022. If Exchange asks the operating system for a page in the database, and an error occurs instead of the page data is returned, then a -1022 error (Jet_errDiskIO) results. 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. The most common reason for a -1022 error is a database file that was severely damaged or truncated.

User Action

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

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

  • If the error is -1808, then check to see if the disk where the database or logs reside is full. If it is, determine the root cause of why the disk filled up. Check the file system and ensure that the file system is not FAT32.

  • If the error is -1022 and the error is caused by database damage in the file system, you need to verify or repair the file system, and then restore Exchange from a backup. Although repairing the database is still an option, repair is less likely to be successful than with the other errors because a -1022 error often signals extensive damage.

  • If the database is undamaged, another application may be holding files open and preventing the Microsoft Exchange Information Store service from accessing them. In such cases, you might also see -1032 errors (Jet_errFileAccessDenied). Restarting all of the Exchange services or restarting the server might remove the lock.

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

For More Information

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.

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.