I am using TFS 2013 update 4:
Scenario:
Add a new iteration from the administration page of a project.
Go to the project Dashboard create a new work item.
Newly created ierations and areas are not shown in the relative dropdowns.
Steps taken:
Checked the server for errors in the event viewer, no issues.
Check the 'Visual Studio Team foundation Job Agent' running with no issues under the TFS admin user.
The newly created iteration exists in the collection database table 'tbl_nodes' and in the 'TFS_Warehouse' Database.
Checked the Jobs on the database and forced them to start, did not solve it.
What I was not able to do is figure out which table exactly the TFS is querying the nodes from, afterall the Stored procedures are encrypted.
Amemdment:
**the newly created iterations exist in the 'tbl_nodes' but does not exist in 'TreeNodes' table.
Since newly created iterations and areas are both in database. Try to restart Team Foundation Background Job Agent service to force synchronization in TFS server.
If it's still not help, give a try with rebooting the server, which may do the trick. You can also take a look Mark's solution in this similar issue Newly created TFS 2010 iteration not visible
Related
My company is using a TFS 2013 (Update 4 = 12.0.31101.0) server for development. I was tasked with migrating the TFS server to VSTS but realized I had to update to TFS2018 to be able to use the current migration tool.
My boss obviously didn't like the idea of performing "open heart surgery" on our productive environment so we created a back-up of the SQL Collection-Database (by creating a dump using Management Studio) installed a Trial Version of TFS/SQL Server in a VM (VirtualBox) and tried importing the back-up.
Using the built-in import tool (TFS\Tools\TfsRestore.exe) I imported the old DB into the SQL Server, which actually worked really well, looking at the DB in ManagementStudio everything that needs to be there seems to be there.
However, trying to attach the Team Project Collection in the Team Foundation Server Administration Console I simply can't find it. I List Available Databases and the only one it finds is the DefaultCollection that was created during installation of the server.
I made sure that the versions are the exact same version, only difference is the License which is a real License on our production environment and a Dev License on the VM.
Anyone got an idea why this is happening? Maybe some way to get a more detailed Exception?
Edit: Trying to use the TfsConfig registerDB command throws an expection:
TFS30040: The database is not correctly configured. Contact your Team Foundation Server administrator
First, please make sure you are a member of the Team Foundation Administrators security group and a member of the sysadmin security group for any SQL Server databases that the new Team Foundation Server uses.
Usually this kind of issue should be solved after giving proper database permissions to the user.
Besides, after the configuration you can try RemapDBs to redirect TFS to its databases.
Back to the error: TF30040: The database is not correctly configured. Contact your Team Foundation Server. Here is a similar thread for your reference: TF30040: The database is not correctly configured
Moreover, you could also check the event view on your VM, if there are some more detail error message for troubleshooting.
Did you detach the collection in the TFS admin console before taking the backup on your 2013 server?
When you detach the collection is moves all of the relevant data from the TFS configuration database in to the collection database. You can then take a backup of the collection database and restore it to the new SQL server instance.
Note that detaching the collection will take it offline until the backup is complete and you re-attach the collection.
Then the new version of TFS should be able to see the collection and attach it. This will copy the configuration data to the new configuration database and you'll be able to bring the collection online.
So steps are
Detach collection in TFS 2013
Take backup of the TFS 2013 collection DB
Re-attach the TFS 2013 collection so that users can continue to use the collection whilst you test your upgrade
Copy the backup to the 2018 server
Restore the backup
In the TFS 2018 Admin console attach the collection
Once you're happy that the upgrade will go smoothly repeat the process but skip step 3.
Managed to do it by following this guide : https://cromwellhaus.com/2013/08/restoring-tfs-2012-to-sandbox/
Short Version: I was missing the config database, it was quite easy once I was using the old config.
I'm trying to move a Team Project from one Team Collection to another, including check-in history, user stories and source code.
I'm running a TFS 2015 Update 3 setup, but the tools I found do not support this version.
Tools:
http://tfsintegration.codeplex.com/
https://visualstudiogallery.msdn.microsoft.com/eb77e739-c98c-4e36-9ead-fa115b27fefe
0. Create an empty collection that will be used as a copy of DefaultCollection.
I called my second collection "TeamPrjectCollection"
1. Make a Full Backup in TFS Administration Console
2. Detach the collection that contains your Team Project
3. Back up the collection database only using SQL Management Studio.
4. Restore database from backup to your empty collection
Restore DefaultCollection from backup file into the empty Collection called "TeamPrjectCollection". You might get an error message during restore, make sure to open Options tab and check "Overwrite the existing database" and "Close existing connections to destination database".
If you still get access error try do get DB offline restart the server and then back online the DB.
5. Attach both collections in TFS Administration Console
Select Tfs_DefaultDatabase DBs from the list and attach it, then select Tfs_TeamProjectCollection and attach it too with different Collection Name. Ignore the warning at the end.
6. Sort your Team Projects in both collections
After your attach process second collection will go offline due to the warning message saying that your both team projects exist in both collections.
Simply remove MyFirstProject from 'TeamProject Collection'
and remove 'TeamProjectToMigrate' from 'DefaultCollection'
Bring 'TeamProjectCollection' online.
As can see both Collections are accessible from TFS
For more details please refer to Visual Studio documentation here: https://www.visualstudio.com/en-us/docs/setup-admin/tfs/admin/move-project-collection
As #Daniel mentioned in comment, there's no way to move team projects between collections other than by using third party tools. But this feature is under planned, you can track this UserVoice:
We are committed to allow you to move team projects between
collections, although it’s currently not in scope for the 2016
calendar year. We’ll provide an updated timeline as we get closer to
2017.
I'm using TFS 2015 on-prem and I'm using the standard SCRUM template. I have 1 Team Project and I'm using the team field to segregate work. I have created a few build definitions and ran a few builds over the last few weeks.
When I installed TFS I did not install or configure Reporting Services straight away as I had planned to do that later. I have since done this and I now have my Tfs_Warehouse which is updating with most things but NOT FactBuildProject or FactBuildDetails. Some of my other facts are pulling over, such as FactCurrentWorkItem and even FactBuildCoverage. I have rebuilt the warehouse in the TFS Admin Console.
As this is a standard process template and standard reports I expect that the required fields should be set to reportable.
How can I get data in my FactBuildProject table and where can I look for issues with it? I'm not sure where to start and I can't find anyone else in the world with a similar problem.
If you are using the new task-based build system, then you are out of luck, since that data is not being propagated to the data warehouse.
Check the comments on this blogpost: http://nakedalm.com/create-a-build-vnext-build-definition-on-vso/
We recently changed domains for our entire network, and I am trying to find a way to migrate my TFS workspace from my old Domain\Username to the new Domain\Username without losing any pending changes.
Note also that I need a solution to accomplish this via the command line, as Visual Studio won't let me access the old workspace from the old domain.
See the MSDN article about the Workspaces Command. You can invoke tf workspace with an argument /updateUserName. That should do the trick.
I just migrated my TFS server from my old domain to a new domain because my organization had a company name change. After the migration, I had to overcome several issues and eventually I was left with the development team getting TFS14045 error messages. The fix to this problem was simply having the developers issue the following command from their Visual Studio command prompt.
tf workspaces /updateUserName:OLDDOMAIN\olddomainusername /s:http://[tfsserver]:8080/tfs
I found that if multiple developers had logged into that workstation and created workspaces with visual studio that I had to issue this command for each domain account until I get them all. After I did this procedure I was then able to remove their corresponding records form the tbl_identity table of the TFS_Configuration database on my TFS server so that I wouldn't then also have to look at duplicate accounts for the same person (one for their old domain account and one for their new domain account) inside my TFS collection. Leaving this record in place also created another error that you will get if a developer breaks the build and TFS tries to create a auto generated work item for that developer to fix the build. If both the old domain account and the new domain account is present in the TFS collection (recorded in the tbl_identity table...) then TFS will not know which user account to use when making the work item for the broken build.
Good luck and I apologize if this is too rambling to read but I am in a hurry and I hate reading posts that leave out detail ;-)
We've lost our TFS and domain servers. TFS was configured to use domain accounts. We could resotre only the TFS Project Collection databases and thanks to the "TFSConfig repair" command, we finally attached them to a new TFS instance.
But all of the default security groups for repaired projects are lost (except the administrators). For example we don't have "Contributors" group anymore.
Now we want to restore these standard groups. Maybe it's possible to fix it by applying the default TFS "project proccess templates" on all existing projects and collections again.
Is there any way to address it?
As you lost the Domain server you have to follow the Move User and Service Accounts chapter of the "Move Team Foundation Server from One Environment to Another" procedure.
By the way, there's no such feature as reapplying a process template on an existing Team Project.
Have you tried to recreate at least one group that you lost? Only to know if that is working (maybe TFS will return an error because the group still exists in the database but it's not shown for whatever reason) ?
One last thing: check the TFS Scheduler Windows Service is running on the TFS Server and look for errors in the Windows Event Log.