NS_I_DISK_START (0X400D0054) - Disk SPACE alert on Content Server

1. Disk Space is Low — The Most Common Cause

In my experience, this error pops up when the disk where the Content Server stores document files hits 90% full or so. It's a warning from DocuWare, not a crash. The Content Server keeps working, but you'll see it in the Event Log and maybe in the DocuWare Admin. I had a client last month whose Content Server C: drive was 98% full because the temp folder had 200GB of old log files. The error was there, but the server still ran. The fix is simple: free up space.

How to Fix It

1. Check which disk has the problem. Look at the error message — it says Disk %1. In DocuWare Admin, go to the Content Server's storage locations. Usually it's the drive where the DWDocumentCache folder lives.
2. Open File Explorer on the server and look at the disk's free space. If it's under 10%, that's your problem.
3. Delete temporary files. Run Disk Cleanup (right-click the drive, Properties, Disk Cleanup). Check 'Temporary files' and 'Recycle Bin'. I've seen this free up 30GB sometimes.
4. Check the C:\Windows\Temp and C:\Users\%username%\AppData\Local\Temp folders. Delete anything older than a week.
5. Look for log files from the Content Server itself. The default location is C:\ProgramData\DocuWare\Log. If there's gigabytes of log, zip them up or delete old ones.
6. Check if disk quotas are enabled — I've seen a server where a single user's cache filled the whole disk.

The real fix is to keep at least 20% free space. Set up a scheduled task to run Disk Cleanup weekly. That'll stop the error from coming back.

2. Document Cache is Too Big

The second most common cause I see is the document cache directory on the Content Server getting bloated. When users view or download documents, the server caches them in DWDocumentCache. Over time, this folder can hit hundreds of GBs. I once worked on a server where the cache was 400GB because nobody had cleared it in two years. The error 0X400D0054 was firing every 10 minutes.

How to Fix It

1. Stop the DocuWare Content Server service. You can do this from Services.msc or the server's admin panel.
2. Go to the cache folder. It's usually D:\DocuWare\DWDocumentCache or similar — depends on your setup. Check the DocuWare Admin for the exact path.
3. Delete everything inside the cache folder. Don't delete the folder itself. Just delete the subfolders and files inside. The server will recreate them when it starts.
4. Restart the Content Server service.

This will free up a ton of space fast. The cache will rebuild as users access documents, but it'll stay small for a while. If you want to limit the cache size, you can configure a maximum size in the DocuWare Admin under the Content Server settings. But I've never needed to — just clean it every few months.

3. Content Server Can't Write to Its Database

Sometimes the disk space issue isn't about the file store — it's about the Content Server's own database disk. If the SQL Server or the DocuWareContentServer database is on a small drive, and that drive gets full, the service throws this warning. I helped a client whose SQL Server was on a C: drive with only 5GB free. The Content Server couldn't write its metadata, and the error appeared.

How to Fix It

1. Find out where the Content Server database is stored. Open SQL Server Management Studio, connect to the SQL instance, and look at the properties of the DocuWareContentServer database.
2. Check the free space on that drive. If it's low, shrink the database log file. Right-click the database, Tasks, Shrink, Files. Choose 'Log' and shrink to a reasonable size. I've seen log files grow to 50GB because of full recovery mode — shrinking back to 1GB works fine.
3. If the data file is full, you might need to move the database to a bigger drive. Or add a new data file on a larger drive. This is more advanced — back up the database first.
4. Also check the TempDB. If it's on the same drive and growing, move it off. Use SQL Server's ALTER DATABASE commands.

One client had the TempDB on a C: drive with only 1GB free. Moving it to a D: drive fixed the error immediately.

Quick-Reference Summary Table

If none of these fix it, check the Event Log for other errors that might be hiding. Sometimes the Content Server shows this warning when another service crashed. But 9 times out of 10, it's just space. Don't overthink it.