Unspecified Error in VS.Net
Moderator: SourceGear
-
- Posts: 22
- Joined: Fri Feb 20, 2004 10:35 am
Unspecified Error in VS.Net
I'm trying to do a "Open From Source Control" in VS.Net 2003. I have to login to vault (when it should auto-login like everywhere else) and then I specify the folder. Immediately I receive the error "Unspecified Error". Any help on this is appreciated, since I can't figure out why it would do this. The directory is actually non-existent because I was wanting to get a clean structure of the source.
Does the output window have anything useful in it?
If not, turn on IDE logging at http://support.sourcegear.com/viewtopic.php?t=2898 and see if it has anything useful in it.
If not, turn on IDE logging at http://support.sourcegear.com/viewtopic.php?t=2898 and see if it has anything useful in it.
-
- Posts: 22
- Joined: Fri Feb 20, 2004 10:35 am
I enabled the logging but I don't see anything useful in it. Maybe you can. I enabled all logging.
- Attachments
-
- VaultIDEClient.zip
- Log file zipped up
- (15.65 KiB) Downloaded 744 times
This looks like the normal client log, not the IDE log. Take a look at http://support.sourcegear.com/viewtopic.php?t=2898 again and create the registry entry to create an IDE-specific log.
Also, if you try to open the project from a different machine (but same Vault user), do you get the same results?
Also, if you try to open the project from a different machine (but same Vault user), do you get the same results?
-
- Posts: 22
- Joined: Fri Feb 20, 2004 10:35 am
-
- Posts: 22
- Joined: Fri Feb 20, 2004 10:35 am
Here's the attachment try again. Guess it didn't like the .log extension.
- Attachments
-
- VaultLog.txt
- Vault Log
- (2.11 KiB) Downloaded 692 times
-
- Posts: 22
- Joined: Fri Feb 20, 2004 10:35 am
-
- Posts: 22
- Joined: Fri Feb 20, 2004 10:35 am
I think I may have found the problem. We used to have a project and solution in the same folder. We moved the project out, but there was an extra file in the solution directory called xyz.vsscc that was blank. This was in addition to our xyz.vssscc. Once I removed that from the directory it worked fine.