This error just started happening this morning in one particular project. When I try to publish the site it gives me this error and I can't complete the publish! Sometimes restarting Visual Studio magically fixes the problem, but it will just appear again later. Not only that, when I restart VS I lose all my "undo capabilities".
There is a KB article on the subject, but it did not help.
What can I do to stop this very annoying problem once and for all?
Network administrator advised me to run my solutions from the C: of my local development machine. Had to create a batch file to manually copy the source code files over to the network drive throughout the day (so that they get backed up).
Building your solution on C:\ doesn't really solve the issue, it just avoids it. True, that is a good work around, but you still can't build from a shared drive. I faced this same issue in VS and was able to overcome it without moving things locally. Here's what I did:
The Microsoft KB article more or less gets you in the right direction:
http://support.microsoft.com/kb/810886
Be sure to refer to it because the registry keys it tells you to adjust are correct.
On your local machine, either adjust the MaxCmds and MaxMpxCt like the article says, or add them. When I went to check, those values did not exist for me so I had to create them. If you do add them, choose NEW -> DWORD value. After it's created, then double click on the item to adjust the value. Make sure when you edit the DWORD value that you click on the Decimal base and don't use the Hexadecimal base. I put 500 for both MaxCmds and MaxMpxCt. Then restart.
Next, go to your share server and then do the exact same thing. Restart.
The range of values for these registry entries is between 0 and 65535, so you might need to adjust accordingly, but for me 500 worked.
One last thing... backing up your registry never hurts.. ;)
I made the reg changes locally as you described. When you say 'shared server' I guess you are talking about a drive on another networked windows machine. I'm trying with a local drive, so there is no 'shared server' to modify. No change to the error message. Oh well.