Sometimes when I try to do check-in to TFS, I get the following message:
And the check-in fails.
Searching the Internet for this, it seems to be E_UNEXPECTED, or if it uses COM it also could mean "Catastrophic failure".
But I predictably found no solution for this, as the error message is doing very poorly its job of giving information on what is happening.
How can I make this will not happen again?
You can remove this error by upgrading to a newer version of visual studio and TFS. TFS and Visual Studio 2010 fall out of mainstream support in a couple of months. You need to start your upgrade planning now!
http://nakedalm.com/blog/its-that-time-again-get-ready-to-upgrade-to-tfs-2015/
Due to you still being on 2010 after all this time, I would recommend moving to Visual Studio Online rather than trying to run TFS internally.
Related
We are using XAML builds in TFS 2015.
In the team explorer, builds tab in Visual Studio 2017 (but still connecting to the TFS 2015 server) all of a sudden I am seeing the following 'Page not found' message and none of my XAML builds appear:
This happened after removing a TFS 2015 connection, then connecting to a TFS 2017 instance, then deleting the 2017 connection and then re-connecting to to the previous TFS 2015 instance.
I have tried
Clearing the MEFComponentCache folder
Running devenv /setup
Completely uninstalling and re-installing VS2017
... and I'm still getting this error each time I connect to my TFS server. I also have VS2015 installed and this does show the builds but 2017 does not. A lot of the other posts on this issue seem to related to VS2015 but not 2017. I'm guessing something has changed here. Does anyone know why this is happening and how to fix it please?
I'm new with TFS, but it is possible, that Visual Studio 2017 has added some files, like setting-files on your system and if you delete VS17 the files will not be deleted.
I think you can try two options:
You can remove VS17 again and run a programm to clean up your PC, like this clean up tool. After that you can install VS17 again and check, whether the problem is solved.
You can upgrade your TFS15 instance to TFS17. See this or this link for more informations.
Attention, I'm new with that, it is only an idea and make BACKUPS!! ;)
We are receiving an unexpected error when using our VBScript external debugging tool. We used this link in the past to create the external tool:
Visual Studio 2013 and VB Scripts
It has worked fine in VS2013 when we created the tool. Well, we moved to a new machine and now this tool will not work. We receive the following error asking us to register the PDM.dll or it is missing, which we have done. I'm assuming it is a configuration issue of some sort either in the Visual Studio 2013 or elsewhere. Would anyone have experience with this or could offer a suggestion?
Error:
"The script debugger failed to connect to the target process. The correct version of pdm.dll is not registered. ...."
I know this is common error but we have tried the common fixes that we are ware of.
Thanks!
When I loaded VS 2012 (with VS 2013 still installed), somehow it fixed the issue. Both 2012 and 2013 can debug VBScripts with use of the External Tool created for VBScript debugging. We had this issue before in the past, on the previous machine (i.e. PC), it was just the opposite fix. VS 2012 wouldn't debug VBScripts with the External Tool created, but after loading VS 2013 it worked. Somehow, the second installation changes the configuration which impacts both versions, resulting in the VBscript target connection to work.
Recently started using Visual Studio 2012, converting SSIS packages from 2008, and seem to be unable to set breakpoints in Script Tasks. The error we're receiving says
Cannot start debugging. Pre-debugging negotiations with Host failed.
Cannot seem to find any information about this error, or what's causing it. There is also a brief flash of a dialog box that says
Visual Studio has encountered an unexpected error
but that disappears quickly.
This issue has been resolved. The input parameters were set incorrect and hence was failing. It has been fixed now
I think you install new version of Visual Studio you just have to uninstall the Visual Studio tools for Application for the new version then repair the Visual Studio tool for Application 2012 and every thinks will be good
For some reason I cannot check in my code to our Visual Studio Online account. Other developers can, but not me. This is the error I am getting:
"Could not find dataspace with category VersionControl and identifier [some guid]"
Searching for any help on the above error is not returning anything meaningful.
This started to happen after I installed Visual Studio 2015 Enterprise. I launched it for the first time after creating a new web application with Visual Studio 2013. I then opened that new solution in 2015 and all was fine. Things began to go awry once I tried to put it in our Visual Studio Online account. When I went to Team Explorer in VS 2015 I selected "Projects and My Teams / New Team Project". This then bounced me over to our Visual Studio Online account in the browser for me to fill out that simple form to create a new team project. I filled the form out and submitted. I then got an error that the project was not successfully created. Unfortunately Visual Studio still thinks it was created and it shows up in the list of projects ONLY WITHIN Visual Studio -- it does not show up online. Eventually I just became frustrated and deleted everything related to all that I just tried but then learned that I cannot check anything in now on my old projects! I had other developers test and they still can so the problem evidently is on my machine. I then uninstalled VS 2013 and VS 2015 then reinstalled VS 2013 and am still having the problem.
I am hoping someone can point me to some cached junk that needs to be cleared on my system. :-)
This is a bit shot in the dark, few things you can try:
Delete the local cache under:
%localappdata%\Microsoft\Team Foundation
%localappdata%\Microsoft\VisualStudio\14.0\SyncSettings
Open cmd. Type:
"%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\Common7\Tools\vsvars32.bat"
Verify connections: tf settings connections
Run Visual Studio in safe mode (devenv.exe /SafeMode)
Run Visual Studio with activity log (devenv.exe /log) and check for errors.
I have the problem that Visual Studio 2013 crashes when I lock the computer or start another instance of Visual Studio.
I use Visual Studio 2013 with latest patches applied. I always start Visual Studio as Admin.
This seems to only happen with a certain big solution. This problem did not occur to me with other solutions.
I tried to delete the solution and make a clean checkout from TFS, but Visual Studio still crashes.
I know this is not much information, but do you have any idea how to fix this or how to what else I could check?
Additional Information: This still happens even with Visual Studio 2015 on a fresh Windows 8.1 installation...
Here's the error:
Use the following steps to solve the issue:
Source: http://resharper-support.jetbrains.com/entries/24765142-Visual-Studio-with-ReSharper-is-freezing-and-or-crashing
I would copy the solution with quotation but as you can see, there is a lot of text to edit.
Start Visual Studio using the /log switch. Then check the created log file for warnings and errors:
%APPDATA%\Microsoft\VisualStudio\11.0\ActivityLog.xml
If you use a Web Browser to view the file, it will be nicely formatted, due to the accompanying xsl-sheet.