Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / ADO.NET / April 2006

Tip: Looking for answers? Try searching our database.

webservices - always work local?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jeff Jarrell - 22 Apr 2006 03:35 GMT
I am coming from a shop that is historically is winforms and we work in our own workareas on network drives. Primarily so  the daily work gets backed up but also so it is easy to look at each other's work in progress. we aren't all in the same location.  The version control and build tools are oriented around this configuration.

We are finally moving towards some web services and after a couple of hours it appears that the path of least resistance is to work locally.  I tried using local iis with virtual dirs pointing to the network shares but I keep coming across this...

Error 1 An error occurred loading a configuration file: Failed to start monitoring changes to '\\popeye\jarr\scServices\app_data' 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 tried the registry patches mentioned in the KB, but it seems the error ultimately comes back.

So do I just give up and work locally?  Is that the convention?

thanks,
jeff
Jeff Jarrell - 22 Apr 2006 16:44 GMT
Oops, sent it to the wrong group.
 I am coming from a shop that is historically is winforms and we work in our own workareas on network drives. Primarily so  the daily work gets backed up but also so it is easy to look at each other's work in progress. we aren't all in the same location.  The version control and build tools are oriented around this configuration.

 We are finally moving towards some web services and after a couple of hours it appears that the path of least resistance is to work locally.  I tried using local iis with virtual dirs pointing to the network shares but I keep coming across this...

 Error 1 An error occurred loading a configuration file: Failed to start monitoring changes to '\\popeye\jarr\scServices\app_data' 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 tried the registry patches mentioned in the KB, but it seems the error ultimately comes back.

 So do I just give up and work locally?  Is that the convention?

 thanks,
 jeff

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.