Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot perform all File Server Resource Manager reports, File Management tasks , and FCI- related operations on a computer that is running Windows Server 2008 R2 if one or more mount points do not point to a valid volume


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install the Microsoft File Server Resource Manager role service on a computer that is running Windows Server 2008 R2.
  • One or more mount points are pointing to a destination that no longer exists. For example, a volume that is taken offline or a volume that is moved to another Cluster node.
In this scenario, you cannot perform all File Server Resource Manager reports, File Management Tasks and File Classification Infrastructure (FCI) related operations.

↑ Back to the top


Cause

The File Server Resource Manager module throws an exception and stops operations when namespaces include a mount point whose destination no longer exists . You expect this mount point to be ignored.

↑ Back to the top


Resolution

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 the problem described in this article. 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

To apply this hotfix, you must be running Windows Server 2008 R2. Additionally, the Microsoft File Server Resource Manager service must be installed.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Srm.dll6.1.7600.20618266,75215-Jan-201020:05x64
Srmclient.dll6.1.7600.2061895,23215-Jan-201020:05x64
Srmscan.dll6.1.7600.206181,253,88815-Jan-201020:05x64
Srmtrace.dll6.1.7600.2061899,32815-Jan-201020:05x64
Srm_ps.dll6.1.7600.1638524,06414-Jul-200901:41x64
Srmcontentcls.dll6.1.7600.2061840,96015-Jan-201020:12x86
Srm.dll6.1.7600.20618267,77615-Jan-201020:06x86
Srmclient.dll6.1.7600.2061862,97615-Jan-201020:06x86
Srmscan.dll6.1.7600.20618748,03215-Jan-201020:06x86
Srmtrace.dll6.1.7600.2061870,65615-Jan-201020:06x86
Srm_ps.dll6.1.7600.1638512,28814-Jul-200901:16x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about the File Server Resource Manager, visit the following Microsoft Web sites:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_589f1f7ead3bf32c8327b0c59b526ee5_31bf3856ad364e35_6.1.7600.20618_none_a6d3ca24734d15c0.manifest
File versionNot applicable
File size1,046
Date (UTC)15-Jan-2010
Time (UTC)23:16
PlatformNot applicable
File nameAmd64_bc0e8c3154c552576c2e7c9824b2ef7b_31bf3856ad364e35_6.1.7600.20618_none_8696ed5fe5eb71b6.manifest
File versionNot applicable
File size686
Date (UTC)15-Jan-2010
Time (UTC)23:16
PlatformNot applicable
File nameAmd64_microsoft-windows-fsrm-common_31bf3856ad364e35_6.1.7600.20618_none_267bee3793631415.manifest
File versionNot applicable
File size138,213
Date (UTC)15-Jan-2010
Time (UTC)23:16
PlatformNot applicable
File nameMsil_srmcontentcls_31bf3856ad364e35_6.1.7600.20618_none_e02c3a94fc5c7988.manifest
File versionNot applicable
File size1,600
Date (UTC)15-Jan-2010
Time (UTC)21:04
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,493
Date (UTC)15-Jan-2010
Time (UTC)23:16
PlatformNot applicable
File nameX86_microsoft-windows-fsrm-common_31bf3856ad364e35_6.1.7600.20618_none_ca5d52b3db05a2df.manifest
File versionNot applicable
File size138,209
Date (UTC)15-Jan-2010
Time (UTC)23:16
PlatformNot applicable

↑ Back to the top


Keywords: KB979539, kbqfe, kbsurveynew, kbautohotfix, kbfix, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 979539
Revision : 2
Created on : 10/7/2011
Published on : 10/7/2011
Exists online : False
Views : 240