Synchronise AD with TFS 2015 worked properly for years even after the update from TFS 2013 to 2015. Suddenly the sync was broken. And the following Error came up:
Maybe you add a group or user with illegal character to AD?
Like posted here
Team Foundation group accounts must not include non printable characters in the ASCII value range of 1-31. Tab's ASCII value is 9, so it's not supported in TFS.
We tried to follow: Mike Kaufmanns Blog
which will guide you to execute his program from github
When executing this program a user popped up and his description had faulty characters.
We removed the whole Description and the Sync executed properly.
Regards
Related
The date of Team foundation server changed to the year: 2023 and after that non of the defined work items can be found at the board. Neither they're accessible by querying. As it seems they're lost for only a certain project. All of the other projects are alright.
They didn't appear even after correction of the date.
How can I get the disappeared work items back?
Please check the work items not only in VS but also through web portal.
If you could also not find the work item by entering a known Work Item Id. Suggest you remote to your TFS database server and launched SQL Server Management Studio to explore the raw data. Double check if the workitems are still stored in database.
If not you may have to restore your last back-up TFS database. Otherwise suggest you clear TFS and VS cache.
I am trying to find out the users that has logged into TFS 2015 Update 3 in last 6 months.
Solution using C#/ REST API is good, if not available is there a way to generate the report using SQL.
I have followed this:This. I think the Query is not compatible with TFS 2015 Update 3 database.
This is only possible if you don't clean up or archive the contents of the tbl_command in the TFS databases. By default these are cleaned up after 7 days (from the top of my head). The limit can be changed by altering the job definition (which may need to be redone after each service pack installation).
Or you can setup a custom job that copies the contents of tbl_command to a custom table/database for future reference.
Which leaves you to see whether a user has made any work item changes or checked in code in he last 6 months, queued any builds, triggered any releases... Each uses a different API and a lot of these don't offer a easy query by user interface as far as I can know.
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 am trying out Enterprise Architect integration with Team Foundation Server using EA trial version. I was able to create a model with several sub packages using DBMS based and TFS 2013 as a version control system. I was able to check out a package successfully from TFS via EA. However I could not check in that same package, EA keeps showing me the error message:
You cannot check-in package ‘blahblah’.
The associated file ‘blahblah.xml’ is not currently checked-out by you.
I double checked the xml file from TFS Source Control via Visual Studio, it showed that the xml file was “lock, edit” under my same credentials that was used in EA Version control settings.
Interestingly, I was able to Undo check out successfully.
Any help is appreciated.
I remember having this issue at work a couple of months ago. I don't have access to Enterprise Architect at the moment, nor am I in a position to recreate the problem to verify this solution, but I do remember how our team solved it:
The missing assumption to solving this, which may or may not be true in your case, is that your team went from the standard authentication method in the TFS settings, to SCC(or possibly the other way around). Now, assuming your credentials are the same in either method, you won't get an issue in Visual Studio, and can do everything apart from checking in in Enterprise Architect until you update your TFS settings in Enterprise Architect. Heck, everything will seem correct everywhere as your files IS checked out to you (no idea why this is permitted) but you cannot check in through the standard authentication method.
I had the same problem which I was able to solve only by resynchronizing the status with the version control.
Right click on Model, click on "Package Control", click on "Re-sync status with VC provider".
In TFS I have a started a Scrum project, but I want to add some fields to a Work Item.
So I'm following this tutorial on how to add Estimate and Completed work hour fields to a Work Item.
I added one field in the layout, like shown in the tutorial. But when I try to save it I then get the following error:
TF237113: You don't have enough permissions to complete the import operation.
I think I have all the needed permissions. I changed all my user permissions and also the permissions I have in the TFS project that I'm working on.
But so far no luck. Even when I try to add a field in the Layout tab that already exists, then it still gives me that error. Anyone any idea what I can try to solve this error?
It looks like you're using Visual Studio Online (Since I can see that you have a Windows Live ID), Visual Studio Online doesn't support process template customization at all at the moment. This is due to the fact that they release new versions of the service every 3 weeks or so, and having to consolidate and test all customization across all projects would be a major pain.