Network BIOS command limit?

I was trying to set up a web on a mapped network drive in vs2005b2 when I got this cryptic message:

An error occurred loading a configuration file: Failed to start monitoring changes to 'x:\xxx\xxx' because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft knowledge base article 810886.

Has anyone seen this, and more important, has anyone got it to work following the knowledge base article given?

Not that it will be much help but I came across someone else who had the same problem. http://thedotnet.com/blogs/scott_hanselman/archive/2005/04/22/296763.aspx, he found that following the knowledge base didn't solve the problem. His only workaround was to work locally.

Thanks Mitch
I've allready read that blog, albeit joyful reading, it was not that helpful.

-tmh-

I solved the problem. I had to set the proper access for the user logged in to the share on the folder where the files are + some  twiddling with caspol.

 

Hi PinkF,

Would you be kind enough to post a slightly more detailed explanation of how you solved this problem?! I've been wrestling with this one for about 4 days now and haven't got anywhere!

Thanks in advance!



Dan

Got the same problem...  Deployed the remote debugger (which BTW VS2K5 refuses to 'see') and ollowed the reghacks for lanmanworkstation/server [MaxCmd = 65535, etc..]

But still no debugging..    there has to be someone who is using XP with VS2005 on a local subdomain with a IIS 6 W2K3 box who is sucessfully debugging?!! 

Someone help me...

-Eric

I'm experiencing a similar issue while running a Windows 2000 Server SP4, and a Windows 2000 SP4 workstation.  I've applied the reghacks to the server (setting the client lanmanworkstation\parameters\MaxCmds to 65535, and the server lanmanserver\parameters\MaxMpxCt to 65535).  However, I still get the following error when I try to debug:

An error occurred loading a configuration file: Failed to start monitoring changes to '[...]' 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.

The user account is a member of the Administrators group on the server.  I'm not sure where to look for modifying policy settings.

did you ever find a solution to this?

dude please! thats like no information at all, where'd you get the changes? I'm dying here... trying to debug a sharepoint web remotely using VS2008 with a site using .Net 2.0, aa!

For client OS's, Vista and XP, this limit is hard coded in.. it seems for servers, such as Windows 2003, this limit can be configured in the registry.. if you are hitting this wall (I've hit it on solutions loaded via the network, or when asp.net wp running on vista/xp tries to exec an app where its files are on a network share)..

You won't get around it..

I am curious if you ever got a answer to this bios limit problem?
I am currently having this problem on a specific VS2005 project.

I didn't manage to fix this error but I have a way to get around it. It seems like a debugger issue, so I have deployed the whole project to an IIS directory. From there, I could view the project without problems, hitting refresh everytime i want to debug. Just make sure that <customErrors mode="Off"/>

Hope this had helped you all temporarily.

I found a solution that actually works.  You need to add an additional registry key:

Add the following DWORD value at the following registry key:

HKLM\Software\Microsoft\ASP.NET\FCNMode

The following table lists possible values for the FCNMode DWORD value and the behavior that is associated with each value.

Value Behavior Does not exist This is the default behavior. For each subdirectory, the application will create an object that will monitor the subdirectory.

0 or greater than 2 This is the default behavior. For each subdirectory, the application will create an object that will monitor the subdirectory.

1 The application will disable File Change Notifications (FCNs).

2 The application will create one object to monitor the main directory. The application will use this object to monitor each subdirectory.

I recommend setting the value to 1, to disable the FCN.  This is what is causing the error when you try to use the debugger.

Good luck!

Alicia

This issue for me was caused because the drive n:\ I had mapped was to my \\machine\c$ 

It appears the dollar sign was causing this issue.

My project was on n:\myproject.

newrain said:

I found a solution that actually works.  You need to add an additional registry key:

Add the following DWORD value at the following registry key:

HKLM\Software\Microsoft\ASP.NET\FCNMode

The following table lists possible values for the FCNMode DWORD value and the behavior that is associated with each value.

Value Behavior Does not exist This is the default behavior. For each subdirectory, the application will create an object that will monitor the subdirectory.

0 or greater than 2 This is the default behavior. For each subdirectory, the application will create an object that will monitor the subdirectory.

1 The application will disable File Change Notifications (FCNs).

2 The application will create one object to monitor the main directory. The application will use this object to monitor each subdirectory.

I recommend setting the value to 1, to disable the FCN.  This is what is causing the error when you try to use the debugger.

Good luck!

Alicia

I tried this, and took your suggestion that I turn off the FCN's

When running Visual Studio, this caused many headaches.  Every time I tried to run the app for a test, it would inform me that the source was different, and ask me to use it or not.  It also did not always pick up my changes.  Is set it to "2", and it fixed the problem.

This is a wierd one!  I have been programming on this XP box for almost a year with no problems.  But I recently started on a site that would have many pages (over 30), so I segregated the file structure by page, to make working on the project easier.  Still no problem, until I installed a web template using Blend.  Then I could not run ANY projects until I put in this fix...

venturadeb said:

newrain said:

*snip*

I tried this, and took your suggestion that I turn off the FCN's

When running Visual Studio, this caused many headaches.  Every time I tried to run the app for a test, it would inform me that the source was different, and ask me to use it or not.  It also did not always pick up my changes.  Is set it to "2", and it fixed the problem.

This is a wierd one!  I have been programming on this XP box for almost a year with no problems.  But I recently started on a site that would have many pages (over 30), so I segregated the file structure by page, to make working on the project easier.  Still no problem, until I installed a web template using Blend.  Then I could not run ANY projects until I put in this fix...

I had exactly the same problem:

An error occurred loading a configuration file: Failed to start monitoring changes to '\\xxx\xxx\xxx 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

 I added two registry keys according to http://support.microsoft.com/default.aspx/kb/810886 and then restarted the server.

After this error disappeared.

bor said:

venturadeb said:

*snip*

I had exactly the same problem:

An error occurred loading a configuration file: Failed to start monitoring changes to '\\xxx\xxx\xxx 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

 I added two registry keys according to http://support.microsoft.com/default.aspx/kb/810886 and then restarted the server.

After this error disappeared.

With assistance from our IT dept, I applied a .reg file which I believe is the hotfix described here.

 

It appears to set the FCMMode to 2. Doesn't sound like you'd want it set to anything else, based on testimony above.

 

If setting the keys as described in KB810886 doesn't work, try this, described at the link above.

This can be solved by using this KB article (http://support.microsoft.com/kb/810886/en-us) and instead of using their suggested increase of '50' use '2048' instead.  You need to make this change on both the server (hosting the UNC share) and the workstation (running the debugging) and restart both machines and try again.

This solved my issue.

 

Cheers
Ånubis.