TFS Reporting Services - visual-studio-2012

I installed TFS Server 2013 and I configured Sql Reporting Services after the TFS installation. All went well until I saw that Reporting Services is not seen by the TFS (in the browser, no url for reports are available) even if the wizard is showing me that Reporting Services are configured and enabled in TFS. When I follow the Reporting Services Url, I see that no TFS reports were created.
Has anyone else had this problem? Does anyone know the answer?
Employees had already introduced data into TFS so I can't just reinstall the server.
Please help!

Grab the TFS Power Tools and download the process template from the TFS server and then use:
tfpt addprojectreports
/collection:"http://MyServer:8080/tfs/DefaultCollection"
/teamproject:MyProject /processtemplate:"TemplateName"
More details here:
Upload reports to a team project

Related

SharePoint integration not working after TFS 2010 to TFS 2017 upgrade for old sites. TFSRedirect.aspx error

We upgraded a site from TFS 2010 to TFS 2017 to new infrastructure including the TFS, SQL, SharePoint and Reporting Services.
Everything is working ok except for old SharePoint portal sites.
They initially appeared to be working but were in fact being redirected to the old Reporting Services site. We did tell TFS about the new SharePoint and Reporting using instructions here: https://msdn.microsoft.com/en-us/library/dd386320(VS.100).aspx
However, that still didn't resolve. So we tried to add &tf:ClearCache=1 to the TFSRedirect URL thinking that maybe it was caching the old URI. However, now whenever we try to access that portal all the webparts are broken and when we try to access anything with a TFSRedirect it gives an error.
Error=TF250008: This SharePoint site is not currently associated with a team project in Team Foundation Server. However, we have done what we thought was requried (URL above). What are we missing?

Login prompt in deploying report to SharePoint 2013 in integrated mode

I have sharepoint 2013. I have one SQL instance in sharepoint integrated mode and another instance in SSRS native mode on my server.
I get the login failure error.
I am dealing with this failure that is explained in the following solutions. But non of them solved my problem:
I did this solution:
https://stackoverflow.com/a/1445068/779408
and this:
http://ybbest.wordpress.com/2011/08/04/how-to-fix-%E2%80%9Cnot-able-to-deploy-report-to-sharepoint-2010-in-integrated-mode%E2%80%9D/
then I tested this solution:
http://www.thorntontechnical.com/tech/sharepoint/sharepoint-2010-ssrs-integrated-mode-deploy-login-prompt#.U5vQj7EmFKb
and implemented the solution in this:
https://sharepoint.stackexchange.com/questions/16656/not-able-to-deploy-report-to-sharepoint-2010-in-integrated-mode
Now I have the following web application and its Document library
http://test.local:44444/sites/sc1/Reports
But I can not deploy my reports on it.
What should I do now??
This issue normally occurs due to incomplete installation. Ensure that SQL Server Reporting services Add-in for sharepoint is installed. If not, run SQL Server setup again to install the missing add-in. If SharePoint 2013 is missing service pack 1, it may cause errors during configuration.
I would suggest you make use of the release configuration manager. You can create releases such as
LOCAL
REPORT_TESTING
REPORT_STAGING
PRODUCTION
SOME_SHAREPOINT_DEPLOYMENT
Each release type contains it's own instance of configuration values. This would allow the release type to control the deployment. If you are not using SharePoint locally then you can set the LOCAL release configuration to the standard SSRS values on your local machine.
this issue happening when you deployment the SSRS reports on SharePoint mode and configure FBA on the SP server
To solve this issue you must extend the Web Application that include BI Center
I have been facing the same issue,
When creating a new service application in SharePoint using SQL Server Reporting Services Service Application, I forgot to check the Web Application to be Associated.
Solution:
After I checked the Web Application & updated the service application properties, its Working.
Hope it helps someone...

TFS 2013 error TF218017 when attempting to create new team project with SharePoint 2013 Integration

