Error message when you use a Windows Vista-based computer to try to access files on a Windows Vista-based file server: lt;DriveLetter gt;: is not accessible. Insufficient system resources exist to complete the API

Error message when you use a Windows Vista-based computer to try to access files on a Windows Vista-based file server: <DriveLetter>: is not accessible. Insufficient system resources exist to complete the API
Article ID : 938475
Last Review : November 2, 2007
Revision : 2.2
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (/Feedback.aspx?kbNumber=256986/) Description of the Microsoft Windows registry
On This Page

SYMPTOMS

When you use a Windows Vista-based computer to try to access files on a Windows Vista-based file server, you may receive an error message that resembles the following:
DriveLetter: is not accessible.
Insufficient system resources exist to complete the API.

Back to the top

CAUSE

This problem occurs if you try to access the file by using a long-term Server Message Block (SMB) request, and if more than 64 concurrent long-term SMB requests are sent to the file server. In this situation, all other long-term SMB requests are not answered.

Note Unlike typical SMB requests, a long-term SMB request remains open until it is answered by the server. For example, a long-term request is sent when a client computer uses the FindFirstChangeNotification function to monitor a shared resource for changes.

In Windows Vista, the Server service intentionally limits the maximum number of concurrent asynchronous network requests to 64. A Windows Vista-based client computer also has this limitation. However, the file server processes typical SMB requests immediately.

Note If both of the file server and the client computer are Windows Vista-based computers, the SMB 2.0 protocol is used for file sharing operations.

Back to the top

RESOLUTION

To resolve this problem, apply the following hotfix to both the file server and the client computer. After you apply the hotfix, you must modify a registry entry on the server to configure the maximum number of concurrent SMB requests. For more information about how to do this, see the Registry information section.

Back to the top

Hotfix information

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451)

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Prerequisites

No prerequisites are required.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, modify the AsynchronousCredits registry entry on the file server to configure the maximum number of concurrent SMB requests. To do this, follow these steps:

1. Click Start, type regedit in the Start Search box, and then press ENTER.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Lanmanserver Parameters
3. In the details pane, double-click the AsynchronousCredits entry.

Note The value type of this entry is REG_DWORD. The value data of this entry is decimal. If the AsynchronousCredits registry entry does not exist, create it.

4. In the Value data box, enter the maximum number of concurrent SMB requests.

Note If the value is larger than 64, resource usage on the file server increases. The file server may run out of resources such as paged pool memory. We recommend that you limit number of clients that access the file server before you increase this value.

This article does not make specific recommendations on the value that you set because of the complexity of the network environment.

5. Exit Registry Editor.

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 Vista, 32-bit versions
File name File version File size Date Time Platform
Package_1_for_kb938475~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,783 15-Jun-2007 17:34 Not Applicable
Package_2_for_kb938475~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,996 15-Jun-2007 17:34 Not Applicable
Update.mum Not Applicable 1,897 15-Jun-2007 17:34 Not Applicable
X86_25d0b76c7c00d970e39bd582c48dc22c_31bf3856ad364e35_6.0.6000.20620_none_cbbc3c6387dbeb8b.manifest Not Applicable 698 15-Jun-2007 17:34 Not Applicable
X86_9f816cda4d567616d3afaac228e6dba9_31bf3856ad364e35_6.0.6000.20620_none_6a3a12f093b96198.manifest Not Applicable 700 15-Jun-2007 17:34 Not Applicable
X86_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6000.20620_none_7e1f299c6d24b8b7.manifest Not Applicable 9,344 15-Jun-2007 17:35 Not Applicable
X86_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.0.6000.20620_none_d87a55d61282fd5a.manifest Not Applicable 4,718 15-Jun-2007 17:35 Not Applicable
Mrxsmb.sys 6.0.6000.20620 101,888 15-Jun-2007 00:50 x86
Srv2.sys 6.0.6000.20620 130,560 15-Jun-2007 00:51 x86
Windows Vista, 64-bit versions
File name File version File size Date Time Platform
Amd64_872643c0e08b3bfea6e35d908e0eff9e_31bf3856ad364e35_6.0.6000.20620_none_2c94f2fd4b883804.manifest Not Applicable 704 15-Jun-2007 17:34 Not Applicable
Amd64_c0811949d12dd84ac380a6ab85453b26_31bf3856ad364e35_6.0.6000.20620_none_954a2531d9f6fb41.manifest Not Applicable 702 15-Jun-2007 17:34 Not Applicable
Amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.0.6000.20620_none_da3dc520258229ed.manifest Not Applicable 9,615 15-Jun-2007 17:44 Not Applicable
Amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.0.6000.20620_none_3498f159cae06e90.manifest Not Applicable 4,983 15-Jun-2007 17:44 Not Applicable
Package_1_for_kb938475~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,793 15-Jun-2007 17:34 Not Applicable
Package_2_for_kb938475~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 2,008 15-Jun-2007 17:34 Not Applicable
Update.mum Not Applicable 1,909 15-Jun-2007 17:34 Not Applicable
Mrxsmb.sys 6.0.6000.20620 133,632 15-Jun-2007 01:04 x64
Srv2.sys 6.0.6000.20620 163,840 15-Jun-2007 01:05 x64

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

SMB 2.0 is a new version of SMB that is designed for the latest networking environments and for the needs of the next generation of file servers. SMB 2.0 is the default protocol for Windows Vista-based file servers and for file servers that run Windows Server 2008.

For more information about SMB 2.0, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/bb726965.aspx (http://technet.microsoft.com/en-us/library/bb726965.aspx)

For more information about the FindFirstChangeNotification function, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/aa914108.aspx (http://msdn2.microsoft.com/en-us/library/aa914108.aspx)

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

937082 (/Feedback.aspx?kbNumber=937082/) You cannot configure the maximum number of concurrent SMB requests that are sent to a Windows Vista-based file server
926646 (/Feedback.aspx?kbNumber=926646/) You cannot configure the maximum number of concurrent SMB requests that are sent to the Server service in Windows XP

For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top



APPLIES TO
• Windows Vista Ultimate
• Windows Vista Business
• Windows Vista Enterprise
• Windows Vista Ultimate 64-bit Edition
• Windows Vista Business 64-bit Edition
• Windows Vista Enterprise 64-bit Edition

Back to the top

Keywords: 
kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver KB938475

Back to the top

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image