I'm running a TFS -> VSTS migration using OpsHub Visual Studio Online Migration utility.
Version-1.0
OpsHub Integration Manager Framework-OVSMU-V2.0.0.002
I keep getting errors similar to the following:
OH-ConnLoader-0003: Connector for system name : tfs.XXXX.com\XXX to XXXX.visualstudio.com _PROJECT| TFS Target 1456778794042 Source TFS 1456778794043 could not be instantiated due to OH-TFS-Connector-0060: Unable to initialize TFS SCM Connector. OH-TFS-Connector-0048: Failed to login to Team Foundation Server : https://xxxx.visualstudio.com/ with user : null. Server Error : TF400324: Team Foundation services are not available from server https://tfsprodscussu5.app.visualstudio.com/A74e933d7-11c5-493b-af7e-a9e81b64ff78.
Technical information (for administrator):
Page not found.. You may have given wrong credentials or credentials are not valid now.
I don't get the errors repeatedly, but about once a day. Since I'm the only one executing the migration and I can't watch it all day and night when we have these failures overnight I lose hours of potential migration time. When the migration utility hits this error it halts the migration until you start it over. So far I've been running for 3 days and have only been able to migrate 3000 code items. At this pace it will take me 11 days to migrate this one project, just the code items!
Is there any work around for this error? Why does the migration halt when it hits this error.
Try clearing the Team Foundation cache on your migration computer. To do so, follow these instructions:
Close OpsHub and any other .NET applications you might have running.
Delete any files that might be in these folders:
%localappdata%\Microsoft\Team Foundation\3.0\Cache
%localappdata%\Microsoft\Team Foundation\4.0\Cache
%localappdata%\Microsoft\Team Foundation\5.0\Cache
%localappdata%\Microsoft\Team Foundation\6.0\Cache
Open OpsHub and resume your migration.
We had the same issue earlier today, which completely blocked our migration for 3 hours until I did this.
If this is happening to you daily, then you might want to do this each afternoon (until your migration is complete).
Related
I upgraded TFS from version 2010 -> TFS 2013 Update 5 -> to TFS 2017.3.1. The migration was successful, without errors.
When we select any work item we get error:
TF400898: An Internal Error Occurred.
{"message":"TF400898: An Internal Error Occurred.","type":"System.NullReferenceException"}
Content?bundle=vss-bundle-basejs-vLDQ_BPnMflh1yV4rhP43SsHlun31XvwYB1svh7haP9E=:5 GET http://servr_name:8080/Colection/sssdddd59ad7c58-da11-49ed-a085-6acc62384a85/_api/_wit/workItemTypes?__v=5&typeNames=FDR&stamp=5-12c3sss1sss162-12c40e0-117e5b3-12c4b45-11884ddddsaf-12c4b4b-1sss2c3166-117e5c2-ffffdddsffff826b3e0c-0-0-stateColors-True 500 (Internal Server Error)
It looks like api can't read domain users who own the work item.
This is not a TFS cache issue because it has been cleared on the client and server.
It depends on the users. eg, TFS administrator does not have such an error, work item opens correctly.
What could be the reason for this error?
Update 2
OP finally re-graduated 2010 to 2017 without the following command and it seems to have helped.
TFSConfig ChangeServerID /SQLInstance:server_db /DatabaseName:TFS_Configuration
First check Event Log in Event Viewer to see whether there is some useful information.
For the migration, make sure there are not any databases left from another TFS instance. Cleaning these up should help.
It depends on the users. eg, TFS administrator does not have such an
error, work item opens correctly.
If this issue depends on users. That may related to permission sync up.
You could try to remove all users out of the project and add them back again. Which may do the trick.
Also double check the permission related settings. Whether they are added under an area with deny permission for security settings. Since in TFS, deny trumps allow.
Update
If the upgrade was successful without any errors. Then this kind of error may related to the configuration.
You could try re-running the configuration wizard for the team project to fix the issue. How to please refer this tutorial: Configure features after an upgrade
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.
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
I have previously Install the TFS 2013 pre-lease,create team project everything was working fine util the license expired,giving me only one option that is to uninstall and reinstall.
I Now install new instance of tfs 2013,I created a report server do all the configuration,tested the url and it works fine.But when i try to configure the TFS In a stadard single server mode. i keep getting error when its configuring the report. Am new to this Technology but i did not face such issues during my first installation.The report server and the tfs are both on the same server.But the database am using is on a name instance.
here is the error i keep getting:
TF255324: The database that you specified cannot be created because a database already exists with that name. The database name is: Tfs_Warehouse. The server hosting the database is: URANUS\dev. You can use one of the three following options.
• If the database is a valid database from a previous version of Team Foundation Server and you want to upgrade it, you must use the Upgrade from Previous Version Wizard.
• If the database is a valid database from the current version of Team Foundation Server and you want to use it, you must use the Application Tier Only Wizard.
• If the database is a valid database used by another Team Foundation Server instance and you wish to create a new database, you must use the advanced wizard to supply a different SQL Server instance or database label.
For more information, see the readme file and the installation guide for Team Foundation.
The following database already exists, but cannot be used as part of this installation of Team Foundation Server: Tfs_Configuration. The database is hosted on the following server: URANUS\dev. You can manually delete or rename this database before you continue, but it is not required. If you do not, the database will be renamed as part of the installation process.
TF400080: Your system does not have the recommended amount of system memory available: 10 GB. While SharePoint 2013 with Team Foundation Server can operate with less than this amount of memory, the performance will be degraded. Upgrade your system memory to at least the recommended minimum for optimal performance.
TF255142: Windows Firewall is not enabled. If you enable Windows Firewall after configuring Team Foundation Server, you must add exceptions for ports used by Team Foundation Server to Windows Firewall.
Enabling legacy trace logging for SharePoint. Upon completion of installation or upgrade, legacy trace logging will be returned to its original status.
I suggest you to upgrade your TFS 2013, by using http://aka.ms/TFSUpgradeWeekend.
link : http://blogs.msdn.com/b/briankel/archive/2013/08/23/register-now-for-team-foundation-server-2013-upgrade-weekend.aspx
Remark : Enter your credentials on MSDN
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.