I had started the upgrade from 2012 to TFS 2015 3 days before 2 of the collections have completed and one of the collection out of 3 is running from Day one.Its size is about 2.5 TB.Having said that , i had performed same upgrade months back and it had finished successfully in 52 hours.Can any one help on the reason why it is taking a longer time now ?
Look at the screen shot for reference:
Upgrade Window in progress
There is a log named TFS_TFSUpgrade_Date_Time with the type TFS Upgrade in Team Foundation Server Administration Console→ Logs.
You can compare the logs between twice upgrade to check which step had taken a longer time.
Related
I went to do an upgrade of TFS2015 to TFS2018.2.
In past tests and experiences, these upgrades take some time against the collections if they are on the larger side. I first started a POC with TFS2015 to TFS2017.3 and that took 24 hours total to do the upgrade and it was successfully completed. As I was doing the POC TFS2018.2 RTM, so I went with the same POC but this time I went from TFS2015 to TFS2018.2, that upgrade only took about an hour or so, which seems really odd.
It looks like it completed without error but the amount of time it took to upgrade the collections seemed really off, compared to any other upgrade I have done in the past. How long is the upgrade process expected to take?
The length of time to upgrade the collections depends on the amount of changes made to the database, and which tables changes were made to, and the size of the team project collection databases.
I recently performed an upgrade against a 500 GB collection from 2015 to 2018 and the entire upgrade process took 20 minutes. It's fast.
Previous versions to 2015 were slow because TFS 2015 introduced significant database schema changes. Nothing after that has required such a major schema change.
I am trying to set up an integration with MS Project 2013 with TFS 2017 I have not tried this before. so i am not sure if there is a problem with my pc setup or the addin configuration.This is the error i get when trying to open saved query:
Error Converting Value "System.Security.Principal.WindowsIdentity;xxx" to type 'Microsoft.VisualStudio.Identity.Services.IdentityDiscriptor'.Path 'authenticatedUser.descriptor'. line 1 postion 168
I am able to load it from Visual Studio 2015 in the workitems load the Query and then click "Open in Microsoft Office" then choose MS Project. this loads successfully. but i do get errors that I can't publish changes. It asked to restart Project and try again
I cannot reproduce this issue with project 2013 and TFS 2017.
Check Addins’ key in registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\MS Project\Addins), change newest addin (e.g. TFCOfficeShim.Connect.5) LoadBehavior to 3 and others to 0, then try to open saved query in Project 2013 and check the result.
If still don’t work, try to repair your project product.
I have uninstalled Office 365 and Project 2013. Restarted my PC and installed Project 2013 and this fixed this issue.
The issue came back and did some more google searches. I found the answer as part of a bug kb
https://support.microsoft.com/en-us/help/3181963/excel-or-project-cannot-connect-to-tfs-2010-or-tfs-2012-servers
After installing this update and rebooting it works.
We are trying to migrate an On-Prem TFS 2013 project to VS Team Services and getting the following error on 77 Work Items (all the same error):
OH-TFS-Connector-0051: Operation failed createOrUpdateTestResult.
Server Error : Error occured while Create/Update Test Rrun caused
by:Date must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59
PM. Confirm that the date is correct.
This happened when we were trying to migrate 7 Team Projects (and we're just starting the process), such message don't provide us any clue about which one of the invoved Team Projects is the faulty one, also it doesn't seem possible that we could manually edit the source Work Items (Test Run) in order to fix the error.
We can provide the logs if needed.
This issue has been fixed in the latest release of OVSMU. However, from the new version onward, some migration features are no longer a part of the Free Version of the tool. Please refer the Gallery Page for a complete list of functionalists between version in the latest release.
I have managed to remove weekends from the sprint burndown chart within the TFS report server however cannot get the change to reflect on the Web Access view.
Following some documentation online I have even made changes to the 'Sprint Burndown.rdl' report within the Scrum 2013 Process Template and uploaded this back into TFS however this didn't appear to change anything.
Has anyone managed to successfully remove weekends from this chart?
The Web Access module uses a different location to store what weekdays are and which aren't. You cannot remove weekends from the graph, this is a much requested feature and according to the admin comment it is coming soon.
UNDER REVIEW · Visual Studio team
Visual Studio team (Product Team, Microsoft) responded · Aug 22, 2013:
We’re starting work on this and should be able to close it down soon. Stay tuned.
It might ship with TFS 2013 update 2 if they managed to fix this.
Update
TFS 2013 update 2 RC now has the features to set Team Days off, which will effectively hide the weekends and these team days off from the burndown chart.
Non-working days – Starting with Update 2, you can define you’re non-working days (weekends, for most of us) and we’ll exclude them from the burn down calculation so it no longer looks like you are on track when you really aren’t (because you don’t plan to work the weekend :)).
http://blogs.msdn.com/b/bharry/archive/2014/02/05/vs-tfs-2013-2-update-2-ctp-released.aspx
I'm trying to migrate from TFS 2012 Update 2 to TFS 2013.
Following the documentation I installed TFS 2012.2 on the new hardware, backed up/restored the databases, then installed TFS 2013 as an upgrade.
I can see the Team Project and the builds. The problem is when I right click a build to queue up a new one and click on the Parameters tab I just get a blank panel. My best guess is there was an error loading the parameters. Note those builds worked fine in TFS 2012.2.
If I create a new build from scratch and I use their new default template (TfvcTemplate.12.xaml) I still get the same error.
I don't see any errors in the output window or the event log.
It turns out it's a known bug with VS2013 connecting to TFS2013
The VS2013 hotfix has been released. Taken from here.
For future reference, this was fixed in Visual Studio 2013 Update 1 (see KB 2911573).