locked
Unable to rename files or folders in a particular folder. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    I have one particular location running Windows 2008R2 on Vmware where a particular share is not allowing users to rename files or directories within this share.

    Attempting to rename a file from a dos prompt gives the error message "The process cannot access the file because it is being used by another process.

    Attempting to rename in explorer gives "The action can't be completed because the file is open in another program"

    The file or directory is not in use and is confirmed by running handles filename and no results are found.

    I can create new files or folders, delete files or folders, edit  and save the newly created file (within notepad), just not rename it.

    If I go up a directory or down a directory, I can add, delete, edit AND rename the file so it's got to be something funky with the permissions. All the permissions are set to  various users and groups as Full Control for This folder, subfolder and files.

    No Deny access has been granted.

    I cannot move a file into this directory either.

    Running procmon shows the following capture as I tr to rename e:\shares\buyer\a.txt  to b.txt

    

    If I reboot the server, the problem goes away....for a couple of days.

    AV has been disabled 

    Any ideas?

    http://absoblogginlutely.net


    • Edited by helsby Thursday, November 12, 2015 9:40 PM added Vmware parent. Removed c:\temp issues.
    Thursday, November 12, 2015 9:21 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Shaon - I should have highlighted the lines that were the issue - not the one below ;-)

    My issue is actually with renaming e:\shares\buyer\a.txt  to b.txt in this particular case, but in actual fact any file renames or additions into the e:\shares\buyer directory.

    The issue starts to occur after the server has been up and running for sometime, although the most recent case was after the server had been up for only 2 days. As a reboot clears the problem for a while, it does seem to imply that permissions and chkdsks are reporting fine, but this is more of a resource issue on the server.

    As it's a production server (when would it ever *not* be a production server) and the issue takes a while to occur, I can't leave the server in safe mode or clean boot to see what happens, especially as the reboot to get into safe/clean mode will also clear the lock in the first place.

    I did notice that the server still had vmware tools on it after it was v2v'd to a hyperv server, so I removed the vmware tools (by hand) and as the issue seems to be resource related I also increased the memory on the server.  I am hoping this was the culprit and the issue does not occur again.

    http://absoblogginlutely.net

    Tuesday, November 17, 2015 5:28 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can use this tool to see what process is locking the files.

    https://technet.microsoft.com/en-us/sysinternals/processmonitor

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Thursday, November 12, 2015 9:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    processmonitor is the tool I used above to generate the screenshot. Unless I'm missing something, it's not showing any locks in the gui (without delving deep into tracing) and handles from sysinternals also shows no locks.

    http://absoblogginlutely.net

    Thursday, November 12, 2015 10:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ok, sorry, missed that. You may need to chkdsk the drive.

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.


    Thursday, November 12, 2015 10:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    From the description, as you can delete the file, it seems not related to NTFS permission as rename requires the same permission as Delete + Write. Also if it is a permission issue, the error message should be different.

    I noticed that the folder is under c:\windows\Microsoft .NET - is it IIS or any application related? As AV was disabled already, check if there is any other application needs to access that folder.

    Also test to go to Safe Mode just to see if you can rename files. Most applications will not be started in Safe Mode so it could help us confirm whether or not it is NTFS permission related.

    If issue does not exist, you can try Clean Boot (disable all third party startups and Services in MSCONFIG) to continue the narrow down.

    How to perform a Clean Boot:

    https://support.microsoft.com/en-us/kb/929135

    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Sunday, November 15, 2015 8:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Shaon - I should have highlighted the lines that were the issue - not the one below ;-)

    My issue is actually with renaming e:\shares\buyer\a.txt  to b.txt in this particular case, but in actual fact any file renames or additions into the e:\shares\buyer directory.

    The issue starts to occur after the server has been up and running for sometime, although the most recent case was after the server had been up for only 2 days. As a reboot clears the problem for a while, it does seem to imply that permissions and chkdsks are reporting fine, but this is more of a resource issue on the server.

    As it's a production server (when would it ever *not* be a production server) and the issue takes a while to occur, I can't leave the server in safe mode or clean boot to see what happens, especially as the reboot to get into safe/clean mode will also clear the lock in the first place.

    I did notice that the server still had vmware tools on it after it was v2v'd to a hyperv server, so I removed the vmware tools (by hand) and as the issue seems to be resource related I also increased the memory on the server.  I am hoping this was the culprit and the issue does not occur again.

    http://absoblogginlutely.net

    Tuesday, November 17, 2015 5:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for the reply.

    As it has been a while, whether the issue reoccurs? 

    Still if you can delete any of these files but just not able to rename, it seems not be a permission issue. 

    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, November 26, 2015 10:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I can confirm the problem has gone away. It was either the beware tools on a hyperventilating or more likely the lack of memory on the server.

    http://absoblogginlutely.net

    Thursday, November 26, 2015 12:25 PM