Checkout File and AutoMerge Always Gives a Generic Error - visual-studio-2010

I'm using TFS 2010. Every single time I try and do a "Checkout File And AutoMerge", I get the following generic error message:
Error
The following exception was encountered. NAMEOFFILE cannot be merged.
Please retry with another resolution option.
This doesn't tell me anything about why or how to resolve it. This is very frustrating because I cannot automerge anything and TFS doesn't give me a manual merge option either. Never thought I'd miss SVN so much. Any ideas how to resolve this?

Related

What is fatal error C1090: PDB API call failed, error code '3': vc142.pdb?

I set up a new project with Visual Studio 2019 version 16.3.10. When I try to build I get the following error:
EasyTcpStubs.c : fatal error C1090: PDB API call failed, error code '3':
W:\Dropbox\Me (Mine)\TcpToNamedPipe\TcpToNamedPipe\Debug\vc142.pdb
I have searched the internet and this site for any explanation of this error. Maybe I missed it but I could not find anything.
The project is a Console project.
The error occurs without a line number so it does not seem to be the source. I tried another project and it compiles OK (but it is an old project whereas this error is occuring on a brand new project.
Does anyone know something about this?
For me, I stopped Dropbox and it works. It seems that something is using W:\Dropbox\Me (Mine)\TcpToNamedPipe\TcpToNamedPipe\Debug.
In my experience this error is likely due to some permission error. If your project is in Dropbox, OneDrive, etc, most likely you get this error because your Dropbox cannot sync and update files properly. Restart Dropbox and that should fix the issue.
In My case, I suspect it is some type of race condition/lock issue with the code that opens/closes the *.pdb file. In my case I am running /MP (Multiprocessor Compile) so up to 4 *.cpp modules being built at a time. It works fine on a stand alone build machine. But I'm a vendor and must use a VM environment to develop for my customer, and the disk requirements are so large I must place the builds on a network share.
The latency of file I/O access over a network share seems to be the issue.
Thats all I know about the issue at the moment.
As I learn/test discover more, I can improve this answer.
Synology Drive Client (v3.2.0) caused this error for me. Pausing the sync eliminated the error. Thanks to all for the clue of DropBox, OneDrive, etc. causing the issue.

Can't launch Visual Studio Addin example Woodgrove Expenses

I am getting into Excel office add-in dev and trying to get the Woodgrove example (https://github.com/OfficeDev/Excel-Add-in-WoodGrove-Expense-Trends) up and running. Unfortunately, it gives an error when I launch it.
Unhandled exception at line 1, column 1 in https::/localhost:App/Home/Functions.js
.... - Javascript runtime error: 'args' is undefined
Any ideas whether I am missing a setting?
There's a typo in that file. On the very first line, delete the string "args".
In the meantime, I will fix the sample.
Update 3/2/18: You're correct, there was a lot more corruption in that file than just that typo on the first line. I think I found it all and pushed the new version of the file to the repo. It works for me now. If you do a pull now, you should get an uncorrupted version. See if it works for you now.

Team Explorer for VS 2013 - can't check in

I have an existing solution that has previously had no problems. I added two new projects to the solution, completing my dev work with no problem, however when I try to check the solution in I get an error similar to the following:
C:\Project1Path\Project1.csproj: Download of item $/Project1/Project1/Project1.csproj was not completed. Perform a get operation to correct.
I get the same when I try to check in just this project. I have not tried checking in the other new project yet as ideally I want to check everything in together.
I did a Get Latest on the solution on the outside chance that that was what the error was telling me to do but to no avail.
Any help appreciated as sooner or later someone else is going to want to work on the solution.
Many thanks
Simon
I had this issue and when I ran get latest in source control it picked up a non version controlled file with the same name and asked to overwrite it.
If you get that conflict make sure you overwrite the local file.
If you don't get a conflict maybe delete local file manually and then get latest.
I'm not sure that'll work but you could try.
If this isn't resolved with a get latest, go to the actual file in team explorer. If it has a small diagonal icon next to it then right click to resolve the conflict manually. Here you can override the changes.
This is here for anyone else who may run into the problem.
In my case the file was deleted in the TFS. Undo pending changes for this file (undelete it) then try to check in again.
Note: you cannot tell if the file is delete just by looking at solution explorer.
It happened to me as well when I tried to checkin the code from TRUNK after merging from feature branch.
What I did is rolling back the change from TRUNK and merging it again.

Random access is denied errors in Visual Studio/TFS

I keep getting "access is denied" errors in Visual Studio when I run "get latest", or I try and check in code, or something like that. It seems to happen about 75% of the time, but if I try again a second time the error goes away and the operation works. I am using Visual Studio 2013. Any ideas on how to fix this?
In my situation, I could check-in files, but for some reason when I performed a "Get Latest" action, I got access denied ...
The solution was to create a new workspace. I guess there is some corruption on the workspace, but I'm not sure where this may have occurred, or whether there is a configuration type file for workspaces?
It sounds like you have a faulty proxy between you and the TFS server that is dropping your credentials. You should try connecting without the proxy...

Visual studio error list shows empty results list

After fixing errors and rebuilding the error list window still has empty placeholders and a count of zero errors.
This only goes away after restarting VS
It seems random, some days I dont get the problem at all with the same solution
Trying to open one of the empty errors by clicking on it gives me a "Visual studio has encountered an unexpected error." message.
Its driving me crazy. Cant find any help out there or other people reporting the same problem
VS gets crazy many times.
Make sure your version is up-to-date,
Delete your automatically generated .suo file(s) (resides near the solution file)
Still bad? there might be a corruption or invalidity in a XML file it tries to read or something like that.
Try removing temporary files and generated files. Look at this:
https://www.google.com/?q=visual%20studio%20temp%20files%20location#q=visual+studio+temp+files+location]
You can try using VS Command line switches like /Log and /Out. Further more - Add switches to the MSBuild command in your project configuration. Here is the references:
http://msdn.microsoft.com/en-us/library/xee0c8y7.aspx
http://msdn.microsoft.com/en-us/library/ms164311.aspx
Try using SysInternals ProcessMonitor to see What file is opened just before the error occurs.
Nothing helped? Reinstall VS completely. do a full Uninstall. I suggest you backup your preferences and tools beforehand. You can do this manually or by signing in to VS with your live ID.
http://msdn.microsoft.com/en-us/library/dn457348.aspx
Be aware - your extensions should be re-downloaded. and one of them might be the cause for all this suffering
Maybe this does the trick, update VisualSVN:
https://www.visualsvn.com/visualsvn/download/
To debug this, you can use this solution: https://stackoverflow.com/a/9589139/61883
solved it by:
Open two instances of Visual Studio. Open the same project in both.
In one instance, goto Debug->Exceptions and enable all the 'Thrown' options to stop at first chance exceptions. This will stop the debugger when the exception is generated.
In the same instance, select Debug->Attach to Process, select devenv.exe.
In the other instance, open the form to cause the exception
With any luck the first instance should stop somewhere that yields a more relevant exception.

Resources