We recently started getting "The handle is invalid" errors in VS.NET 2003 when we do a get latest on the solution--but not individual projects, only on the whole solution.
We deterimed the problem to be that we added links to the application log files within the "Solution Items" folder. These files were not in vault--everyone has the same files in the same location, we only wanted them to show up in the solution for easy eaccess.
With these links there, we get the error:
Title: Microsoft Development Environment
Text: The handle is invalid
When we removed the links, the error went away (of course we'd rather have the files as a part of the solution).
At a previous job I'm pretty sure I did the same thing (added files not under source control) using VSS and did't have a problem. Perhaps VSS was forgiving of VS.NET doing something it shouldn't (maybe VS.NET is requesting files it should know are not under source control).
Thanks,
Sam
"The handle is invalid" errors from VS.NET
Moderator: SourceGear
Invalid handle error
I added the files to the solution itself as a solution item.
1. Right-click on the solution and choose Add > Add Existing Item..
2. Choose a file that it outside the solution root
3. Get notice from VS.NET that file will not be placed in source control (fine, that's what we want)
4. Check in solution.
5. Get latest on solution.
6. Get handle is invalid errors.
As far as I remember the same procedure did not produce any errors when using VSS server/client.
Thanks,
Sam
1. Right-click on the solution and choose Add > Add Existing Item..
2. Choose a file that it outside the solution root
3. Get notice from VS.NET that file will not be placed in source control (fine, that's what we want)
4. Check in solution.
5. Get latest on solution.
6. Get handle is invalid errors.
As far as I remember the same procedure did not produce any errors when using VSS server/client.
Thanks,
Sam
I just tried this on a simple test solution in VS 2003 and Vault 3.1 beta. I got the error that it couldn't add to SCC, but not the handle error.
Can you try this with a simple solution and see if it fails in the same way? There might be something about the config of the solution you are using that is causing the problem.
Can you try this with a simple solution and see if it fails in the same way? There might be something about the config of the solution you are using that is causing the problem.