I am getting an error and from what I have read this is bad. In Exchange, running eseutil /MS to get the freespace.txt file dump, we get the following error- Operation terminated with the following error -1022 (Jet_errDiskIO, Disk IO error) after xx seconds. Any suggestions on what we need to do to fix this? We are running Exchange Server 2003 standard and Windows Server 2003 standard. Thanks in advance for any help you can give!

hi,hom much free space is there on your disk that you are running eseutil? Eseutil.exe can be used to defragment, repair, or check the integrity of a Microsoft Exchange Server database. The amount of free disk space needed to defragment a database (Eseutil /d) is 110 percent of the size of the file being defragmented. When you repair a database (Eseutil /p), the amount of free disk space required depends on the number of corrupt pages in the database. This is different from how the older Edbutil.exe program repaired databases. Normally, 25 percent of the file being repaired is a conservative estimate of the amount of free disk space required. Checking database integrity (Eseutil /g) is an in-place operation and does not require any additional free disk space. In the case of the defrag or repair operations, the /t command line switch should be used to specify the location of a temporary file. This file should be located on a drive that has the required free disk space. This can be a local or a network drive. Reference : http://support.microsoft.com/default.aspx/kb/183888regards,Mumin CICEK | Exchange - MVP | www.cozumpark.com | www.mumincicek.com

Hi Please make sure that your database is not suffering from the Disk issues. also check the application and system log to make sure that nothing error relaed to storage is loggedVinod

Interesting, just generating space tree dump you are getting this error... ~ Do you get any error about disk related issues in event log? You may need to run hardware diagnostics to find the health of drives. ~ If you don't see any error in event log or in diagnostics, I would check File Level Antivirus scanning to verify proper exclusion set. I doubt that antivirus scanning would be using edb/stm file when you run Eseutil /MS. Overview of Exchange Server 2003 and antivirus software http://support.microsoft.com/kb/823166 How to Properly Configure File System Antivirus Software on Exchange Server http://www.msexchange.org/articles/Properly-Configure-file-system-antivirus-Exchange.html Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Thanks for all of the advice. We will dive into the suggestions and let you know the results. Thanks again!

Just a couple of additional things in reference to the responses. We are not getting any disk related error messages in the server logs. We are not trying to defrag the exchange database at this time. Running eseutil /MS is supposed to output a text file dump (freespace.txt) to let you know how much space you could save by doing a defrag. Before running the command, I disabled all Endpoint and Mail Security services, dismounted the store and stopped all exchange services. It still gave me the error.

Having a -1022 error is really bad. http://support.microsoft.com/kb/314917Any errors in the Application log?lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Hi, Please use Eseutil /mh to see if the database is in a dirty shutdown status. If so, the error -1022 can occur when running eseutil /ms. In that situation, you may need to restore the database with the backup or do a database repair (Eseutil /p). Eseutil http://technet.microsoft.com/en-us/library/aa998249.aspx Thanks, Elvis

Elvis thanks for the suggestion. We ran the eseutil /mh and it says we are in the clean shutdown status.

We ran the Eseutil /mh and we got the following results: <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0pt; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> Microsoft(R) Exchange Server Database Utilities Version 6.5 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Database: d:\exchsrvr\mdbdata\priv1.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdef Format ulVersion: 0x620,11 Engine ulVersion: 0x620,11 Created ulVersion: 0x620,9 DB Signature: Create time:03/15/2008 13:25:53 Rand:84330 Computer: cbDbPage: 4096 dbtime: 974552323 (0x3a167d03) State: Clean Shutdown Log Required: 0-0 (0x0-0x0) Streaming File: Yes Shadowed: Yes Last Objid: 174808 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 0 Repair Date: 00/00/1900 00:00:00 Old Repair Count: 0 Last Consistent: (0xFB83,20C4,28) 06/17/2009 21:08:54 Last Attach: (0xFA40,397,183) 06/17/2009 09:59:41 Last Detach: (0xFB83,20C4,28) 06/17/2009 21:08:54 Dbid: 1 Log Signature: Create time:03/15/2008 13:25:52 Rand:106593 Computer: OS Version: (5.2.3790 SP 2) Previous Full Backup: Log Gen: 64377-64382 (0xfb79-0xfb7e) Mark: (0xFB7B,18D4,1D4) Mark: 06/17/2009 19:00:04 Previous Incremental Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Current Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Current Shadow copy backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 cpgUpgrade55Format: 0 cpgUpgradeFreePages: 0 cpgUpgradeSpaceMapPages: 0 ECC Fix Success Count: none Old ECC Fix Success Count: none ECC Fix Error Count: none Old ECC Fix Error Count: none Bad Checksum Error Count: none Old bad Checksum Error Count: none Operation completed successfully in 3.31 seconds.

If it's in clean shutdown mode but we get the same error where do you think we should look next?

If you start everything again and try to do a full online backup. Does it work and purge transaction log files? if not whats the error in application log?lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

We do a full backup daily with NTBackup, backing up the Exchange Store. The transaction log files are purged when the daily backup is performed. There are no error messages in the application log referring to the backup.

make sure that you're using the correct version of eseutl.compare file versions with ese.dll and store.exelasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

On the D: drive where exchange is installed the Store.exe (d:exchsrver\bin) is version 6.5.7654.12. The ese.dll (d:exchsrver\bin) is version 6.5.7638.2. There is also an ese.dll in c:program files\microsoft integration\microsoft exchange. This one is version 6.5.6994.0. Thanks again for your help.

CoveWolf,In this scenario when disk space is not a problem, I would start backing up the databases as soon as possible and create another store to move all mailboxes on this store. Just to be on safer side I would perfer to use an independant disk for the new store and wont mount them on the same disk where the old database is. As an alternate Iwill also think of getting some help from older backups. Retore the latest online backupyou have to see if that helps.If this fails then probably I will go with hard repairs (eseutil /p ) as suggested by others. The reason is you never know how much of data you will loose after running hard repair. If you are keen about knowing it there is a way to run eseutil /k and wait till it completes. This will let you know how much amount of data will be lost on repair.MMilind Naphade | MCTS:M | http://www.msexchangegeek.com

Do you have any AV software running on the server, try to disable it while running eseutil.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

The -1022 error is pretty nasty, if I remember correctly. As bad or worse than the -1018 error. Take a look at this KB:http://support.microsoft.com/kb/314917Endpoint? As in Symantec Endpoint Security? Putting Symantec Endpoint Security on our servers was one of the biggest security mistakes we made this year. Get rid of it! Even if you disable it, it can still interfere with things at the network layer. On our older servers and workstations, we were seeing an additional 10 - 20ms network latency merely because Endpoint was installed. We had very unpredictable results with respect to SMTP e-mail inbound and outbound. Before you continue, REMOVE Endpoint.My $0.02 worth.Jim McBee - Blog - http://mostlyexchange.blogspot.com