We migrated our TFS 2017 to TFS 2018 by first using the "Move or Clone Team Foundation Server from one hardware to another" instructions (https://learn.microsoft.com/en-us/tfs/server/admin/move-clone-hardware) and then upgrading that to TFS 2018 which seemed to go just fine. TFS works, however the URLs in the emails that go out regarding work items are still pointing at the old server. The only URL that I can find to change is the Public URL on the Application Tier, which is already correct. In the message header on the emails that are sent out, the old server also appears to be the sending domain:
In-Reply-To: Tfs.WorkItem.Project.######oldservername
I can't find references to that old server anywhere though. Any idea what I might be missing?
We were able to find the issue. The tbl_AccessMapping table in the database for the Project Collection had different values in it than the tbl_AccessMapping table in the tfs_teamfoundationconfiguration database (specifically the accesspoint field). tfs_teamfoundationconfiguration was correct, so we synced those correct values over to the Project Collection database.
This took some time to take effect, I assume due to caching. Restarting IIS would likely fix it quicker.
Related
I previously had TFS 2017 and SQL 2016 working well on a single 250GB Server 2016 .VHDX with two partitions, C: and D:. SQL is installed on C:, with its data directories on D:.
Oddly, C: started filling up unexpectedly, so I decided to move the D: partition to its own .VHDX and expand C:.
This all went well, and I now have two 100GB .VHDXs with C: and D:, respectively. (This is a one-man shop, so data storage needs are quite small at present. These needs will increase soon, however, so this is another reason to split off into multiples like this.)
The trouble comes when I try to sign in to TFS using the same domain account (DOMAIN\User) that worked before all of this took place. I'm now unable to sign in, and I'm prompted for credentials in a continuous loop (unless I cancel the basic auth dialog, in which case I get a 401-Unauthorized).
I've reapplied all accounts using the TFS Management Console, but this hasn't worked. FYI I'm able to boot to the server desktop and connect to the SQL instance and browse TFS tables using SSMS.
What must I fix to be able to sign in as before?
Seems the relationship between TFS and SQL server is destroyed by the partition expanding.
First, please check if there are problems for the SQL Server and TFS databases. If no issues, just try to Re-RegisterDB and RemapDBs for TFS.
If that still not work, I am afraid that you have to reconfigure the TFS. uninstall the application tier then reinstall it again using the existing database. If the SQL Server and TFS database also have problems, you have to reinstall sql server and restore the backed up data.
Similar thread for your reference : TFS 2013 Admin Console locks Tfs_Configuration preventing it's restoration
I have very recently started working on Team foundation server and really have limited idea on the subject.
I have been given a problem to solve and I really dont have an idea to proceed.
We are doing a TFS-Sharepoint 2010 integration.
In dev server, the TFS is configured and is pointing to TFS_DefaultCollection database. Now, in TFS, 3 new fields have been added. It points to Field101,Field102 and Field103 columns(I dont know how these columns are created but it seems it is dynamically generated,I suppose, not sure though) of WorkItemLatest table.
Some custom stored procedure is written to insert/update the database table with sharepoint webpart. Now in the stored proc, the developer has referenced Field101,Field102 and Field103 columns.
Now comes the question of deployment this to production. In production, there is already a TFS configured. We have to make changes on top of this. But, when running the sql scripts, we found, naturally, Field101,Field102 and Field103 are not present there. So, what should be our approach which will help us address this issue? Please suggest. Also, please let me know how these 3 fields are created when 3 fields are added in TFS UI? Please help.
You need to use the WITAdmin tool to export the work item type definitions that you want to edit and mahe the changes there. You can find this fully documented on MSDN: http://msdn.microsoft.com/en-us/library/dd236914.aspx
So, we are using TFS 2012 RC and have modified the work flow a bit for a regular task item by adding a few custom transition states.
When updating tasks though Visual Studio 2012 RC, everything works fine. I can move through all the states without any problems. However, when updating the task through TFS Portal, either by dragging the item on the board or opening the form and changing the state using the pulldown, I get the following error: "TF237165: Team Foundation could not update the work item because of a validation error on the server. This may happen because the work item type has been modified or destroyed, or you do not have permission to update the work item."
This ONLY happens, however, when moving to the Done state and nothing else. All other states work fine.
So, I'm not sure what that means since it works fine in Visual Studio. What would be helpful if I could see the exception or more information somewhere, but I don't know where these validation errors are stored.
Any help would be greatly appreciated!
The issue was with the work flow. The transition was setting a field that was conflicting with the state also changing the same field.
In my case there was another issue.
The problem was that the field had a trailing \r\n in the data being sent down by the server. I believe the client javascript OM was removing this which makes the field dirty even though it’s read only.
Workaround was to make the field read-write instead of read-only. Then I set back it to read-only - and now it works.
Micrsoft promised they may fix it in next release.
In my case, on TFS 2013 U5 I had changed my TFS Profile DisplayName so that it did not match my ActiveDirectory DisplayName. I could not edit or create anything until I changed the DisplayName back.
I have configured TFS 2010, but when I try to load the project dashboard for a team project, it returns a reporting service error so I am not able to see the "Task Burndown (hours)" and " Burn Rate (hours/day)". Other parts of the page are working fine.
The error is as:
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot impersonate user for data source 'TfsReportDS'. (rsErrorImpersonatingUser) Get Online Help
Log on failed. (rsLogonFailed) Get Online Help
For more information about this error navigate to the report server on the local server machine, or enable remote errors
I got resolution finally....
Go to analysis service.
You will see database named as TFS_Analysis.
Go to Roles node.
View properties of "TfsWarehouseDataReader".
Click on Data Sources.
Now you will see Tfs_AnalysisDataSource.
Change access to "Read" and check "Read Definition" box. Now Click OK and You are Done.
The main problem was with SCHEMA CONFLICTS.
First identify which fields are causing schema conflicts, invoke GetWarehouseStatus and observe the XML which fields got conflicted, and in which collection. once you found the filed names then rename the fields with the help of below link.
geekswithblogs.net/Natalia/Default.aspx
msdn.microsoft.com/en-us/library/ee921480(v=VS.100).aspx
then rebuild your warehouse from tfs admin console, take a back up of old database in sql database and delete it .wait for some time (depends on warehouse time to refresh the cube or check the GetWarehouseStatus next day and check the xml ). to check this use below link
type //localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx?op=GetProcessingStatus
I spend lot of time to resolve this issue, that's why posting the solution here, this may help some one... any queries related schema conflicts and Reporting services feel free to post me... iam not a expert but for sure i can help you out in this issues....
Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.
We're switching over to Team Foundation for our version control, and I have to learn it and set it up. Our IT guy did the installation of the both the data tier and the app tier, and he is of course convinced that it's right. However when i log in as tfssetup and try to create a new project, i get the error:
Error
Insufficient permissions to create a new SQL Server Reporting Services at tsttfsapp1.
Explanation
The permissions granted your user name and ID on the SQL Server Reporting Services at tsttfsapp1 do not allow you create a new project. You must be granted specific permission by the server administrator.
User Action
Contact the Administrator for the SQL Server Reporting Services at tsttfsapp1 and ask that the permission "Content Manager" be added to your user account
So i tried to log in to http://servername/Reports_TFS it asks for the credentials but doesn't accept them. Even stranger when i try to access it from a computer and user that aren't on the same domain as the app tier server, it doesn't ask for credentials and lets me right in. As far as i know the default name of the site should be Reports, not Reports_TFS is it possible that his renaming of that could be causing the problem?
tfssetup is definitely a "Content Manager" as far as i can tell, so i don't understand why we are getting this problem. Also any recommendation for good websites or books that can take a complete beginner and help me become an expert in 3 weeks (what's left of the 6 week time frame allowed for me to learn) would be appreciated.
Thanks
I'm not sure this will help, but we had this error at my place of work on our 2005 TFS server. We opened a ticket with Microsoft and sent them our TFS database. They were able to replicate the issue with the copy of the database. Somehow the TFS database had gotten into an invalid state, but they weren't able to determine how this happened or how to fix it. Unfortunately, this error kept us from being able to upgrade the server to TFS 2008 too. We ended up getting latest of all the code and adding it to source control on a new install of TFS. What a pain.
OK so it turns out it was only a problem because I was using a 2005 client with a 2008 server. A 2008 client has no problem creating a project on the 2008 server, but the 2005 client is not able to create a project on a 2008 server.