Fix NS_I_CATATONIC_FAILURE (0x800D0199) Disk Catatonic Error

Quick Fix (30 seconds) — Reset the Catatonic Disk

This error means your Content Server disk got stuck in a "catatonic" state — it's not responding, but it's not dead. The fastest way to bring it back is a soft reset. You don't need to reboot the whole server for this.

1. Open the Enterprise Vault Administration Console on your Content Server.
2. Go to Servers > Your Content Server > Storage Groups.
3. Find the storage group that contains the disk showing error 0x800D0199. The disk name and index number are in the error message (e.g., Disk 1).
4. Right-click that disk and choose Reset State.
5. Click Yes when the confirmation pop-up appears.
6. Wait 10–15 seconds. After reset, the disk status should change from "Catatonic" to "Active" or "Resyncing". If it goes active, you're done. If it stays catatonic or goes to "Failed", move to the moderate fix.

Why this works: The disk got stuck during a normal operation—usually a backup or a heavy archive restore. Resetting tells the Content Server to recheck the disk's heartbeat. Nine times out of ten, it snaps back. This doesn't affect data.

Moderate Fix (5 minutes) — Check Disk Health and Free Up Space

If reset didn't work, the disk is likely full or has physical issues. Let's rule those out before you rebuild anything.

Step 1: Check disk space on the server

1. Open File Explorer on the Content Server machine.
2. Right-click the drive that holds the catatonic disk's storage location (usually the same drive letter where your Enterprise Vault data lives).
3. Click Properties. Look at the free space. If it's below 10% of total capacity, that's your problem.
4. Free up space: delete old log files, move archive data to another drive, or extend the volume if you have room.
5. Once you have at least 15% free space, go back to the EV Admin Console and right-click the catatonic disk again. Choose Reset State.

Step 2: Run CHKDSK on the disk

If space wasn't the issue, the disk might have corruption. Run a read-only check first (no repair) to see what's going on.

chkdsk D: /f

Replace D: with the actual drive letter. Run this in an elevated Command Prompt (right-click Command Prompt, choose Run as Administrator).

After CHKDSK finishes, if it reports bad sectors or file system errors, you need to replace that drive. If it comes back clean, try the reset one more time in the EV console. Still catatonic? Move to the advanced fix.

Advanced Fix (15+ minutes) — Rebuild the Storage Group Disk

You've tried the soft reset and checked disk health. The disk is still catatonic. Time to rebuild it. Don't worry — you won't lose archived data. The data is stored in the SQL database; the disk is just a cache/index location.

Step 1: Delete the catatonic disk from the storage group

1. In the EV Admin Console, navigate to the storage group containing the bad disk.
2. Right-click the catatonic disk and choose Delete. A warning will pop up saying this removes the disk from the group but keeps the physical files.
3. Click Yes. The disk disappears from the list. You'll see a yellow warning in the event log — that's normal.

Step 2: Create a new disk with the same size and location

1. Right-click the same storage group and choose New > Disk.
2. Give it the same name as the old one (e.g., "Disk 1") or something similar like "Disk 1 - NEW".
3. Set the size to the same value as the old disk. If you're not sure, 500 GB is a safe default for most environments.
4. Choose the same physical drive and folder path where the old disk's files resided. The Content Server will reuse the existing directory.
5. Click Finish. The new disk will start in a "Creating" state, then move to "Active".

Step 3: Verify data integrity

Once the new disk is active, run a consistency check on that storage group:

1. In the EV Admin Console, right-click the storage group and choose Tasks > Verify Storage Group.
2. Let it run. This checks that all archive data in SQL matches the files on disk. It can take 30 minutes to an hour depending on size.
3. After it finishes, check the Event Viewer (Application log) for any errors. If you see zero errors, you're golden.

What if none of this works?

If you've done all three steps and the error comes back within a week, you have a hardware problem. Replace the physical drive or the entire storage array. Also check for antivirus exclusions — Enterprise Vault's working directories need to be excluded from real-time scanning. That alone can cause catatonic errors on busy servers.

One last thing: never ignore this error. A catatonic disk won't archive new items. Users will start seeing "archive could not be completed" errors in Outlook or Notes. Fix it before the help desk tickets pile up.