Problem summary:
I have just built a new TFS 2013 environment for my organization. On my first attempt\test creating a new team project using Visual Studio 2013, I receive the following error at the final stage (Finish button):
"TF218017: A SharePoint site could not be created for use as the team project portal. The following error ocured: Server was unable to process request. ---> The user does not exist or is not unique.---> The user does not exist or is not unique."
I have found several other posts with folks encountering this same error but the proposed solution seems to always be to change the authentication mode in SharePoint to classic which is not available in SharePoint 2013.
The error message implies that this is permissions related. However, it is a little baffling due the fact that when I created a new TFS Project collection using the TFS Admin console it created a new site collection in SharePoint with no issues. I don't understand how my permissions would allow me to create a site collection but not place sites under the site collection.
Here are some details about my setup:
TFS 2013 running on Windows Server 2008 R2 Enterprise
SharePoint 2013 Foundation (separate server within same domain as TFS
server)
TFS Service account is a Site collection admin on the SharePoint site
collection
My AD account is a Site Collection admin on the SharePoint site
Collection
TFS Service account is a Farm Admin in SharePoint
My AD account is a Farm Admin in SharePoint
The TFS2013 Server is also a Farm Admin in SharePoint
No problems were encountered during installation of TFS 2013
TFS Server is used solely for TFS - nothing else is hosted here.
TFS Extensions For SharePoint have been installed on all servers in
the SharePoint 2013 Farm
TFS Server fully updated as of 1/17/2014
workstation fully updated as of 1/17/2014
Details on what I have attempted/researched so far:
Confirmed with my networking staff that there are no firewall\blocked ports
issues between TFS Server and SharePoint Servers
For the time period in which I was trying to create the new team
project there are no errors\warnings in the event viewer on my local
machine, SharePoint servers, or the TFS Server
When running Fiddler on the TFS server while trying to create the new
Team Project - I am seeing no traffic at all between the TFS server
and the SharePoint server.
my workstation has no open connections to any of the servers in question when trying to create the Team project
Cleared cache on my workstation at: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\4.0\Cache and C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\5.0\Cache
Verified nothing in cache on TFS Server at: C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v12.0
Performed IIS reset on TFS Server
Re-start on TFS Server
Team Foundation Server Best Practices Analyzer (it says "SharePoint products is not installed", I'm suspecting this is because SharePoint is installed on another server)
Installed Visual Studio 2013 Update 1.
I apologize if this is in bad form but I have also posted this on the msdn forum: http://social.msdn.microsoft.com/Forums/vstudio/en-US/0758f52d-bf03-44e4-96aa-b60468395914/tf218017-cannot-create-sharepoint-2013-site-from-tfs-2013?forum=tfsgeneral
I am reaching the bounds of my skill set on this one. Any help\ideas would be greatly appreciated. Thanks!
Update:
Well, unfortunately I had to break down and call tech support from an un-named large tech company for assistance on this. Some changes were made to our SharePoint environment in the process which coincided with the SharePoint farm "going down". I am not sure if the problem on the farm was a coincidence or related to my changes but the end result is that my SharePoint people are now skeptical of my TFS integration etc... so I was forced to do a default install of SharePoint on the TFS box. I will leave this post up for others with similar issues to discuss unless that is in bad form. Thanks to all who tried to help with this.
Here are some additional items I would check:
Make sure you start VS 2013 elevated (Right-click when opening and choose 'Run As Administrator') when creating a team project.
If possible, see what happens if you try from a different computer or the server itself using Team Explorer.
Ensure that the user that you are attempting to create the team project with has enough permissions in SharePoint (you can make the account a site collection admin on the site collection in question).
The user should be a TFS Server Administrator or Team Project Collection Administrator.
Make sure that user account has Content Manager rights in the related Reporting Services folder as well, just in case.
Go to the your SharePoint site collection and attempt to create a site in it manually as the account that you are trying to create the Team Project with; when you perform this, make sure you create it with one of the team site templates that TFS installed (like the Agile or CMMI); If you encounter errors this way it may help you narrow down the problem.
Don't forget to review the event logs on the machines involved.
Okay, I finally go to take another crack at this against my SharePoint enterprise environment and got it to work: The key was to simply remove Anonymous Authentication from the SharePoint web application and it worked!
Access the SharePoint web site collection (for example server/site/DefaultCollection) and add your user or group on Site Collection Administrator.

TFS Error after migration - TF250016 on Reports Site in Sharepoint

Good day all,
We recently migrated from TFS2008 to TFS2010. We migrated our TFS_name databases and our WSS databases. We followed the migration steps and our upgrade was successful, except for a single piece regarding the project sites.
Whenever I go into a team project portal, I receive the following error when trying to access the "Reports" site.
TF250016: No access rights have been granted for the following site: http://<tfsserver>/Sites/<project portal site>. You must grant access rights between the SharePoint Web application and Team Foundation Server. You must also associate this site with reports and dashboards for a specific project in Team Foundation Server. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=147580).
I have gone through the TFS upgrade steps and made sure we followed every step and we are running of ideas. Can anyone point me in the right direction? We didn't notice this error as we are not using reports at this time, but it's something we would like to implement in the future.
Thank you
Edit
(to read in the comments)
You did a move from one server to another and upgrade your TFS Server.
It's most likely you didn't follow the "how to move a TFS from one hardware configuration to another" procedure, then you'r SQL Report Server is down or incorrectly configured (the SQL Connection strings in the Data Sources configuration are incorrect).
Follow the procedure I gave you for the SQS Server Resport Service part and you should be fine.

Accessing TFS API from machines without Team Explorer

Can I use TFS API in my code and deploy the code in the machine where Visual Studio or Team Explorer doesn't exist?
I found this, which says I shouldn't do that.
Any help on this? Thanks!
No you can't, when you develop client application for the TFS, this means you need the run time files for this API which is exists in the Team Explorer.
You could use the new OData API, or the standard WebService API (officially unsupported) to connect to TFS without the need for the SDK or Team Explorer on the machine.
And there's the Java API's that ship with Team Explorer Everywhere 2010 SP1, which are supposedly easier to use in stand-alone fashion than the .NET API's that require Team Explorer to be installed.
Do note that in order to follow the proper license terms, you generally do need to have a TFS CAL for every machine/user connecting to TFS.

Resources