I had branched out from our QA branch on TFS, mapped it locally and tried making changes to the code locally. When trying to save my code changes, it gives me a warning saying that " the file is write-protected(read only). This has never happened before to me. We tried doing the same thing on my teammates workstation and it works fine for him.
Is it a permissions issue....am I doing something wrong while branching out? I am connected to the right tfs server. I'm not sure what might be causing the files in the branch to be read only.
I'd highly appreciate your help on this.
Thanks
The reason could be that your solution went offline.
What you can try is connect to your main TFS server, Load the solution then just goto File->SourceControl->go online.
Hope this will solve your problem as it solved mine.. :-)
Sorry guys...I'm going to have to answer my own question.
It was the connection to our main tfs server. I connected to the backup tfs server and it works just fine. However, what is baffling is that my teammates can work with the main tfs server just fine.Only I can't.Still puzzled.
Related
I am trying to branch a directory in TFS using the Source Control explorer, however whenever I do, I always get this error:
TF400962: There was a database update error. Please try your operation again.
This occurs after confirming I would like to branch after it informs me that it will be committed as a single operation, pending changes will not be created and that it cannot be canceled when it is started.
I have been stuck on this for a while now and I can't seem to find any solution to this, here is a list of things I have tried.
Made sure the Target Branch Name is below 255 characters (As suggested here). I also made sure the whole path on my machine was also less than 255 characters.
Changed workspaces.
Updated Visual Studio to the latest version.
Restarted Visual Studio.
Restarted my machine.
Branched another directory (To see if the directory I need to branch isn't throwing the error).
Made sure connection to the TFS server was correct.
Checked that I had the correct settings in the workspace.
Downloaded the directory I am trying to branch to my PC.
I have ran out of ideas and it really is frustrating me. Any help would be appreciated. I'm using Visual Studio 2017 Enterprise now running on the latest updates.
Check if you had a deleted branch in the path you are trying to branch to.
Steps to reproduce:
Have code at $/path/to/main
Branch from $/path/to/main to $/another/path/dev
Delete $/another/path/dev
Try to branch from $/path/to/main to $/another/path/dev/branch
-> TF400962
Problem seems to be that $/another/path/dev/branch overlaps with deleted branch $/another/path/dev
Resolution:
Show deleted elements in TFS Explorer
Convert deleted branch $/another/path/dev/branch to regular folder
Branch from $/path/to/main to $/another/path/dev/branch
-> Success!
The error you are getting a generic error that could happen because of any TFS SQL Server related issue. Please check events logs on your TFS's SQL server machine. You might find more information there.
There is more information here
https://connect.microsoft.com/VisualStudio/feedback/details/1128642/tf400962-there-was-a-database-update-error-please-try-your-operation-again
Make sure your TFS DB is not out of disk space.
I'm pretty new to programming, and I'm having an incredibly difficult time making GitHub and Visual Studio Community 2015 play nice with each other. Usually the first commit goes well, and I can see it on GitHub.com just fine. But it never lets me make any more commits. I make changes to the file, save it, but the commit button in VS stays grayed out. I've been all over the Team Explorer to figure out what I'm doing wrong, and I can't figure it out. It says I have no unpublished changes or anything, even though I'm changing tons of things in the file.
Is there any reason it would stop working after the first commit?
Close VS
Open the particular .sln file from the repo
This worked for me.
You would need to add your username and email in you global configuration. Then you will be able to see the commit button enabled.
I had to add username and mail in VS to activate the commit button. The visual studio message telling me to add the data only appeared after a restart of VS. Maybe this will help someone else.
Try to use git push on git shell, the console will tell you if there are any errors, and give you searchable errors.
I think I figured it out, and as predicted, I'm an idiot. I was accidentally saving the files OUTSIDE the local repo folder. If anyone else has this problem, make sure you are saving things in the right places. Also, cloning the remote repo instead of trying to create two in each place helped a lot.
If you have a local database file, then you will not be able to copy/move the database file, and so any change in the solution cannot be committed. You have either to close the database service, close the connection inside the application or to close the solution and do the commit.
I have this issue with Xcode 5 where I'm trying to commit a file to a remote git repository (BitBucket) and getting a pop up window with the following error: "The repository "project_name" could not be reached. Please verify that the repository is online and reachable and try again."
I've been working with this setup for awhile now (since Xcode 4) and didn't have any problems with it. Under Xcode->Preferences->Accounts->Repositories I saw the correct repository, but duplicated. I deleted and added it again, but it didn't help. I tried closing the project and rebooting the computer and it didn't help either. I can see the project's history under Source Control->History. I can access the repository on BitBucket.
Any idea where this is coming from and how to solve this issue?
Not sure if this helps in the tracking down of this problem, but here goes anyway:
I have been connecting to a local network git repository perfectly well for a number of months, but I encountered this problem later yesterday and nothing I did seemed to improve the situation. That included:
Rebooting both the development machine and the server;
Reinstalling Xcode from the App Store;
Re-cloning the project from the git command line (which could see the repository perfectly well);
Checking out the repository from Xcode (I was able to check out but every other operation, such as , Commit, Refresh Status etc. seemed to cause the problem...)
Manipulation the repository with SourceTree (which could also see it fine).
Eventually I stumbled across a solution to my local issue. If I launch Xcode with a wired and wireless network enabled then I can't see the repository. If I close it, disable wifi and relaunch it then I can.
I've not had much opportunity to work out what the difference is (especially as the wifi connects to the same network and is the secondary choice for networking) but it does seem to fix it.
Hope that might help others and hopefully I can find a real explanation soon!
Dave,
Well it seems this had nothing to do with Bitbucket.
The problem was a messed up .git folder on my machine.
My project resides in a Dropbox folder. Somehow, perhaps because of accessing it from different machines, it created copy/duplicate files in the .git folder and it messed up Git. After fixing all the conflicts Git returned to working as usual and I was able to commit from Xcode to the remote repository.
Now, if you encounter this issue, you might not have the same setup as mine or work on Dropbox or any similar service, but I strongly recommend checking your Git folder thoroughly. Good chance something is messed up there.
Check internet connection of system.also quit xcode and reopen it.
I have a developer in another country who is accessing svn from there.
Now we had an issue with the firewall, and he could not access the repository for a while. The firewall error should be fixed now, and it works again for others. This devs gets the error "Error:access to '/svn/path/lots-of-numbers' forbidden" though.
When I tried to find the cause, I found this: link to similar case
However, he sent me the repository link he uses, and it is all in lower case, just as it should be. The permissions are also correct, I just double checked them.
Could the problem lie in the firewall somehow, or does anyone have another suggestion?
Figured it out some time ago, but I guess I should post this here too in case someone else has a similar issue. My problem was actually with permission settings.
What I have now that works, are the exact same settings I had in the svn server previously, only now they are inherited from the root. Sooo...yeah. I have no idea why that actually made a difference.
I've had the same issue for a while and figured out what was wrong. I had a capital where I shouldn't have. My repository was svn/dave, but i had it in the URL as svn/Dave. It let me log in without any issues, but I couldn't actually do anything. Changing it to lower case cleared everything up.
I faced similar situation and I also had changed the permission in the server to inherit from the root.
My problem got solved after I issued the command svn update
Usually it is a practice that I always follow - I run svn status . and then svn update . before firing svn commit.
I skipped svn update this time and caught the error.
It looks like svn update does much more than just update the files.
I made some changes to my website, then had to reformat my server, and over two weeks I tried to undo what I did (it was a stupid forum thingy). Obviously I missed something, becuase now I have the dreaded Build Failed With No Error problem.
This is my home server, so no I am not running source control.
After staring at it for a few days, I decided to try somehting. Today I allowed VS to run the last successful build, and it still works.
QUESTION: How can I go back to the last successful build? I don't care about any changes made since it worked. That's really all I need.
THANKS
Have you checked to see if you have Previous Versions available?
It sounds like you won't likely be able to recover the source files / project config, though you could certainly attempt to recover the "source" by using tools like ILSpy or .NET Reflector. You can use them to examine the output assemblies, and reconstruct your code if necessary.
As a lesson learned, both Mercurial and Git work wonderfully for versioning home projects - I'd give a slight nod to Mercurial in your case as it works just a tad bit easier on the Windows platform.