Get rid of Event id 482 occurs while reading or writing data to/from EDB file

At times, you are unable to write data to Microsoft Exchange Server database and you are also not allowed to access the database files. All these problems may occur due to low exchange disk space or when the edb file gets corrupt. In this situation, you may also get errors in Application Event Log of Exchange server such as Event id 482 while making an attempt to read or write data to/from EDB file.

Assume a situation practically where you are trying to start Information Store service of Exchange 2003 server, but you fail to do so and the following error is seen in Application event log:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 482
User: N/A
Information Store (4360) First Storage Group: An attempt to write to the file "D:\Program Files\Exchsrvr\mdbdata\res2.log" at offset 4194304 (0x0000000000400000) for 1048576 (0x00100000) bytes failed after 0 seconds with system error 112 (0x00000070): "There is not enough space on the disk.". The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup.”



There can be two reasons behind Event id 482 which are as follows:

  1. When there is low disk space in exchange disk space. Error 0x00000070 states about ERROR_DISK_FULL and Error 0xfffff8f0 indicate JET_errDiskFull.
  2. Second reason can be Edb file corruption which Exchange server is unable to recognize


  1. In case the low exchange disk space is the problem for event id 482, then you need to remove some useless files from the disk
  2. In other case, if Edb file corruption then you must use Microsoft Exchange Server Edb repair tool to completely resolve up the corruption issues. By making use of highly advanced scanning techniques, scans the entire edb files and repairs as well as recovers all its objects like mails, notes, tasks, contacts, journal, calendar items etc in least amount of time period.