none
Windows 2008 FSRM Quota: Running Command Line action wont work RRS feed

  • Question

  •  

    I am using windows 2008 R2

    I have tried all options found on google eg

    running c:\windows\system32\cmd.exe and also placing a batch file in the same directory. No Joy.

    All I try to do now is just run c:\windows\system32\cmd.exe with no arguments, to eliminate access rights issues with my batch file.

    Output from event manager is:

    Event 8197, SRMSVC

    File Server Resource Manager Service error: Unexpected error.

    Operation:

    Running command line action.

    Quota threshold reached

    Processing File Server Resource Manager event

    Action Type: Command Action

    Account: NT AUTHORITY\NetworkService

    Executable path: C:\windows\system32\cmd.exe

    Arguments:

    Working Directory: is c:\storagereports\incident

    Quota Path: C:\

    Threshold: 90

    Error specific details:

    Error:AuthzInitializeContextFromSid, 0x80070005, Access is denied

     

    Friday, September 23, 2011 1:46 PM

Answers

  • I managed to fix it myself.

    The problem was I was logged on as a remote user who had been put into the administrators group. In order to be able to configure the FSRM succesfully you need to be a local administrator on the machine. I created an admin account local to the machine to get around this problem.

    It seems that FSRM will allow you to configure a quota with a command action even if you are a remote admin account, but when the quota is reached the command doesn't get executed. You get 'access denied' in the event viewer. At that point Windows realizes that the user who set it up  doesn't have the correct access rights.I wish it would just not allow you to run FSRM and configure it, it gives you a false sense of progress.

    Once I logged in as a local administrator and ran FRSM and in the quota parameters and I put c:\windows\system32\cmd.exe in the command line and the arguments were /c "mybatch.bat" it all started working.

    The double quotes around the batch file are also required.

    Once I chose the location of the log file and also an output file I was creating there was no issues with authentication ie you dont need to put them under c:\windows. I just created a new directory in c:

    There is nothing in W2008 to help you work through these kind of issues, you just have to try different approaches and hope you find the way.

    There seems to be no shortage of bloggers describing these 'wonderful' features, but obvioulsy they just re-worded Msoft documents, they didn't actually try out all the features and provide some useful information on the pitfalls that can be encountered.

    Several more days wasted out of my life..


    Thursday, September 29, 2011 6:00 AM

All replies

  • Hi Steve,

    what exactly are you trying to do? Run a batch file? Could you paste it here so we can give a look and see what can be the issue?

    Please provide more details.

     

     


    Thank you,

    F. Schubert
    System Administrator

    MCT | Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Tuesday, September 27, 2011 3:19 PM
  • Hi,

    It seems to be a FSRM related error.

    Here is a similar thread:

    http://social.technet.microsoft.com/Forums/en-US/winserverManagement/thread/c0f61131-8d6f-4853-b41e-4694642af939


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.
    Wednesday, September 28, 2011 8:47 AM
    Moderator
  • I managed to fix it myself.

    The problem was I was logged on as a remote user who had been put into the administrators group. In order to be able to configure the FSRM succesfully you need to be a local administrator on the machine. I created an admin account local to the machine to get around this problem.

    It seems that FSRM will allow you to configure a quota with a command action even if you are a remote admin account, but when the quota is reached the command doesn't get executed. You get 'access denied' in the event viewer. At that point Windows realizes that the user who set it up  doesn't have the correct access rights.I wish it would just not allow you to run FSRM and configure it, it gives you a false sense of progress.

    Once I logged in as a local administrator and ran FRSM and in the quota parameters and I put c:\windows\system32\cmd.exe in the command line and the arguments were /c "mybatch.bat" it all started working.

    The double quotes around the batch file are also required.

    Once I chose the location of the log file and also an output file I was creating there was no issues with authentication ie you dont need to put them under c:\windows. I just created a new directory in c:

    There is nothing in W2008 to help you work through these kind of issues, you just have to try different approaches and hope you find the way.

    There seems to be no shortage of bloggers describing these 'wonderful' features, but obvioulsy they just re-worded Msoft documents, they didn't actually try out all the features and provide some useful information on the pitfalls that can be encountered.

    Several more days wasted out of my life..


    Thursday, September 29, 2011 6:00 AM
  • I have been struggling with a similar issue, trying to run a powershell script to generate a more involved email notification. I followed Shaon Shan's link, and though I didn't follow the steps to modify the permissions on the FSRM XML files, I did use psexec to launch a cmd.exe as the Local System account. I ran the dirquota command in this context, and then the script was executed successfully.

    Thanks to you both.

    --Geoff

    Friday, January 20, 2012 7:20 PM