Unspecified Error in VS.Net

tomcat2001 · Post by **tomcat2001** » Wed Aug 24, 2005 10:56 am

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.

dan · Post by **dan** » Wed Aug 24, 2005 12:36 pm

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.

tomcat2001 · Post by **tomcat2001** » Wed Aug 24, 2005 1:04 pm

I enabled the logging but I don't see anything useful in it. Maybe you can. I enabled all logging.

dan · Post by **dan** » Wed Aug 24, 2005 1:19 pm

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?

tomcat2001 · Post by **tomcat2001** » Wed Aug 24, 2005 1:34 pm

Here's the log I had from doing the registry part. I actually had it, but didn't attach it. I'll try and do this from another computer also.

tomcat2001 · Post by **tomcat2001** » Wed Aug 24, 2005 1:36 pm

Here's the attachment try again. Guess it didn't like the .log extension.

tomcat2001 · Post by **tomcat2001** » Wed Aug 24, 2005 1:47 pm

I tried this on some other developers computer with the same result. I removed his root working folder and then tried doing this with the same result. Then he attempted to do the same, and he has the same result.

dan · Post by **dan** » Wed Aug 24, 2005 1:58 pm

OK, we'll need a little more history about this solution:

1. What version of Vault are you using?

2. Was it working before and now isn't?

3. What has changed in the solution or project since it last worked?

4. Any configuration changes to the clients or servers since t last worked?

tomcat2001 · Post by **tomcat2001** » Wed Aug 24, 2005 2:13 pm

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.