Microsoft KB Archive Search

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.

  1. Home
  2. Snapshot contents are not accessible when Server for NFS has handle signing enabled

Snapshot contents are not accessible when Server for NFS has handle signing enabled

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a server that is running Windows Server 2012 R2 or Windows Server 2012.
  • You have the "Server for NFS role" service installed.
  • The NFS share that is provisioned by the server for NFS is backed by a volume that has snapshots available on it.
  • You try to use an NFS client to navigate the NFS share that is exported by the "Server for NFS role" service.
In this scenario, you cannot browse the snapshot share.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
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 update in Windows Server 2012 R2, you must first have update 2919355 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the NFS service. To do this, use the following commands:

nfsadmin server stop 
nfsadmin server start

Hotfix replacement information

This hotfix does not replace any previously released hotfix.


File information
The English (United States) 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 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows Server 2012 R2RTMGDR
  • 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 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 2012 R2
File nameFile versionFile sizeDateTimePlatform
Msnfsflt.mofNot Applicable4,46018-Jun-201315:17Not applicable
Msnfsflt.sys6.3.9600.1780431,74411-Apr-201502:04x64
Nfs-servercore-ppdlic.xrm-msNot Applicable2,89311-Apr-201503:15Not applicable
Nfssvc.exe6.3.9600.1780467,58411-Apr-201501:52x64
Nfssvr.mofNot Applicable6,23318-Jun-201315:17Not applicable
Nfssvr.sys6.3.9600.178041,233,40811-Apr-201502:02x64

Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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 8/Windows Server 2012" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows Server 2012 RTMGDR
    6.2.920 0.21xxxWindows Server 2012 RTMLDR
  • 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 2012" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. 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 2012
File nameFile versionFile sizeDateTimePlatform
Msnfsflt.mofNot applicable4,46006-Jul-201220:34Not applicable
Msnfsflt.sys6.2.9200.1645332,25608-Nov-201204:00x64
Nfs-servercore-ppdlic.xrm-msNot applicable2,89313-Apr-201506:25Not applicable
Nfssvc.exe6.2.9200.1645367,58408-Nov-201204:22x64
Nfssvr.mofNot applicable6,23306-Jul-201220:34Not applicable
Nfssvr.sys6.2.9200.173431,249,79213-Apr-201503:21x64
Msnfsflt.mofNot applicable4,46002-Jun-201214:44Not applicable
Msnfsflt.sys6.2.9200.1638432,25626-Jul-201202:29x64
Nfs-servercore-ppdlic.xrm-msNot applicable2,89312-Apr-201522:45Not applicable
Nfssvc.exe6.2.9200.1638467,58426-Jul-201203:08x64
Nfssvr.mofNot applicable6,23302-Jun-201214:44Not applicable
Nfssvr.sys6.2.9200.214561,249,79209-Apr-201522:21x64

Additional file information

Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_42db36e703767e3001c064ad8329192a_31bf3856ad364e35_6.3.9600.17804_none_3a388d204aa4f255.manifest
File versionNot applicable
File size706
Date (UTC)11-Apr-2015
Time (UTC)07:55
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.3.9600.17804_none_4cb97a94db01e54e.manifest
File versionNot applicable
File size38,040
Date (UTC)11-Apr-2015
Time (UTC)03:15
File namePackage_1_for_kb3056053~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot applicable
File size1,838
Date (UTC)11-Apr-2015
Time (UTC)07:55
File namePackage_for_kb3056053_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot applicable
File size1,413
Date (UTC)11-Apr-2015
Time (UTC)07:55
File namePackage_for_kb3056053_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot applicable
File size1,475
Date (UTC)11-Apr-2015
Time (UTC)07:55
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_13e5ede1eb981050a935759710a7d367_31bf3856ad364e35_6.2.9200.17343_none_da6a36fc1216011c.manifest
File versionNot applicable
File size706
Date (UTC)13-Apr-2015
Time (UTC)11:13
PlatformNot applicable
File nameAmd64_c686ffffad1416eefd33e0868b4e1df9_31bf3856ad364e35_6.2.9200.21457_none_a582e9e4c42865e3.manifest
File versionNot applicable
File size706
Date (UTC)13-Apr-2015
Time (UTC)11:13
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.17343_none_b498787690f0797b.manifest
File versionNot applicable
File size38,027
Date (UTC)13-Apr-2015
Time (UTC)11:14
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.21457_none_b51b467daa129a92.manifest
File versionNot applicable
File size38,027
Date (UTC)13-Apr-2015
Time (UTC)11:14
PlatformNot applicable

↑ Back to the top

Workaround

To temporarily work around this problem, you can choose to disable handle signing. To do this, set the HandleSigningEnabled parameter to 0 (zero) as described in Performance Tuning Guidelines for Windows Server 2012 R2.

Note This is a temporary workaround and not a recommended best practice because it has potential security implications.

↑ 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

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbqfe, kbsurveynew, kbautohotfix, kbhotfixserver, kbfix, kbexpertiseinter, kbbug

↑ Back to the top

Article Info
Article ID : 3056053
Revision : 1
Created on : 1/7/2017
Published on : 1/19/2016
Exists online : False
Views : 215