• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 407
  • Last Modified:

Error when rebuilding Visual Studio 2005 project on a network server

Hello,

I have a Visual Studio 2005 (in Visual SourceSafe) project that rebuilds with no errors on my local computer.  I just recently moved this Visual Studio 2005 project to a network drive (along with changing the new working folder in Visual SourceSafe).  As soon as I did this, I attempted to rebuild the project (from my local machine) and received the following error:

An error occurred loading a configuration file: Failed to start monitoring changes to 'H:\OCCUPANCY\tempreports' because the network BIOS command limit has been reached. For more information

I have given the Network Service user Read & Execute, List Contents and Read permissions on my network soucecode directory but to no avail

Reading the related Microsoft Knowledge Base article (http://support.microsoft.com/kb/810886), it said that it was a registry issue (I do not like to have to mess with they registry unless I absolutely need to).  Is their any truth to this or is their a different resolution?

Any Ideas???

Please let me know
Thanks
0
mrsdev
Asked:
mrsdev
  • 3
  • 2
  • 2
1 Solution
 
VBRocksCommented:
I've never found a solution to this problem.  I always copy the solution to my computer, modify it, then copy it back to the server.
0
 
Bob LearnedCommented:
I would also like to be so bold to suggest that network locations are not a very good practice, and that the best practice in this case is to use some kind of source control (SourceSafe, SVN, Team Foundation Server), and work locally.
0
 
mrsdevAuthor Commented:
Hello,

Thanks for the responses.

We are currently working locally using Visual SourceSafe.  Management didn't like this approach since we, at times, have things checked out for awhile.  If the hard drive crashes (which has happened in the past), we lose our work that we had checked out.

What I was going to suggest was creating a Task Scheduler (or WinCron) job that runs once a night and copies my local sourcecode out to a network server that is getting backed up.

Is this the best solution to this issue?  What do you think?

Please let me know
Thanks
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
VBRocksCommented:
A nightly backup is a great idea.

We have to have a copy of the source maintained on the server, because of SAS requirements, source control, and backups.



0
 
mrsdevAuthor Commented:
Thanks for the replies.

I am assuming, safely (from the responses given), that I will go with my own solution (my last comment):  to create a Task Scheduler (or WinCron) job that runs once a night and copy my local sourcecode out to a network server that is getting backed up.

Who should the points go to?


Please let me know
Thanks
0
 
Bob LearnedCommented:
Points to VBRocks...
0
 
mrsdevAuthor Commented:
Thanks again.

"That if we confess with our mouth the LORD JESUS and believe in our hearts that GOD raised the LORD JESUS from the dead, thou shalt be saved."  Romans chapter 10, verse 9
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now