An error occurred registering project with source control

projectthunder · Post by **projectthunder** » Thu Feb 03, 2005 1:11 pm

Dear Support,

The computer that sets up the project in to the vault has no issue with it at all. When we try to pull down a C# project from the vault version 3.02 we get the following error.
________________________________________________________
The project "ThunderECF" is under source control. An error occurred registering this project with source control. It is recommended that you do not make any changes to this project.
________________________________________________________

After the error it will pull down just the csproj file but nothing else. Then we can pull down the files using the vault client but VS will just prompt with "Access error" and it will never acknowledge the files are there.

dan · Post by **dan** » Thu Feb 03, 2005 1:54 pm

Try unbinding the project and then rebinding it and see if that helps

projectthunder · Post by **projectthunder** » Thu Feb 03, 2005 2:01 pm

We have tried that already, it didn't work because we are getting the same error messages.

dan · Post by **dan** » Thu Feb 03, 2005 2:40 pm

Did you do an Open from Source Control from withing Visual Studio, or do a Get from the Vault GUI client? Note that you have to first do an Open From Source Control one time from VS in order to use integration (after that Gets from either Vault client will work).

projectthunder · Post by **projectthunder** » Thu Feb 03, 2005 3:17 pm

dan wrote:Did you do an Open from Source Control from withing Visual Studio, or do a Get from the Vault GUI client? Note that you have to first do an Open From Source Control one time from VS in order to use integration (after that Gets from either Vault client will work).

This is happening on more than one computer. It does not happen on the computer where the project was established in to source control. We added the project in to the VS solution via the source control menu "Add Project from Source Control". We have in addition tried Get Latest from the vault client and then rebinding it will work for a second or a couple attemps then goes back to "access failure".

This process has worked fine for several months. However recently it has been a anomoly that has gotten worse and worse with the final error just being "Access Failure". We upgraded to the 3.0.2 the other day and still have the same issue.

Thanks!

dan · Post by **dan** » Thu Feb 03, 2005 3:43 pm

Did Open From Source Control make any difference?

You might also turn on logging and see if that reveals anything. See http://support.sourcegear.com/viewtopic.php?t=2898 and http://support.sourcegear.com/viewtopic.php?p=5375 for the two different kinds of logging you can do with the IDE client.

Also, are these machines set up to have Vault as the default provider? You can verify that from the Vault GUI client Tools->Options

projectthunder · Post by **projectthunder** » Thu Feb 03, 2005 4:36 pm

dan wrote:Did Open From Source Control make any difference?

You might also turn on logging and see if that reveals anything. See http://support.sourcegear.com/viewtopic.php?t=2898 and http://support.sourcegear.com/viewtopic.php?p=5375 for the two different kinds of logging you can do with the IDE client.

Also, are these machines set up to have Vault as the default provider? You can verify that from the Vault GUI client Tools->Options

"Open From Source Control" did not make a difference, we are still getting the error "Access Failure" when are trying to Get the latest version in VS.
I've created four logs for four different classes, I am attaching these text files in this post, each file is named accordingly with the class it was logging.

dan · Post by **dan** » Thu Feb 03, 2005 5:07 pm

OK, that did not reveal much. Try the log file at http://support.sourcegear.com/viewtopic.php?t=2898 and copy it off when the Access failure happens so we know exactly what function it is in.

Also, does the Output window in Visual Studio say anything useful. Sometimes in Access errors, Vault is trying to overwrite a DLL that was placed in SCC, but is in use by a program, often a web service that hangs onto it longer than it should.

projectthunder · Post by **projectthunder** » Thu Feb 03, 2005 6:15 pm

dan wrote:OK, that did not reveal much. Try the log file at http://support.sourcegear.com/viewtopic.php?t=2898 and copy it off when the Access failure happens so we know exactly what function it is in.

Also, does the Output window in Visual Studio say anything useful. Sometimes in Access errors, Vault is trying to overwrite a DLL that was placed in SCC, but is in use by a program, often a web service that hangs onto it longer than it should.

The output window in VS only says "Operation started at time 4:10:54 PM" and "Operation terminated with error at time 4:10:54 PM" but here is that log file that you've asked for...

dan · Post by **dan** » Fri Feb 04, 2005 8:10 am

After the re-bind is the error message still the one about registration errors, or is it something else? Can you post a screen shot?

The logs are not revealing much info. We will have to add some additional log messages and have you run a special build. Email me using the email below and we can get that out to you.

projectthunder · Post by **projectthunder** » Mon Feb 07, 2005 12:07 pm

dan wrote:After the re-bind is the error message still the one about registration errors, or is it something else? Can you post a screen shot?

The logs are not revealing much info. We will have to add some additional log messages and have you run a special build. Email me using the email below and we can get that out to you.

Vault cannot find the parent folder of the file NavBar_Support.js in the
client side cache. Can you locate that file in the tree? I'd like to find
out if it really is missing, or whether it is something else.

We have removed the entire folder containing the file NavBar_Support.js from the project and after that I was able to pull the project down from the vault into VS on my computer with no error messages and everything is working fine now. Thank you for your assistance.

dan · Post by **dan** » Mon Feb 07, 2005 12:41 pm

Yes, it looks like the problem was that a file was included in the VS project and VS thought it was under source control, but it did not actually exist in Vault. We'll need to have a better error message about this in the future.