Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

WinMgmt.exe - corrupt file


  • Please log in to reply

#1
ncote

ncote

    New Member

  • Member
  • Pip
  • 3 posts
For the last several weeks, my SQL 2000 Server has been getting this message. When I look in the event viewer it only shows up in the system log as an application popup and there is no reference to this error which would indicate that I have a serious problem. But I am running the chkdsk /f and rebooting the computer on a weekly basis. How do I get rid of this message and what does it indicate?

Our environment is in the process of implementing active directory, and the system was a member of the old domain name, which we recently moved into our new domain name. Not sure if that is what causing the problem, seems to coincide.


Application popup: WinMgmt.exe - Corrupt File : The file or directory \System Volume Information\_restore{A4275808-C652-4203-80AB-AA6202A3F2CE}\RP831 is corrupt and unreadable. Please run the Chkdsk utility.
  • 0

Advertisements


#2
admin

admin

    Founder Geek

  • Administrator
  • 24,501 posts
Hi ncote, welcome to Geeks to Go! <_<

The file or directory \System Volume Information\_restore{A4275808-C652-4203-80AB-AA6202A3F2CE}

This file is in a system restore file. I'd start by clearing your restore points. You can clear your restore points by diabling system restore, rebooting, and the enabling it again.
  • 0

#3
ncote

ncote

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Further to my last post, I figured out the problem. So here it is if any of you encounter this same problem. We have a NAS and we have moved several of our SQL databases to the filer. The beautiful thing about this technology is that you can set it up and the operating system doesn't know any different. Through the explorer window, it looks like another drive. This way, we can have several databases on that server but residing on the NAS.

I went through the event viewer, system log and discovered that the first event id created referenced this same location but, it put f:\ and then the rest of the information, which indicated it was the NAS. I was then able to go to the NAS and try to open these files and they were corrupt and I wasn't able to open them. Microsoft has an article on this particular problem (Microsoft Knowledge Base Article - 246026 ) here are the details:

Cannot Delete or Repair Corrupted File on NTFS Volume
View products that this article applies to.
This article was previously published under Q246026
SYMPTOMS
When you try to delete a file on an NTFS volume, you may receive the following error message:

Cannot delete file name: The file or directory is corrupt and unreadable.
The System event log in Windows NT 4.0 contains the following message:

Event ID: 41
Source: Diskperf
Description: The file system structure on disk is corrupt and unreadable. Please run the chkdsk utility on the device with label "Volume_name"
The System event log in Windows 2000 contains the following message:

Event ID: 55
Source: NTFS
Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Drive_letter:"
If you run Chkdsk against the volume, Chkdsk may or may not make repairs, but afterwards you still cannot delete the corrupted file.
CAUSE
This behavior can occur if the NTFS volumes' Master File Table (MFT) is corrupted. The short and long file name pairs that are stored in the directory index record and the file names that are stored in the associated File Record Segment (FRS) contain case-sensitive characters that do not match.

NTFS supports case-sensitive (POSIX) file names, but Chkdsk does not check file names in case-sensitive mode.

For example, assume that the directory index record has a BADFILe.TXT entry but the FRS has a BADFILE.TXT entry for the file name. NTFS views this as being invalid or corrupted, but Chkdsk compares only the names and ignores the case. It does not make repairs.
RESOLUTION
To resolve this issue, back up the volume that contains the corrupted file(s) and exclude the corrupted file(s) from the backup job. Reformat the volume, and then restore from the backup.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
  • 0

#4
ncote

ncote

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
I forgot to mention, Windows Server 2000 does not have the systems restore option.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP