Troubleshooting File Server Resource Manager

  • Article

Applies To: Windows Server 2003 R2

This section lists a few common issues you may encounter when using File Server Resource Manager.

What problem are you having?

  • I am not receiving any e-mail notifications

  • I am only receiving one e-mail notification, even though the event that caused it happened several times in a row

  • My storage reports keep failing and no or little information is available in the Event Log regarding the source of the failure

  • My File Audit reports do not contain any information

  • The "Used" and "Available" values for some of the quotas I have created do not correspond to the actual "Limit" setting

Note

A good troubleshooting option is to look for event logs generated by File Server Resource Manager. All event log entries for File Server Resource Manager can be found in the Application event log under the source: SRMSVC.

I am not receiving any e-mail notifications.

Cause:

The e-mail options have not been configured or have been configured incorrectly.

Solution:

Verify that the SMTP server and e-mail settings in the File Server Resource Manager options have been specified and are valid. Send a test e-mail to confirm that the information is correct and that the SMTP server used to send the notifications is working properly. For more information see Configure E-mail Notifications.

I am only receiving one e-mail notification, even though the event that triggered that notification happened several times in a row.

Cause:

When a user attempts several times to save a blocked file, or a file that exceeds a quota limit, and there is an e-mail notification configured for that file screening or quota event, then only one e-mail will be sent to the administrator for a period of 60 minutes. This prevents over-flooding of messages in the administrator's e-mail account.

Solution:

This is a feature of File Server Resource Manager.

My storage reports keep failing and no or little information is available in the Event Log regarding the source of the failure.

Cause:

The volume where the reports are being saved may be corrupted.

Solution:

Run chkdsk on the volume and try generating reports again.

My File Audit reports do not contain any information.

Cause:

The auditing database is empty (that is, no file screening activity has been reported) or the File Screen Audit properties have not been configured.

Solution:

In the File Server Resource Manager Options dialog box, on the File Screen Audit tab, verify that the Record file screening activity in the auditing databasecheck box is selected. For more information, see Configure File Screen Audit.

The "Used" and "Available" values for some of the quotas I have created do not correspond to the actual "Limit" setting.

Cause:

You may have a nested quota, where the quota that applies to a folder will be a more restrictive quota that derives from one of its parent folders.

Solution:

Under Quota Management, go to Quota, and then select the quota entry that you are troubleshooting. Click View quotas affecting folder on the actions pane, and look for quotas applied to parent folders. This will allow you to identify which quotas have restrictive settings on the quota you have selected (that is, which parent folder quotas have a lower storage limit setting).