September, 2009

  • Never doubt thy debugger

    New opening: Italian Dev Support blog

    • 0 Comments

    Yesterday my Italian colleagues in Developer Support and I officially inaugurated our new team blog: if you can read Italian then join us at http://blogs.msdn.com/itasupport Nerd smile

     

    Carlo

    Quote of the day:
    Everything that irritates us about others can lead us to an understanding of ourselves. - Carl Jung
  • Never doubt thy debugger

    Hosting on a UNC share is not supported for the Windows XP Platform

    • 3 Comments

    If you have a complex solution, with a lot of folders and subfolders, and you are hosting and debugging it on a remote IIS server (not on your local machine), you may get an error similar to the following:

    An error occurred loading a configuration file: Failed to start monitoring changes to '<path>' 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 article mentioned in the error message (810886) suggests to change the MaxCmds and MaxMpxCt values, but when I had the chance to work on this problem this solution does not always work (anyway I suggest you to give it a try before discarding it).

    You may find another message in your event log, like the following:

    Event Type: Warning
    Event Source: Srv
    Event Category: None
    Event ID: 2021
    Date:
    Time:
    User: N/A
    Computer:
    Description: The server was unable to allocate a work item x times in the last 60 seconds

    If you do, give the article 317249 a try (increase the MaxWorkItems value).

    The solution I find most useful is the one described in 911272: if your .NET build is at least 2.0.50727.62 you already have the fix mentioned in the article but you may need to activate it:

    Registry information
    To enable this hotfix, you must 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 suggest to set FCNMode to 2, so you’ll still have File Change Notifications in place.

     

    Carlo

    Quote of the day:
    The greatest challenge to any thinker is stating the problem in a way that will allow a solution. - Bertrand Russell
Page 1 of 1 (2 items)