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 access a symbolic link by running Client for NFS if the path length of the symbolic link is too long


View products that this article applies to.

Symptoms

You are running Client for NFS (Network File System) in a Windows-based operating system. However, you cannot access a symbolic link (symlink).

This problem occurs if the following condition is true:
The path length of the symbolic link + the length of the target of the symbolic link + the integer constant "c" is greater than the length of the maximum path length (The maximum path length is 260 characters).
If you run the ls command in a shell prompt in Subsystem for UNIX-based Applications (SUA) when this issue occurs, you receive the following error message:
Data buffer too small to store result
Similarly, if you run the dir command at a command prompt, the destination file information is not displayed as expected.

↑ Back to the top


Cause

This problem occurs because the buffer size that is allocated for a temporary variable is too small.

↑ Back to the top


Resolution

Hotfix information for Windows Server 2003 R2

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, the computer must run Windows Server 2003 R2. Also, Client for NFS must be installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

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 R2, x86-based version
File nameFile versionFile sizeDateTimeSP requirementService branch
Nfsrdr.sys5.2.3790.3287324,09623-Jan-200910:14SP1SP1QFE
Nfsrdr.sys5.2.3790.4452324,60827-Jan-200910:42SP2SP2QFE
Windows Server 2003 R2, x64-based version
File nameFile versionFile sizeDateTimeSP requirementService branch
Nfsrdr.sys5.2.3790.3287480,25629-Jan-200922:25SP1SP1QFE
Nfsrdr.sys5.2.3790.4452480,76829-Jan-200922:31SP2SP2QFE
Windows Server 2003 R2, Itanium-based version
File nameFile versionFile sizeDateTimeSP requirementService branch
Nfsrdr.sys5.2.3790.3287858,11229-Jan-200906:25SP1SP1QFE
Nfsrdr.sys5.2.3790.4452859,13629-Jan-200906:29SP2SP2QFE

Hotfix information for Windows Server 2008 and for Windows Vista

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the computer must run Windows Server 2008 or Windows Vista. Also, Client for NFS must be installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

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 2008 and Windows Vista file information note

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
Windows Server 2008 and Windows Vista, 32-bit version
File nameFile versionFile sizeDateTime
Nfs-clientcore-ppdlic.xrm-msNot Applicable3,00120-Feb-200904:14
Nfsclnt.exe6.0.6001.2238250,68820-Feb-200901:58
Nfsnp.dll6.0.6001.2238259,90420-Feb-200904:41
Nfsrdr.mofNot Applicable4,44818-Dec-200721:27
Nfsrdr.sys6.0.6001.22382195,58420-Feb-200901:58
Windows Server 2008 and Windows Vista, 64-bit versions
File nameFile versionFile sizeDateTime
Nfs-clientcore-ppdlic.xrm-msNot Applicable3,00120-Feb-200904:34
Nfsclnt.exe6.0.6001.2238262,46420-Feb-200902:26
Nfsnp.dll6.0.6001.2238271,16820-Feb-200904:59
Nfsrdr.mofNot Applicable4,44818-Dec-200721:27
Nfsrdr.sys6.0.6001.22382251,90420-Feb-200902:24
Windows Server 2008, Itanium-based version
File nameFile versionFile sizeDateTime
Nfs-clientcore-ppdlic.xrm-msNot Applicable3,00120-Feb-200904:27
Nfsclnt.exe6.0.6001.22382147,45620-Feb-200902:08
Nfsnp.dll6.0.6001.22382154,62420-Feb-200904:52
Nfsrdr.mofNot Applicable4,44818-Dec-200721:27
Nfsrdr.sys6.0.6001.22382572,41620-Feb-200902:06

↑ Back to the top


Workaround

To work around this problem, you can use the absolute path of the target instead of the symlink.

↑ 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, 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 files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTime
Package_1_for_kb967111~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,95220-Feb-200907:40
Package_2_for_kb967111~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,78520-Feb-200907:40
Package_3_for_kb967111~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,77520-Feb-200907:40
Package_for_kb967111_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36720-Feb-200907:40
Package_for_kb967111_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43020-Feb-200907:40
Package_for_kb967111_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,40920-Feb-200907:40
Package_for_kb967111_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42220-Feb-200907:40
Package_for_kb967111_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42320-Feb-200907:40
Package_for_kb967111_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43020-Feb-200907:40
X86_9be8d9b1e2e634967d85b87917558895_31bf3856ad364e35_6.0.6001.22382_none_bfe4feaabb5f27ad.manifestNot Applicable70220-Feb-200907:40
X86_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.0.6001.22382_none_ad179e805bf0c272.manifestNot Applicable40,43420-Feb-200905:02
Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTime
Amd64_74f5e41ab5bf274b9385853eaf88aefa_31bf3856ad364e35_6.0.6001.22382_none_6b2a60cfee3277a8.manifestNot Applicable70620-Feb-200907:40
Amd64_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.0.6001.22382_none_09363a04144e33a8.manifestNot Applicable40,47020-Feb-200905:21
Package_1_for_kb967111~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,96420-Feb-200907:40
Package_2_for_kb967111~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,79520-Feb-200907:40
Package_3_for_kb967111~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,78520-Feb-200907:40
Package_for_kb967111_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37520-Feb-200907:40
Package_for_kb967111_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43820-Feb-200907:40
Package_for_kb967111_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,41720-Feb-200907:40
Package_for_kb967111_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43020-Feb-200907:40
Package_for_kb967111_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43120-Feb-200907:40
Package_for_kb967111_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43820-Feb-200907:40
Additional files for all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTime
Ia64_034dea1b8eb33083e80804ed6325291d_31bf3856ad364e35_6.0.6001.22382_none_b84b55606b671d6b.manifestNot Applicable70420-Feb-200907:40
Ia64_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.0.6001.22382_none_ad1942765beecb6e.manifestNot Applicable40,45220-Feb-200905:11
Package_1_for_kb967111~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,79020-Feb-200907:40
Package_for_kb967111_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42720-Feb-200907:40
Package_for_kb967111_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43420-Feb-200907:40

↑ Back to the top


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

↑ Back to the top

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