Unable to rename folders ("file in use"), can be solved by restarting Forefront services ... started 2 weeks ago
30 Nopember 2011 12:14
Since November 18, we repeatedly have the issue that users can't rename folders on 2008 R2 file servers. They can create and delete folders, they can create, delete and rename files, but they can not rename folders. Windows claims that the folder would be "in use" and hence can't be renamed.
It can't be related to permissions as it does not work even from a local administrative command prompt or as the System account, even if Everyone has Full permissions on the folder. I found that it can be "solved" (for few hours or days) by restarting the FCSAM ("Microsoft Forefront Client Security Antimalware Service") service.
This issue has NEVER happened before, but since November 18 we have it almost on a daily basis on multiple servers. Can it somehow be related to the Forefront/definition updates that were released at that time?
02 Desember 2011 9:27Moderator
Thank you for your post.
My FEP with the latest update has not occurred the issue like yours.
Please give the FEP/virus & spyware definition version to us.
Try to use procmon to find if other process use the folder (or show access deny entries) when you rename it.
Try to create another folder with several files in another drive to test rename the folder.
If there are more inquiries on this issue, please feel free to let us know.
09 Desember 2011 10:01
Hi, sorry for the late reply.
We are using FCS, not FEP:
Client Version: 1.5.1996.0
Engine Version: 1.1.7903.0
Antivirus definition: 1.117.692.0
Antispyware definition: 1.117.692.0
I already used Procmon, Procexp and Handle to investigate the issue. There are no other processes that have these folders locked (and can't be as it also happens to newly created folders). Even when I create a new folder, I can't rename it from the "New Folder" name to something else.
Sometimes it happens that the error message is displayed ("Access Denied"), but still the renaming worked.
The issue can be resolved for a while by restarting the FCSAM service.
09 Desember 2011 10:25I never seen that before !! Well, is that problem exist only on that server ? Have installed a hotfix or a patch for Windows on 17 or 18 november ? I know the same problem can appear in some situation for excel files but never seen that for folders. Anyway, openning a case with MS support it is the quick way to get a solution.
Bechir Gharbi | http://myitforum.com/myitforumwp/members/bgharbi/ | Time zone : GMT+1
- Ditandai sebagai Jawaban oleh Rick TanModerator 12 Desember 2011 2:04