FSRM - reset all configuration to defaults. (Solved)

[pete]

On a previously-working FSRM, clicking New Storage report or New File Screen Template in FSRM (or attempting to edit an existing template or report) causes the error message:

 

"An unexpected error has occurred. Please check application event log for more information.

 

Details: Value of '10000' not valid for 'Value', 'Value' should be between 'Minimum' and 'Maximum'

Parameter name: Value"

 

Event log for the error in Storage Reports (FSRM source, Event ID 0):

 

An unexpected error occurred in the File Server Resource Manager MMC snap-in

 

Value of '10000' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.

Parameter name: Value

at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)

at Microsoft.Storage.SrmMmc.FilesByOwnerReportParametersDialog.LoadValuesToUI()

at Microsoft.Storage.SrmMmc.ReportTypeControl.InitializeSrmSpecific(RemoteManager remoteManager, HostFlags hostFlags)

at Microsoft.Storage.SrmMmc.ReportTypeSelectionControl.InitializeSrmSpecific(RemoteManager remoteManager, HostFlags hostFlags)

at Microsoft.Storage.SrmMmc.StorageTasksDisplayArea.OnAddRemoveReports(Object sender, EventArgs eventArgs)

 

Event log for the error in File Screen Templates (FSRM source, Event ID 0):

 

An unexpected error occurred in the File Server Resource Manager MMC snap-in

at Microsoft.Storage.SrmMmc.RunReportPage.InitializeSrmSpecific(RemoteManager remoteManager, HostFlags hostFlags)

at Microsoft.Storage.SrmMmc.FileScreenPropertySheetBase.InitializeSrmSpecific(RemoteManager remoteManager, HostFlags hostFlags)

at Microsoft.Storage.SrmMmc.FileScreenTemplatesDisplayArea.OnCreateFileScreenTemplate(Object sender, EventArgs eventArgs)

Value of '10000' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.

Parameter name: Value

at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)

at Microsoft.Storage.SrmMmc.FilesByOwnerReportParametersDialog.LoadValuesToUI()

at Microsoft.Storage.SrmMmc.ReportTypeControl.InitializeSrmSpecific(RemoteManager remoteManager, HostFlags hostFlags)

at Microsoft.Storage.SrmMmc.ReportTypeSelectionControl.InitializeSrmSpecific(RemoteManager remoteManager, HostFlags hostFlags)

at Microsoft.Storage.SrmMmc.RunReportPage.InitializeSrmSpecific(RemoteManager remoteManager, HostFlags hostFlags)

 

which points to Storage reports being the problem.

 

Solutions attempted:

 

• Remove FSRM and then re-install (uses old config, fails in the same manner)
  
• Delete all (visible) config, remove FSRM and re-install (still uses old config, fails in the same manner)
  
• Export config, check the existence of "10000" (not found), modify and re-import (no joy)
  

 

Google has a few similar-ish sounding things where FSRM has fallen over, but the solutions suggested (remove and re-add FSRM), etc haven't solved the issue since FSRM will re-use the existing configuration. Plus the vague error doesn't help when searching.

 

Any ideas / places to look to manually purge the config?

Edited June 14, 2021 by pete
Solved

[pete]

More context:

 

All of the following FSRM function work correctly:

 

• Editing File Screens and File Groups
  
• Classification Management
  
• File Management tasks
  
• Quotas and Quota templates
  

 

Attempting to amend/add Storage Reports or File Screen Templates using powershell or fscrn / storrept also fails. It's not just an MMC issue.

 

Search through settings (using get-fsrmsetting and set-fsrmsetting) and adjusting any "10000" values to a lower value (1000), then restarting FSRM merely changes the error message to complain that "1000" isn't a valid Value.

Edited June 14, 2021 by pete

[pete]

And as often happens when I have to document a problem for other people....

 

TLDR:

 

Using the defaults listed here: https://techcommunity.microsoft.com/t5/storage-at-microsoft/set-fsrm-storage-report-limits-using-powershell/ba-p/425362

 

I used set-fsrmsetting to reset the values to under the defaults, so each was an unique value and restarted FSRM.

 

And now Storage Reports and File Screen Templates are working correctly.

 

 

The takeaway is that the MMC will let you amend report values to unsafe amounts and prevent subsequent editing.