asp.net "network BIOS command limit has been reached" ASP.NET 2.0 + 3.5

Question

I'm trying to run tinyMCE texteditor in ASP.NET 2.0 + 3.5 but I get the following error in my web.config file..

An error occurred loading a configuration file: Failed to start monitoring changes to '###\Visual Studio 2005\WebSites\TinyMCE\tinymce\jscripts\tiny_mce\langs' because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft knowledge base article 810886. Hosting on a UNC share is not supported for the Windows XP Platform.

Any ideas how to solve this?

Answer 1

I had the same error: Failed to start monitoring changes to ‘\xxx\yyy\zzz’ because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft knowledge base article 810886. Hosting on a UNC share is not supported for the Windows XP Platform.

At the time I had several windows of Visual Studio open. So, the simplest solution that worked for me was to close those Visual Studious and to leave open just the one I was working on.

Then the error disappeared.

Answer 2

I had this very same problem and the issue was in my web.config file. I had copied over someone elses while trying to get a custom control to work and they had been running on IIS 7, while I was still on IIS 6. The following are the offending lines:

<system.webServer>
  <validation validateIntegratedModeConfiguration="false"/>
  <modules>
    <remove name="ScriptModule" />
    <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral />
  </modules>
  <handlers>
    <remove name="WebServiceHandlerFactory-Integrated"/>
    <remove name="ScriptHandlerFactory" />
    <remove name="ScriptHandlerFactoryAppServices" />
    <remove name="ScriptResource" />
  </handlers>
</system.webServer>

Pretty much, just had to remove everything between the tag. Hope this helps!

Answer 3

This blog post helped me. It walks you through a few different things to try...

1. Add Registry value

Locate the following key in the syustem registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET Add a DWORD FCNMode and set the value to a decimal with the value 1. Restart Visual Studio to ensure the new setting is found.

2. Add Registry value

Another registry edit here. Locate the following key in the system registry HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ASP.NET Add a DWORD FCNMode and set the value to a decimal with the value 2. Restart Visual Studio to ensure the new setting is found.

3. The project is stored on an internal netword

Depending on how your company’s network is configured Visual Studio may store the project on a network drive. Moving the project to a local drive on your machine and trying to run it again has been known to resolve this issue.

4. MSDN Fix

This comes directly from this article on MSDN; http://support.microsoft.com/kb/810886/en-us – I’ve trimmed it down a little. Verify that the MaxCmds and MaxMpxCt registry values are set to 50 or more. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
3. In the right pane, double-click the MaxCmds value.
4. In the Value data box, verify that the value is 50 or more.
5. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Note Make sure that you make this change to the lanmanserver\parameters registry key and not to the lanmanworkstation\parameters registry key mentioned in step 2.
6. In the right-pane, double-click the MaxMpxCt value. Note On SMB servers that are running a version of Windows earlier than Windows 2000, the MaxMpxCt registry entry is named MaxMpxCount, but has the same function.
7. In the Value data box, verify that the value is 50 or more. Note The MaxMpxCt value determines the maximum number of simultaneous, active requests that the server permits from an individual client.
8. Quit Registry Editor.
9. Restart the server.