I had a problem last night with Exchange 2003 SP2. I started getting reports of users not being able to get to their mailboxes. I confirmed that this was a problem. The primary errors that I was getting had to do with ESE as a source and event IDs of 482 and 428. I looked at the services and all were running except MTA, which I started. I decided to reboot to see if that would fix the problem and then deal with the why of it later. After reboot all functionality was returned. Upon taking a closer look it appears that ESE, some other Exchange things as well as a couple of other programs started reporting a lack of disk space... which I find hard to believe. I looked at the available disk space and it looks more than adequate. The Exchange program as well as the Public folders live on C: which shows 61 GB free. The IS itself lives on the E: drive which has 116 GB free. The Public edb and stm files together are about 400 MB and the entire IS is about 35 GB. Any one have any thoughts on this? Thanx...Jon

are you running standard edition for exchange? what is the total size of your private information store? you may have exceeded the 18gb size limit.http://support.microsoft.com/kb/912375

I believe that we are running Exchange Enterprise. Our entire IS is about 35 GB. The biggest single EDB file is 15 GB. I also forgot to mention that although the IS itself lives on the E: drive, it's logging files are on C:.

Where is the LOG drive located? is it on E drive? or someother drive? the event id says that the logs ran out of disk. Please make sure you backup the exchange regularly in order to purge the logs and to avoid any data corruption. You can locate the LOg drive as below Start Exchange System Manager. Locate the Administrative Group Open the properties on the Storage Group for which you want to change log file paths. Click on General Tab Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

The log files are on the C: drive.

The logs for Mailbox store as well as public store both are on C drive??? Please double check Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Yes, all log files are on C:. Should probably also note that this is not a new install, have had this set up for several years and not made any changes to server in recent past.

Post the full event id for 482 and 428 so we can get the ese error code. You may be running into corruption. I would review your event logs going back to see if you have been getting other ese related events. If so your best bet may be to restore from back up.James Chong (MVP) MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

What other apps reported this?

I had a large number of the 482 error which reads as follows: Information Store (3840) First Storage Group: An attempt to write to the file "C:\Program Files\Exchsrvr\mdbdata\res2.log" at offset 3145728 (0x0000000000300000) 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. It seems that I had one of the 428 messages that read: Information Store (3840) First Storage Group: The database engine is rejecting update operations due to low free disk space on the log disk I'veookedbackover my event logs and this seems to be the first time that I have seen this problem. It doesn't seem to have reappeared today.

In the system log I've found entries for sources of OFADriver (backup driver for arcserve), Srv and IIS Config to name a few. I've also been monitoring disk space today and it's holding pretty steady.

This is locally connected storage? Man, my first thought is disk corruption, but you arent getting those errors anymore?

Check the no of logs for database and then run the full backup. and closely monitor the server for these kind of messages Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

To verify if its a enterprise edition a. Launch ESM b. Expand Administrative Groups->AdministrativeGroupsName->Servers c. In the right-pane, locate the Edition column Based on KB 555434 (Event 428) and KB 555423 (Event 482), it looks very like a disk space issue And according to Event 428: This event is usually seen with ESE Event ID 482. Event ID 482 will precede Event ID 428, and indicates a failure to write to a file If the accompanying Event ID 482 indicates a failure to write to disk because of any other error, then this may not be a disk space issue However, per your description, its plenty of space available: C drive: Log files and public store, free space (61GB) D drive: Mailbox Store, free space (116GB) Please verify the health of information store with ISINTEG and ESEUTIL Also, we can check the health of exchange server by using Exchange Server Best Practices Analyzer ~~~~~~~~~~~~~~ James Luo TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com ~~~~~~~~~~~~~~

Appreciate everyones help. I am now on vacation, but I will have another team member check the forum and respond to your queries

OK... I am back from vacation. We have not had any further occurrences of the issue. I did notice that we went from 61 GB of free disk space down to about 25 GB during the time I was gone. I looked at the log files in mdbdata and I just have the one days worth of files. Then I did a search for any files modified in the last week and obviuosly found some, but not enough that would account for that amount of drop in space. I did go to the Windows/system32 log file folder and deleted a bunch of old logs, which got be back about 30 GB of space, but that still doesn't account for what took away the space in the first place. I made sure to search hidden files and folders and found a lot, but most are things that cycle like my backup of the information store and the mdbdata log files and antivirus definitions.

Well, please use the methods in my post above to check the exchange, see if theres any issue in the exchange

I ran the Exchange BPA. It did report some things that I probably need to look at, but nothing that would indicate any serious health problems with the IS or anything that would lead me to believe that something is failing. However, I did notice that once again, my disk space on C: is very low. I took a look around to see what might be causing it since I had a lot of space last Friday. I looked at all of the logs and they are sized appropriately and are what I expect. So, I did a search for new large files and I found that right now, my ArcServe backup process is backing up to tape the backup I do each night of the IS and the system state. Apparently it creates a duplicate temporary file while it is backing up. I am suspecting that over time the IS has grown and since I had not been cleaning out other system log files finally got to the point where it failed and the drive probably did literally did run out of space. Now that the backup is done, I have almost 50 GB of space. I have not wanted to put this on the E: drive since that's where the IS lives and wanted to keep that pristine, but during the night there's not much traffic and in reality it's one big RAID 5 array anyway, so I may move my back up to there.

Great. Glad you found the cause