Network BIOS command limit has been reached
I've got Visual Studio 2008 running on Windows 7 64bit UltimateRC, when I try to build a project hosted on a unc share I get the following error:An error occurred loading a configuration file: Failed to start monitoring changes to 'filepath' 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.In both XP and Vista this was resolved by adding/increasing the MaxCmnds and MaxMpxCt entries under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters but this isn't working with Win 7.Any suggestions or workarounds for this other than storing the files on the local machine?
June 8th, 2009 10:31am
same problem here
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2009 12:41am
Did you every get this to work?
November 5th, 2009 5:13pm
I am using Visual Studio 2010 running on Windows 7 64bit Professional and had the same issue. As mentioned in the post above, setting the FCNMode to 2 under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ASP.NET fixed it.
Thanks!
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2010 9:37am
Running Visual Studio 2008 on Windows 7 64bit Enterprise. Similar issue.
Adding the FCNMode value 2 worked for me.
There are lots of other web posts that point to
http://support.microsoft.com/kb/810886. That did not work for me.
Thank you.
July 22nd, 2010 9:02am
How nice that someone shared this knowledge, running Seven Ultimate 64 bit on Mac, there was no way i was going to find out for myself!
Problem solved Thank you!
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2010 4:54pm
Perfect. Thanks for sharing.
Additionally I can confirm that this solution also work on a Windows 7 Ultimate 32-bit. Only difference is, you should add the FCNMode key to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET.
November 22nd, 2010 8:48am
Perfect. Thanks for sharing.
Additionally I can confirm that this solution also work on a Windows 7 Ultimate 32-bit. Only difference is, you should add the FCNMode key to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET.
Same here. I had a parallels VM to a file share to my host Mac hard drive and changing this registry setting fixed it. I had to log out and log back in though.
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2011 4:54pm
This worked for me. But I have one question. In my case the problem was not reproduceable on demand it was occuring sometimes when I was clicking on sub directories pages. Now its not happening but how can I assure that this will not happen again.
October 11th, 2011 2:34am
Adding the DWORD FCNMode to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET didn't work for me. I had to add it to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET and set its value to 3.
Free Windows Admin Tool Kit Click here and download it now
December 21st, 2011 11:33am
I had the same problem on Windows 7 64 Bits , but with visual studio 2008.
Here is how I solved it:
1- I removed the read only property for the base project folder.
2- Closed the ASP.net Development Server icon from the Menu bar, near the clock.
3- Rebuild the project
Please keep in mind in such case every time you run the project you have to close the asp.net development server icon.
February 13th, 2012 1:15pm
I had the same problem on Windows 7 64 Bits , but with visual studio 2008.
Here is how I solved it:
1- I removed the read only property for the base project folder.
2- Closed the ASP.net Development Server icon from the Menu bar, near the clock.
3- Rebuild the project
Please keep in mind in such case every time you run the project you have to close the asp.net development server icon.
This fixed my problem. Thank you!
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2012 4:50pm
I have same problem with VS 2010 running on Windows 7 Enterprise which I logged on into it through Terminal Server and I don't have permission to change the registery keys.
Any suggestion?
June 18th, 2012 8:07pm