Corrupted file in Server 2003

Posted on 2011-10-11
Last Modified: 2012-05-12
I have a Server 2003 (used for file sharing) where the domain controller died on me and of course the server shut down improperly.

Now everything I try to go log in, I see an error message of a corrupted file.

The file that is corrupted is the ~$dit.doc file, and I do not need it but I cannot delete it.

Can someone provide me a way to remove the file without any downtime?!

Please look at the attached image
Question by:HZarif
    LVL 23

    Assisted Solution

    There's a KB article on this, but the resolution isn't something someone wants to do:

    Try tools like "Unlocker" -

    You might also try running SFC /checknow and then try running chkdsk.

    There's also UBCD and running its tools like TestDisk....but be careful.

    BTW, as always make sure you have a backup of everything first.  Just like the KB article suggests, hopefully you have a known good backup from before this went belly up.
    LVL 87

    Accepted Solution

    Try booting to safemode or safemode with command prompt only. Then run chkdsk /x on all drive letters.
    LVL 23

    Expert Comment

    by:TheCleaner rindi said try that first (despite your no downtime request).

    See here: (but use the /x parameter as rindi suggested, not /f only)
    LVL 26

    Expert Comment

    What error do you get when you try to delete it?
    LVL 1

    Author Comment

    I have attached a jpg of the error I am getting when I try to delete it.
    LVL 26

    Assisted Solution

    No way around it - you're going to have to do a chkdsk on  the D: drive.

    On the upside, if there's no systems files on the D: drive (e.g., a pagefile's not there) you can run CHKDSK without rebooting the server and taking it entirely offline.

    I'd recommend the following:
    Get a backup of the D: drive in its entirety
    From an elevated command prompt, run CHKDSK D: /X/F/V
    See what gets corrected and what the errors are.

    Also, check the event logs to determine if there's drive errors as well; it's possible that's the root cause - a drive going south.

    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    Suggested Solutions

    Redirected folders in a windows domain can be quite useful for a number of reasons, one of them being that with redirected application data, you can give users more seamless experience when logging into different workstations.  For example, if a use…
    Introduction You may have a need to setup a group of users to allow local administrative access on workstations.  In a domain environment this can easily be achieved with Restricted Groups and Group Policies. This article will demonstrate how to…
    This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
    This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

    728 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now