XADM: IS Shuts Down with JET Reporting Out of Disk Space Due to SFM

This article was previously published under Q196217
This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
The Microsoft Exchange Server information store shuts itself down when theJet database engine (EDB) reports that the hard disk drive containing thetransaction logs is full. This problem may also occur when there is sufficient diskspace available but the transaction logs are contained within a Servicesfor Macintosh (SFM) volume.

The following sequence of events will appear in the Windows NT ApplicationEvent logs prior to the information store shutting down:

   Event ID:    32   Source:      EDB   Type:        Error   Category:    Logging/Recovery   Description: MSExchangeIS ((273) ) Unable to create the log. The drive                may be read-only or out of disk space. Error -1811.				
   Event ID:    1111   Source:      MSExchangeIS   Type:        Error   Category:    General   Description: An error occurred while writing to the database log file.                Attempting to stop the Microsoft Exchange Information                Store.				
   Event ID:    1101   Source:      MSExchangeIS Private   Type:        Error   Category:    Background Cleanup   Description: Error -510 occurred during a background cleanup on message                1-E85.				
   Event ID:    1101   Source:      MSExchangeIS Private   Type:        Error   Category:    Background Cleanup   Description: Error -510 occurred during a background cleanup on message                1-E8C.				
   Event ID:    1025   Source:      MSExchangeIS Private   Type:        Warning   Category:    Transport General   Description: An error occurred. Function name or description of problem:                EcDoDeliverMessage Error: -510				
   Event ID:    1101   Source:      MSExchangeIS Private   Type:        Error   Category:    Background Cleanup   Description: Error -510 occurred during a background cleanup on message                1-E93.				
   Event ID:    5004   Source:      MSExchangeSA   Type:        Error   Category:    General   Description: Generation of the offline Address Book is complete. Result:                The Microsoft Exchange Server computer is not available.                Either there are network problems or the Microsoft Exchange                Server computer is down for maintenance. Microsoft Exchange                Server Information Store ID no: 8004011d-0525-00000000.				
After the information store has shut itself down, the administrator canrestart the information store provided there is sufficient disk space available.
Cause
This problem may occur when SFM has been installed onthe Exchange Server computer and the Jet transaction logs (DSADATA and MDBDATA)reside on a Macintosh volume. After the information store has shut itselfdown after the error has occurred, a zero byte Edbtmp.log or a zero byteEdb.log file will be left in the MDBDATA directory. This error conditionarises when the Edb.log file is full and needs to be rolled over to thenext generation log file number. A zero byte Edbtmp.log file is created byJet and is extended to a file size of 5 MB. Edb.log is then renamedto the next numbered log file (for example, Edb000xx.log). Edbtmp.log isthen renamed to Edb.log and then jet continues processing new incomingmessages.

The problem occurs in the transition of renaming these files when SFM is involved. With SFM, there are essentially two file indexesthat need to be kept: NTFS and Apple Fileshare Protocol (AFP). A timingcondition can arise where the AFP update occurs after the file has alreadybeen renamed and thus no longer exists under the old name in NTFS. If so,SFM will create a new zero byte file, which causes an error condition thatreports back to Jet that "The file already exists." This error iseventually interpreted by Jet as being an out of disk space condition andthe information store then shuts itself down to maintain the databaseintegrity.
Workaround
This problem can be avoided by not having any Jet transaction logs locatedon a SFM volume.
Resolution
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
  • 152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
Status
Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.
Properties

Article ID: 196217 - Last Review: 02/21/2014 00:30:57 - Revision: 4.0

Microsoft Exchange Server 4.0 Standard Edition, Microsoft Exchange Server 5.0 Standard Edition, Microsoft Exchange Server 5.5 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB196217
Feedback