Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
The tag present in the reparse point buffer is invalid RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have recently begun to see conflicts in my WHS status, which I can not seem to resolve. From reading through various related threads it appears the problems may have been there a while and just weren't reported until the recent update. As such I don't know what action could have caused them. I did just add a third drive, but I believe the conflicts predate that change. All of the affected files are in the shares folder, and I have verified at least one of them has a left over good copy in the hidden d:\de directory.

     

    The conflict is with about a dozen files. Each one is reporting as:

     The tag present in the reparse point buffer is invalid.

     

    I have tried deleting the files, renaming the files, renaming the parent folder, and copying over the file, all of which fails.

    I've tried many of the suggestions from the various other "Reparse Point" related threads with no success. This includes running WHS Cleanup, and manually trying to "fsutil reparsepoint delete <>" the files. I've also run chkdsk on reboot set to fix errors. WHS Cleanup did correctly identify there was a problem and create the cmd file, but in all cases any action on the file, including the fsutil tool simply reports "The tag present in the reparse point buffer is invalid".

     

    At this point I have no idea how to get rid of these files short of wiping the system and starting over. Does anyone know of a way to fix this "invalid tag" and remove the files?

    Monday, September 1, 2008 6:58 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    skycam said:

    Kariya

    Thanks for the advice however it was not able to delete the reparse point.
    It gave the same error msg.

    Is there a way to try and delete the file before the OS boots?


    From the administrator’s desktop (Remote Desktop into your Windows Home Server) start a command prompt on your home server.

    Once at the command prompt, navigate to the file in question, starting at  d:\shares\. 

    When you have located the directory containing the file in question, use the DEL command to delete the file. 

    Note that you may need to change the attributes of the file, using ATTRIB, to allow it to be deleted.

    Thanks
    Lara Jones [MSFT] Windows Home Server Team
    Tuesday, December 16, 2008 5:05 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Could you please submit a bug report for this on Connect? You may have to create an ID and request access to the "beta" program first. When you submit your bug report, please be sure to include logs from your server; you can send them by using the Toolkit add-in.
    Monday, September 1, 2008 8:26 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am getting the same error with a zbthumbnail.info file.
    I have tried deleting but the error prevents it.
    Is there a way to delete the file during a reboot?
    Monday, December 1, 2008 1:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    skycam said:

    I am getting the same error with a zbthumbnail.info file.
    I have tried deleting but the error prevents it.
    Is there a way to delete the file during a reboot?


    You might try using a tool written by catsaver (another WHS user) called Windows Home Server Cleanup Tool.  It's unsupported, but other users have used it and it worked fine for them.
    Monday, December 1, 2008 4:02 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    I am having the same issue as the original poster. Like them, I also tried running the WIndows Home Server Cleanup Tool to no avail. I really would like to delete this file - can anyone assist? Thank you.
    Tuesday, December 16, 2008 12:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Kariya

    Thanks for the advice however it was not able to delete the reparse point.
    It gave the same error msg.

    Is there a way to try and delete the file before the OS boots?
    Tuesday, December 16, 2008 4:09 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    skycam said:

    Kariya

    Thanks for the advice however it was not able to delete the reparse point.
    It gave the same error msg.

    Is there a way to try and delete the file before the OS boots?


    From the administrator’s desktop (Remote Desktop into your Windows Home Server) start a command prompt on your home server.

    Once at the command prompt, navigate to the file in question, starting at  d:\shares\. 

    When you have located the directory containing the file in question, use the DEL command to delete the file. 

    Note that you may need to change the attributes of the file, using ATTRIB, to allow it to be deleted.

    Thanks
    Lara Jones [MSFT] Windows Home Server Team
    Tuesday, December 16, 2008 5:05 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Command prompt won't let me change attributes of this file.
    I have tried every way I know how to delete from command propmt.
    File has AH attributes
    Keep getting error msg:
    Tag present in the reparse point buffer is invalid.

    Wednesday, January 21, 2009 2:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    skycam said:

    Command prompt won't let me change attributes of this file.
    I have tried every way I know how to delete from command propmt.
    File has AH attributes
    Keep getting error msg:
    Tag present in the reparse point buffer is invalid.



    Can you file a bug for this? We may need to look at your event logs and I can forward the information to the storage team.

    Thanks!
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, January 21, 2009 5:55 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Has there been any resolution to this issue?

    I too have a file that can not be deleted and has resulted in a permanent error for my Windows Home Server.  I have tried a number of utilities for deleting files as well as all of the procedures I found online for identifying and removing file conflicts.  Additionally, I have tried to remove the physical hard drive (where the file conflict resides) from the Windows Home Server configuration.  I have also reinstalled the server.

    Regardless of what I try it always results in the following error:


    Error Deleting File or Folder

    Cannot delete xxxx.xxx. "The tag present in the reparse point buffer is invalid."

    Any help would be appreciated.
    Friday, March 13, 2009 11:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    John Grantman said:

    Has there been any resolution to this issue?

    I too have a file that can not be deleted and has resulted in a permanent error for my Windows Home Server.  I have tried a number of utilities for deleting files as well as all of the procedures I found online for identifying and removing file conflicts.  Additionally, I have tried to remove the physical hard drive (where the file conflict resides) from the Windows Home Server configuration.  I have also reinstalled the server.

    Regardless of what I try it always results in the following error:


    Error Deleting File or Folder

    Cannot delete xxxx.xxx. "The tag present in the reparse point buffer is invalid."

    Any help would be appreciated.


    You should file a bug report on Connect.
    Saturday, March 14, 2009 4:56 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    John Grantman said:

    Has there been any resolution to this issue?

    I too have a file that can not be deleted and has resulted in a permanent error for my Windows Home Server.  I have tried a number of utilities for deleting files as well as all of the procedures I found online for identifying and removing file conflicts.  Additionally, I have tried to remove the physical hard drive (where the file conflict resides) from the Windows Home Server configuration.  I have also reinstalled the server.

    Regardless of what I try it always results in the following error:


    Error Deleting File or Folder

    Cannot delete xxxx.xxx. "The tag present in the reparse point buffer is invalid."

    Any help would be appreciated.



    As kariya21 pointed out, please file a bug for this one. In regards to this thread, I have contact the developer and I am waiting to hear back.

    Thanks
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Saturday, March 14, 2009 6:45 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I checked on connect and there are already multiple entries for this issue.  (It made me check before I could create feedback).

    And I have resolved my issues through a different means.

    I mapped drive letters to all of the hard disks in my Windows Home Server.  I then browsed the contents and found many old and bogus data files.  Not hundreds but thousands of bogus files from 6 months ago or more.

    I had quite a few problems before Power Pack 1 was installed... and those problems included loss of files and duplicate files.  Most of the junk I found was related to those lost files or data that had been deleted months ago.  And based on the time/date for the files they are just left over files or shadow copies.

    I decided it would take less time and be less dangerous to move all my current data to another location and reinstall the server from scratch.  So I moved all the data off the server using the shares.

    Once all the folders showed 0 contents within the console and the shared folders were empty I marked all the backups for deletion and manually executed a cleanup.  I let it run over 24 hours after completion because the drives were still very active.  After restarting the server I was confident all data had been removed.  There was only one file left and it was the file I could not delete (which is why I posted in here in the first place).  I went back to the drive mappings and there were still a ton of files listed in folders unders shares.  Files that had been deleted long ago.  These files were not showing up in the shares.  * I also found a file that matched the file I was having problems with regarding invalid reparse buffer point.  I deleted all the garbage from the drives (via the drive mappings) ... including the original problem file and restarted the server.

    The server started up without running check disk for the first time in 9 months.  The folders were now COMPLETELY empty including the problem file and file copies were 2x - 4x faster from another computer on the network.  Additionally the amount of drive activity (based on the drive light and a drive monitoring utility) went way down.  (To be accurate I measured for 24 hours after I had moved all the data out of the shares and then another 24 hours after I had deleted the garbage via the drive mappings).  Once the garbage was deleted the server performed much faster.

    But I still did not trust this build since it was created long before Power Pack 1 was developed and I had installed 4 new drives over the past 6 months to expand the server's capacity.  (Plus I just got new install media with PP1 from the Microsoft Store in WA).  This would allow me to use a larger and faster drive as the primary server drive.

    So I still rebuilt the server from scratch and now it is running great.  Once I put all the data back (~ 1.5 TB) and start to use it again day to day I will be interested to find out if the garbage files start getting left behind again.

    I sure hope PP1 fixed whatever may have caused my garbage files problems.  I will know for sure in a few days/weeks.

    Thanks to those who replied and provided assistance/feedback.


    John Grantman
    Tuesday, March 17, 2009 1:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    John Grantman said:

    I checked on connect and there are already multiple entries for this issue.  (It made me check before I could create feedback).

    And I have resolved my issues through a different means.

    I mapped drive letters to all of the hard disks in my Windows Home Server.  I then browsed the contents and found many old and bogus data files.  Not hundreds but thousands of bogus files from 6 months ago or more.

    First, mapping directly to each hard drive that is part of WHS is unsupported.  And, yes, before Power Pack 1, there was a data corruption bug (and some people, including myself, had a bunch of empty folders on each drive after balancing finished and/or after deleting all of the files from a folder).  Both of those problems were taken care of in PP1.

    John Grantman said:

    I had quite a few problems before Power Pack 1 was installed... and those problems included loss of files and duplicate files.  Most of the junk I found was related to those lost files or data that had been deleted months ago.  And based on the time/date for the files they are just left over files or shadow copies.

    I decided it would take less time and be less dangerous to move all my current data to another location and reinstall the server from scratch.  So I moved all the data off the server using the shares.

    Once all the folders showed 0 contents within the console and the shared folders were empty I marked all the backups for deletion and manually executed a cleanup.  I let it run over 24 hours after completion because the drives were still very active.  After restarting the server I was confident all data had been removed.  There was only one file left and it was the file I could not delete (which is why I posted in here in the first place).  I went back to the drive mappings and there were still a ton of files listed in folders unders shares.  Files that had been deleted long ago.  These files were not showing up in the shares.  * I also found a file that matched the file I was having problems with regarding invalid reparse buffer point.  I deleted all the garbage from the drives (via the drive mappings) ... including the original problem file and restarted the server.

    The server started up without running check disk for the first time in 9 months.  The folders were now COMPLETELY empty including the problem file and file copies were 2x - 4x faster from another computer on the network.  Additionally the amount of drive activity (based on the drive light and a drive monitoring utility) went way down.  (To be accurate I measured for 24 hours after I had moved all the data out of the shares and then another 24 hours after I had deleted the garbage via the drive mappings).  Once the garbage was deleted the server performed much faster.

    But I still did not trust this build since it was created long before Power Pack 1 was developed and I had installed 4 new drives over the past 6 months to expand the server's capacity.  (Plus I just got new install media with PP1 from the Microsoft Store in WA).  This would allow me to use a larger and faster drive as the primary server drive.

    So I still rebuilt the server from scratch and now it is running great.  Once I put all the data back (~ 1.5 TB) and start to use it again day to day I will be interested to find out if the garbage files start getting left behind again.

    You shouldn't see that now.  If you do, definitely file a bug report on Connect.

    John Grantman said:

    I sure hope PP1 fixed whatever may have caused my garbage files problems.  I will know for sure in a few days/weeks.

    Thanks to those who replied and provided assistance/feedback.


    John Grantman



    Tuesday, March 17, 2009 1:41 AM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote
    PP1 does not resolve the issue, as is noted in my Connect ticket (373151) logged back in October.  Unfortunately MS never responded, never requested anything further, or provided any feedback.

    My system lasted a few months before a file (which I never access) began showing the conflict.  As has been stated by everyone else, there is no way to delete the file short of rebuilding the entire server.

    Connect ticket (365618) also covers the same issue, and it appeared that MS was actually going to provide a utility to fix the reparse point, as noted by Lara, but then never came through.

    Saturday, May 16, 2009 1:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am still unable to resolve the issue where a particular file is showing up in my network health status as: the tag present in the reparse buffer is invalid. I am unable to delete, move or change the attributes of the file. Also, the folder that that file is in is showing as 'failing' - could that be caused by the corrupt file? The health of all 4 of my HDs say 'healthy' - it's just the folder that is showing as 'failing'. Please advise...
    Friday, June 26, 2009 3:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sorry for resurrecting an old thread but it appears there's no real solution listed.  I, too, have a file that says "the tag present in the reparse point buffer is invalid" and am unable to delete it.  This file popped up when I was battling some other data corruption issues that appear to be solved now.

    It seems like there are already some bugs filed on Connect with no resolution.  And it looks like John Grantman, above, had to solve the issue by rebuilding his server.  After dealing with my recent data corruption issues, rebuilding my server is the absolute last thing I want to do.

    So...any resolution short of rebuilding my server?
    Tuesday, October 13, 2009 2:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Even though there are already bugs filed on Connect, can you please file one as well? The more information Microsoft can get about an issue, the more likely they will be able to resolve it.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, October 13, 2009 4:06 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have the same issue with a .CHM file - have tried several methods to remove this but all return the same error (The tag present in the reparse point buffer is invalid)

    I guess the only solution at the moment is to reinstall completely?

    I'm using PP3 Beta.
    Friday, October 16, 2009 1:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have the same issue with a .CHM file - have tried several methods to remove this but all return the same error (The tag present in the reparse point buffer is invalid)

    I guess the only solution at the moment is to reinstall completely?

    I'm using PP3 Beta.
    First thing you should try is uninstalling PP3 beta, then see if the issue persists.  If not, definitely file a bug report on Connect.
    Friday, October 16, 2009 11:27 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Uninstalled PP3 beta, no change. I'm going to move all data off of the drives and reinstall WHS - To speed this up I will be attaching an sata drive to the WHS, would it be safe to copy files from C:\fs\[DRIVE]\DE\shares\ to the attached sata drive? (Rather than through the recommended UNC shares)

    Thanks.
    Tuesday, October 20, 2009 9:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Copy from \DE\Shares is fine, since they contain your actual data.
    Wednesday, October 21, 2009 10:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Resurrecting the question again.

    I have a file that gives this message and can't be deleted.

    My WHS system is only a few weeks old but already has all the data I care about on it, would really rather not rebuild.

    PP3 is not beta any longer; but it may have been installed by Windows Update after the file problem had already occurred?

    Has there been any movement toward a command or utility to allow it to be deleted?

    thanks...

     

    Sunday, March 28, 2010 10:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Bumping this thread *again*.  Same problem as everyone else, "The data present in the reparse point buffer is invalid". 

    File attributes and file delete from command line do not work, error message in cmd.exe is also "The data present in the reparse point buffer is invalid".

    Would be ideal to get some links to Connect that we can bump.

    WHS SP2.

    Tuesday, May 25, 2010 5:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Would suggest using the WHSCleanup tool and/or File Conflict resolver addin.... after you've doing "chkdsk /r" on all your drives
    Tuesday, May 25, 2010 5:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Would suggest using the WHSCleanup tool and/or File Conflict resolver addin....

    I don't think anyone has reported these things can fix the problem.   These programs eventually rely on access and edit/delete of files and attributes, and that doesn't work.  I don't want to download program after program to delete one file.
    Tuesday, May 25, 2010 6:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Same problem here - "The data present in the reparse point buffer is invalid" - on WHS SP2. I have tried chkdsk on my disk and tried other file unlocking utilities (EMCO UnlockIt) - no effect.

     

    I am sure there is a solution for this problem - I hope someone posts it.

     

    Thanks

    Tuesday, May 25, 2010 7:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    WHSCleanup tool and/or File Conflict resolver addin do NOT resolve the issue or allow access to delete the files. the only 'solution' anyone has posted is to blow away and do a complete fresh reinstall of WHS. Not a good solution. MS team, please help.
    Wednesday, May 26, 2010 2:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    WHSCleanup tool and/or File Conflict resolver addin do NOT resolve the issue or allow access to delete the files. the only 'solution' anyone has posted is to blow away and do a complete fresh reinstall of WHS. Not a good solution. MS team, please help.

     

    I guess the bold/underlined text above says it all - this is a Microsoft website and is surely monitored by MS admins. Is there no solution to this issue? If rebuilding/reinstalling is the only solution, then I guess my next question is "is there any harm in letting the error just be there?"

     

    Thanks

     

    Wednesday, June 2, 2010 3:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You might try using a tool written by catsaver (another WHS user) called Windows Home Server Cleanup Tool.  It's unsupported, but other users have used it and it worked fine for them.

    Hi,

     

    I tried the proposed answer which shows this issue as being resolved - it was a non-started. I am sure everyone on this forum has tried to delete the file giving this issue. It is disallowed.

    I then tried catsaver's Home Server Cleanup Tool. It identified the file and built up the .cmd file but the file, when executed, fails to delete the reparse point. It fails with the same message i.e. "tag present in the reparse...".

     

    Any other ideas??

     

    Thanks

    Ashish

    Friday, June 18, 2010 2:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I guess MS has found the sum of a remainder of an unbalanced equation inherent to the programming of the matrix,  which despite their sincerest efforts they have been unable to eliminate from what is otherwise a harmony of mathematical precision.   There doesn't seem to be anything they want to do more. :(
    Wednesday, June 23, 2010 10:15 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    If you are still having this file conflict, would you try below step

    Tag present in the reparse point buffer is invalid

    Symptoms:   This message indicates that a tombstone file has incorrect reparse point tag.  

    Resolution:  You can rescue your file from c:\fs\*\shares first, where * is pointing to your storage pool hard disk volumes. Usually you may not be able to delete the file from your home server using the home server shared folder.  If this happens, use the following procedure to delete the files.

    1.     Access the Windows Home Server desktop.

    2.     From the administrator’s desktop find the conflict file shadow (real file content) through c:\fs\*\shares\, and copy it to d:\shares\ somewhere

    4.     Open a command prompt window, run

    reg add HKLM\System\CurrentControlSet\Services\DEFilter /v Start /t REG_DWORD /d 4 /f

    5.    Reboot the server

    6.    Access the Windows Home Server desktop, and open a command window, run below commands in sequence

    Fsutil reparsepoint delete <your conflict file d:\shares\...>

    Del <your conflict file d:\shares\...>

    reg add HKLM\System\CurrentControlSet\Services\DEFilter /v Start /t REG_DWORD /d 0 /f

    7.    Reboot the server

     

    Tuesday, August 17, 2010 9:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If you are still having this file conflict, would you try below step

    Tag present in the reparse point buffer is invalid

    Symptoms:   This message indicates that a tombstone file has incorrect reparse point tag.  

    Resolution:  You can rescue your file from c:\fs\*\shares first, where * is pointing to your storage pool hard disk volumes. Usually you may not be able to delete the file from your home server using the home server shared folder.  If this happens, use the following procedure to delete the files.

    1.     Access the Windows Home Server desktop.

    2.     From the administrator’s desktop find the conflict file shadow (real file content) through c:\fs\*\shares\, and copy it to d:\shares\ somewhere

    4.     Open a command prompt window, run

    reg add HKLM\System\CurrentControlSet\Services\DEFilter /v Start /t REG_DWORD /d 4 /f

    5.    Reboot the server

    6.    Access the Windows Home Server desktop, and open a command window, run below commands in sequence

    Fsutil reparsepoint delete <your conflict file d:\shares\...>

    Del <your conflict file d:\shares\...>

    reg add HKLM\System\CurrentControlSet\Services\DEFilter /v Start /t REG_DWORD /d 0 /f

    7.    Reboot the server

     


    This Resolution works for the "The tag present in the reparse point buffer is invalid"

    FYI once you complete steps 4 and 5 you wont be able to use any of your files on your server until you change the registry back and reboot as stated in steps 6 and 7.

    Also using the Fsutil command line may not be necessary.  I was able to just browse to the file and delete it.

     

     

    Sunday, October 3, 2010 4:25 PM