We used to have a great time with our TFS 2010 installation, but all of a sudden it seems to stab us in the back.
When we try to create a new Team Project (either via VS2010 or VS2012 Team Explorer), TFS encounters an error when importing the Process Templates. It doesn't matter which of the installed Templates i select, the error is always the same.
2013-01-16T11:11:08 | Modul: Work Item Tracking | Thread: 39 | Uploading task type from file "C:\Users\user1\AppData\Local\Temp\TPW_tmp447E.tmp\WorkItem Tracking\TypeDefinitions\Bug.xml" hochgeladen...
---Begin Exception---
Zeit: 2013-01-16T11:11:08
Modul: Engine
Exception Description: TF30162: Error at Task "WITs" from Group "WorkItemTracking".
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: TF24016: Team project "MyInfoservice" not found.
Stacktrace:
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.Execute(ProjectCreationContext ctxt, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
bei Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
-- Inner Exception --
Ausnahmemeldung: TF24016: Team project "MyInfoservice" not found. (Type WitPcwFatalException)
Ausnahmestapelüberwachung: at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.ContextWrapper.get_Project()
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.WitPcwTask.WorkItemTypesTask.UploadTypeDefinition(String file, Boolean execute)
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.WitPcwTask.WorkItemTypesTask.Execute()
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.Parse(ContextWrapper wrapper, XmlNode taskXml, Boolean fExecute)
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.Execute(ProjectCreationContext ctxt, XmlNode taskXml)
---End Exception---
EDIT : My colleague just found out that this doesn't occur on any other machines, so it must be our Visual Studio instances that are messed up.
So why are they messed up? We caused a desaster by making attempts at desaster recovery (What happens if we have just the database dump of our TFS Collection?). What we've done, in short:
Make a backup of TFS Database (without detaching it from the TFS)
Create a second Server and reattach the database there
Run TfsConfig Recover on the DataBase
At first sight, the result seemed to be OK, but at a closer look, many problems surfaced. I guess they go back to the fact that visual studio connected to two servers with the same project- and collection GUIDs, but that's just a guess. Now we're trying to get our machines back to work the way they did when only one TFS was being connected to.
Tried but not working:
devenv resetsettings
deleting all VisualStudio and TeamFoundation folders below C:\users\user1\AppData\Local and Roaming
deleting registry keys that contain the TFS server names
Can anyone point me in the right direction what else we can try?
After a few more or less desperate attempts I was finally able to solve this.
Since the exception occured when a file from my local Temp folder was uploaded to TFS, I tried clearing the entire TEMP folder. That did the trick. The relevant information is the first line of the log output I posted above.
Uploading task type from file "C:\Users\user1\AppData\Local\Temp\TPW_tmp447E.tmp\WorkItemTracking\TypeDefinitions\Bug.xml"
I had a similar problem after restoring a TFS 2012 Express collection from backup. I resolved it by deleting the TFS cache on the local dev. machine. I just removed the entire Cache folder...
C:\Users\myUsername\AppData\Local\Microsoft\Team Foundation\5.0\Cache
If you have another dev. machine handy then you can check if you can create a TFS project on it. If you can then the problem is with your dev. machine, most likely the cache.
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.
No matter what I do, when I touch TFS in any way, it gives me the error:
TF400030: The local data store is currently in use by another operation. Please wait and then try your operation again. If this error persists, restart the application.
Well not everything, I can see a list of workspaces (all 1 of them). But trying to view the workspace in the source control explorer will only show "Working..." Pending changes can only show me there are 654 included changes (a migration, don't judge), but none of the actual changed files and strangely none of the excluded changes.
I tried to nuke this workspace and rebuild it from scratch. But even using tf.exe workspace /delete ..., right after a fresh reboot, will give me the above error.
I tried deleting all VS / TFS related folders from AppData\Local\Microsoft and running devenv.exe /resetuserdata afterwards as explained by Willy-P. Schaub.
Then running tf.exe workspaces results in No workspace matching * found on this computer. ... until starting VS again, after which my workspace is visible again
As explained by Philip Kelly the TF400030 error might be because of a scanner running. But I don't know how to locate / kill such a scanner and no process on my PC is doing any significant IO.
I fear spending the time to reinstall VS would result in this exact same situation and reinstalling my PC seems a bit excessive.
Is there a way to make the TFS client forget about my local workspace? Or even better hunt down and kill whatever other process causes the TF400030?
sigh sometimes the answer is so easy: I just rename the mapped folder on disk and TFS started responding again.
Using TFS in Visual Studio 2013, another Team member made many changes to the solution structure (moving files between projects, new projects, new dtsx files, updating most files, consolidating connection managers). After getting latest, whenever I open the solution the Output window now pops up and continuously lists the same error:
TF10121: The path '' is not found or not supported. Type or select a different path.
(this error repeats about once per second)
There is a similar post here for VS 2013 with similar error, though apparently not with the near constant repetition of the error and no help.
Pinning the Output window helps by at least preventing the constant stream of repeating errors from changing the focus while I work.
No change after reinstalling software.
Closing the solution stops the errors. Unloading all the projects stops the errors, but they resume when reloading.
Opening a file in the soln sometimes temporarily halts the errors.
Opening a local solution is fine, adding the solution to source control causes error to start
This seems to be an error with the workspace mappings. It may be that your workspace mapping contains a drive which is no longer available or another issue that breaks the workspace. Possible issues:
Drive no longer available
Inaccessible network drive
Permissions are blocking access to a folder
Your mapping may require you to run with Elevated Privileges.
The target mapping may be empty
From the File -> Source Control and edit the workspace. If editing doesn't solve it, try deleting the workspace completely and creating a new one.
We using VS SSIS 2012, in solution folder I have .vssscc file and it has very short config info. I saw two parameters have empty value like ""
"PROJECT_FILE_RELATIVE_PATH" = ""
"ORIGINAL_PROJECT_FILE_PATH" = ""
So I changed to
"PROJECT_FILE_RELATIVE_PATH" = "."
"ORIGINAL_PROJECT_FILE_PATH" = "."
And seems removed message. As you can see I have no explanation. Just tried and worked for me.
This happen to me in Visual Studio 2017 with a solution that contained a python project. One of the python environments was an old environment I deleted before. Once I removed that environment from the project the repeating error stopped.
I am developing a VB.NET (4.5 framework) solution in Visual Studio 2015, Win10 OS, and have been able to run the builds uninhibited for several months, but now I am receiving the following error upon starting the build:
vbc : error BC2012: can't open
'C:\MyProject\ProjR5\ProjR5\obj\Debug\ProjR5.exe' for writing: Access
to the path 'C:\MyProj\ProjR5\ProjR5\obj\Debug\GenTagR5.exe' is
denied.
At first, VS2015 would give me the option to run the last successful build, but even that is no longer an option. After exhaustive internet searches on this problem, none of the dozen or so given solutions are solving my issue.
Here is what I have tried in order to resolve the error so far:
Ran sfc /scannow (elevated prompt)
Using ProcessExplorer, find handle or DLL substring that included my project
Made sure there were no hanging procs (including procs with my project name, devenv.exe, [project].exe, [myproject].vhost.exe, etc.)
Restarted VS2015
Restarted VS2015, running "as Administrator"
Restarted Computer
Full Shutdown of computer
Complete Rebuild of Solution
Build->Clean Solution
Build->Clean Solution, then Build->Build Solution
Build->Rebuild Solution
Uninstalled and Reinstalled VS2015
Disabled all indexing
Removed "Read Only" attribute from entire project folder and files within
Checked startup scripts for like- or identical processes
Disabled all AV apps
Disabled all antispyware apps
Disabled all firewalls
Verified that Application Experience (services.msc) wasn't disabled (I'm using
Win10 ... it isn't even in the list of services)
Set Tools->Options->Projects and Solutions->Build and Run->Max. parallel
builds to 1
Rerun aspnet_regiis.exe (under .NET\Framework)
Checked Local Security Policies and verified account was listed under
"Impersonate a client after authentication"
Removed \bin and \obj folders
Put \bin and \obj back when removing them didn't help
Removed \bin and \obj folders, then Rebuilt
None of these have worked. Any suggestions?
The problem ended up being Samsung Magician's Rapid Mode losing data during its write-caching phase to my solid state drive. I turned off Rapid Mode, and now the project builds without any problems.
Sorry for came too late, but i had this problem and i wanted to show how i fixed for the next devs who need a solution:
It's quite simple, just change your proyect assembly name:1) On your solution explorer: Right click on your proyect.
2) Properties>> aplication>> assembly name>> change it.
3) Compile, run to test it.
4) Change the name again if u wanted the original name.
Adding a description:
Changin the assembly name
New 2 programing in VS but i had same problem of Access or Write exe file ON BUILD.
Problem came out of nowhere. I didn't use or make changes 2 exe file in months,
made exe file, used it now and then and forgot about it....
Then after few months i wanted 2 start exe but no icon on desktop ??? ....tried everything, lost 3 days of searching inside code for error in VS and then called Google....
I read last comment ABOVE which mentioned Bitdefender, opened it and found BitD did block and isolate exe files ..... so i tried exluding files and folders which made problems inside BitD but no help....
So i went back 2 VS.
Within debug i got some X86 processor error which didnt make problem to build but it was warning (free component name in error description helped me ), - errors you can ignore but they are here on build ....
So i made last move before starting it all over again. Removed COMPONENT from application, deleted it on PC ...started VS from start .. and ALL was OK !!!
So in my case it was all about FREE component i used in app inside VS .... Bitdefender found some add / virus in it and blocked build progress.
BitD deleted or blocked exe file in start....
Hope this help anyone with similar problem !
The cause of this error for me was that Team Foundation Server had pulled in a bunch of files to my work space as Read-only. Not sure why it pulled them down from the server with read-only checked, but all I had to do was uncheck it.
Ok. Create a new solution and add its directories to the exception list and copy all your work, except for the '.vbproj' and except for the '.csproj' and the directory files to the directory of the directory of the new solution. I have tried that and it works, due that I have Bitdefender, it will be the only way to sort that issue. After doing so, try to build the app again. If it does not work, then I am definitely out of ideas.
The error says:
Failed to create extension manager for the target platform 'Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider'.
My teammate created the DB Project, but when I pulled it down from source control it failed to create.
The solution is to get an update to the "SQL Server Data Tools". You apparently have an older version.
Look in Visual Studio 2013 under Tools-->Extentions and Updates. On the left pane from there, click on Updates. Hopefully you'll be able to find the update you need there.
(Alternatively, run a repair installation on "SQL Server Data Tools" under Windows' Control Panel-->Programs.)
I fixed this problem by lowering the required version of the tools. I'm not sure why they are installed on his machine and not on mine, but edit the dbproj file and change the requirement to a lower version, like this:
Original:
<SchemaVersion>2.0</SchemaVersion>
<ProjectVersion>4.1</ProjectVersion>
<ProjectGuid>{......}</ProjectGuid>
<DSP>Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider</DSP>
<OutputType>Database</OutputType>
<RootPath>
</RootPath>
Updated: (don't include the *'s)
<SchemaVersion>2.0</SchemaVersion>
<ProjectVersion>4.1</ProjectVersion>
<ProjectGuid>{......}</ProjectGuid>
**<DSP>Microsoft.Data.Tools.Schema.Sql.Sql110DatabaseSchemaProvider</DSP>**
<OutputType>Database</OutputType>
<RootPath>
</RootPath>
Had the same problem and tried the above solutions, though even creating a new project from scratch was getting the same error message. I was also getting "File exists" for some reason.
I found the following in the event viewer:
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
at System.IO.__Error.WinIOError(Int32, System.String)
at System.IO.Path.InternalGetTempFileName(Boolean)
Cleared my temp directory and now the database projects are once again behaving. This is probably not a real common solution to this problem, but wanted to get the info out there in case it can help anyone else!
You can try these steps:
Try adding another database project in your solution.
Enter in the edit the DBProj File
Copy the DSP and use that one.
I was trying to move the proj from vs2013 to vs2012 and it worked for me. The provider was:
<DSP>Microsoft.Data.Tools.Schema.Sql.Sql110DatabaseSchemaProvider</DSP>
You can try the one above if you have VS2012.