Error message when you generate a "Files by Owner" report in the File Server Resource Manager management console on a Windows Server 2003 R2-based computer: "An unexpected error has occurred"

Consider the following scenario. You use the File Server Resource Manager management console (Fsrm.msc) on a Microsoft Windows Server 2003 R2-based computer. Specifically, you try to generate a Files by Owner report by specifying a particular user as the owner. However, you receive the following error message:Additionally, an event that resembles the following is logged in the Application log:

Event Type: Error
Event Source: FSRM
Event Category: None
Event ID: 0
Date: 5/17/2006
Time: 3:15:58 PM
User: N/A
Computer: ComputerName
Description: An unexpected error occurred in the File Server Resource Manager MMC snap-in
at Microsoft.Storage.SrmMmc.ReportTask.SaveChanges(ISrmReportManager reportManager)
at Microsoft.Storage.SrmMmc.StorageReportTaskPropertySheet.SaveChanges()
at Microsoft.Storage.SrmMmc.PropertySheet.OnOkButtonClicked(Object sender, EventArgs eventArgs) Invalid argument: FilterByOwners[0] = 'John Doe'
at Microsoft.Storage.SrmMmc.ISrmReport.SetFilter(String filterName, Object filterValue)
at Microsoft.Storage.SrmMmc.ReportTask.SaveChanges(ISrmReportManager reportManager)

This problem occurs when you generate a Files by Owner report for an owner who does not have a user principal name (UPN).

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must be running Windows Server 2003 R2 to apply this hotfix.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: