In the process of trying to migrate the TFS - Server 2013 to a new location we encountered an issue.
TF30046: The instance information does not match. Team Foundation expected xxx which was not found.
We tried to change the HostID in the DataBase as suggested by this link:
https://devtipsandtricks.wordpress.com/2013/02/25/tfs-express-2012-tf30046-the-instance-information-does-not-match/
but this did not resolve the issue. Because when I do that, I have another error stating the collection is in the process of being serviced.
Steps taken
Fresh OS
New install of SQL
Restored database from backup (all was well)
It seems I made it work.
Thnx to #ds19 for making me revist the documentation again.
The fix was:
Restore the database from backup
Doing the Application Tier only wizard
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.
My current environment is on a single vm:
TFS2013
SQL Server 2012 (dedicated instance, installed on the same vm)
1 project collection
Reporting configured
My migration target environment is:
New VM containing TFS 2017 update 1
Existing SQL Server 2014 AAG, without SSAS
Reporting not configured (because of SSAS not installed), and I actually don't need reporting
I tried multiple ways to do this installation, but encountered many problems with Always-On:
Upgrade/configure directly with database restore (through SQL Management Studio) directly in AAG, encountered TF400711 error
Upgrade/configure without Always-On, works well, but now my problem is to move my databases to AAG. Tfs_Configuration is OK, but when I attach my collection, encountering the TF246017 error. I'm not understanding this error because I use the same connection string than my Tfs_Configuration database...
What is the best procedure in my case?
I read this and this post, but they don't match to my situation.
You could use way2, since Tfs_Configuration is OK, you just need to figure out the error TFS246017. This error can occur due to following reasons
Incorrect SQL Installation order especially if you are using Express edition
Database In Recovery
Database Out-of-Sync – during migration to newer version of TFS
Permission of Service Account is not right
SQL Database not running or not reachable
TFS Proxy not reachable
Double check if you have got enough permission for the installation account. Suggest you go through the Windows Event Log , a good candidate where to look for the potential cause.
Also take a look at this thread: TF246017: Team Foundation Server could not connect to the database & this one. There are many resource about this issue in google which may help you figured it out.
The company I'm working at is moving TFS to a new server (and new user accounts since now we are using domain accounts). The previous server was on version 2012.4 Express and the new is using TFS 2013 Express.
To do this, I backup the old server databases, migrated them to the new server by using the utilities provided for that matter and ran the upgrade wizard.
The only problem I'm having now is that I can't map the projects to the previous locations on this since it keeps telling me that the project is locked in my previous workspace.
I've used a couple methods that should have worked but keep getting the same error:
Invoked the webservice StapWorkitemCache at http://ServerName:8080/tfs/WorkItemTracking/v3.0/ClientService.asmx both on the new and the old server
Ran witadmin rebuildcache /collection:http://ServerName:Port/VirtualDirectoryName/CollectionName both on the new and the previous server
Deleted VersionControl.config from my computer
Deleted the workspaces by connecting to both the servers on Visual Studio and removing any workspace that I had.
I just keep getting the same error saying that the local folder is locked to the old workspace. How can I solve this once and for all?
EDIT:
Is it possible that I should be migrating just the TFS_DefaultCollection database instead of bringing the TFS_Configuration along?
EDIT 2
New problem arose:
Nobody can see their projects on the old server. Since I couldn't get the new server to work, I put the old one back online and now nobody can connect and on the web administration page there aren't any projects.
I am unable to connect to the server which is located remotely and required connection to OpenVPN.
I would have concluded that its some sort of Authentication issue, but it seems that my teams mates using similar Working Environment to mine are able to establish connection. I am able to log in from their PC using my Credentials. Looks like this could be due to my local settings.
I have cleared the Cache as suggested in MSDN sites. Also, Firewall and Antivirus are off.
I also get prompted for the User/Name password when I click Team Explorer Icon on Visual Studio. Invalid credentials show error messages as expected, on entering proper credential information, I get the following message:
TFS31001: Team Foundation cannot
retrieve the list of team projects
from Team Foundation Server. The Team
Foundation Server returned the
following error: Team Foundation
services are not available from the
server.
What could be the reason for this?
That error message is always due to a security issue but that doesn't tell you "why" there is a security issue. Can you take a look at the event log for more details- not sure what else might be in there but it might be a good starting point.
I had this issue a long time ago when working remotely and it was a trial and error thing but in my case clearing cache then removing the TFS Team Project and re-adding it fixed the issue. You can try that. I see you did clear cache but I am not sure from reading this if you removed and re-added. If settings are cached and you dont do that I doubt you will see a change.
Another more aggressive solution would be to uninstall and reinstall Team Explorer. Also, make sure your up to date on SPs. Permissions could have been messed up somehow with TFS installation and this could potentially resolve the issue.
Anyway, I know this isn't a cut and dry answer but I hope it helps. I just spent the last three days upgrading all our company Team Projects from 2008 to 2010 so I feel your pain :)
It was problem at my end. Using a Different Gateway did the trick.
I've got this error once my TFS database server ran out of diskspace.
I encountered same error.
I found this which looked like a viable solution. :
http://social.msdn.microsoft.com/Forums/en-US/tfsversioncontrol/thread/f681a2d6-eca9-4488-96a3-ed979a545a9b
I ended up just turning my proxy settings of in IE and it started working instantly.
The same story occured with tfs 2012 - it was installed and configured properly, local network has domain and all users in domain correctly connected and worked with tfs projects.
But once the connection denied all tries for connection, all credentials were correct, but connections has been refused. Tried to configure tfs clients access, to reboot client machines... but worthless.
Only server service/machine rebooting helped. Good luck!
I fixed by clearing the cache at:
C:\users{yourusername}\Appdata\Local\Microsoft\Team Foundation{version e.g.3.0}\Cache
Quit any open instance of visual studio first.
We have a problem with our current TFS installation. For some reason, which I won't get into, the Sharepoint DBs (sts_content, sts_config) got corrupted. So now, none of our team-project sites work, we have no access to our documents and can't create new team projects. We can still work with the version control, though.
We wanted to "play" with the server and try to fix it, without affecting the users. So we duplicated the server to a virtual one. We now continued and changed all of the relevant configuration to point to the new server, as explained in the MSDN article.
The step of rebuilding the warehouse (with setupwarehouse) failed. Also, we can't access the VersionControl web service (ourserver:8080/VersionControl/v1.0/repository.asmx). We are seeing errors in the EventLog:
TF53002: Unable to obtain registration data for application Build.
TF53005: Unable to retrieve the Team Foundation Server installed UI culture.
TF53002: Unable to obtain registration data for application VersionControl.
TF30040: The database is not correctly configured. Contact your Team Foundation Server administrator.
The solutions suggested in this blog post did not assist. So now we're kind of stuck.
Any assistance will be appreciated.
This is a really old question, but what I would suggest doing is installing a fresh copy of Team Foundation Server 2010, then in the configuration wizard, select 'Upgrade' and choose your existing TFS2005 databases. This will allow you to get a working server up and running, without SharePoint and the Cube/Warehouse configured. You can then tackle each of those problems separately via the TFS Administration Console.