We have assumed maintenance of a legacy 32bit application. I installed TFS 2008 to use in maintaining the project.
We will never use reporting or sharepoint. I cant create a project because of issues with SSRS.
(The Project Creation Wizard encountered a problem while creating reports on the SQL Server Reporting Services on OHSENSS801. The reason for the failure cannot be determined at this time. Because the operation failed, the wizard was not able to finish creating the SQL Server Reporting Services site. )
How can I disable reporting and sharepoint in TFS 2008?
Thank you.
Unlike TFS 2010 and above version, you have to install the SharePoint components for TF2008.
TFS2008 is a very old server version and out of support for a long time. You could use TFS2010 instead, the SharePoint is no longer a prerequisite when you install TFS2010. You can go for TFS2010 Basic Configuration which is the most compact TFS installation possible.
In Basic Configuration, SharePoint and Reporting Integration will not be possible. It will install and configure Source Control, Work Item tracking and Build Services only.
Highly recommend you to move to a newly versioned TFS server. If you insist on using TFS2008, you could try to troubleshoot the configuration of SQL Server Reporting Services. Details please refer this thread in MSDN: SQL Server Reporting Services is not configured correctly
About how to remove Sharepoint and Reporting Services from TFS, you could go through this question. However, afraid removing these components, you will still not able to create team project. After all, if it will work, there is no need to be a prerequisite for installing TFS2008.
Related
I have installed SQL Server Data Tools in standalone mode (SSDT 2012 11.0.3000.0) i.e. without it being part of any SQL Server or Visual Studio Package. All I'm seeing now in SSCM is Integration Services running. There is no SSRS, SSAS or for that matter not even Database Engine and Agent services running. Even when I create any analysis or reporting service projects, all I see is SSIS toolbox over there. I haven't done this kind of standalone installation before and don't know if I might be missing something. Really appreciate some help here
Thanks,
Pratik
I have had some problems with Team Foundation Server 2012.
I have managed to recreate the reporting services and now have a SQL Server Reporting Services page to go to from TFS.
However it does not have any reports in it.
How do I go about recreating the ones that come with the process template?
TFS is being used for source control and planning at the moment so I don't want to start from scratch.
If your TFS had already been connected to SSRS before creating the team project, these reports would have been created automatically. Since you have connected it after the fact, I would recommend you use the TFS Power Tools (make sure you download the correct version for you TFS installation) and run the tfpt addprojectreports command. You can run the command with the /? switch for details on how to use it.
I have been working for a client who run SQL Server 2008 in their live environment. I had been working onsite for a period but now work from home. However, due to security, I cannot connect to the live setup, I can only connect to a test server. This server runs SQL Server 2012. I script any code and send it to the office for someone to deploy. The problem I have is I am now doing some reporting services work. They are only pretty basic reports, tablix controls, nothing fancy. Is is possible to build on 2012 and deploy to 2008? Can I do something with the .rdl file to make this work or is it not going to be feasible?
Thanks in advance
In the Properties of the ReportServer Project in Visual Studio you can set the target server version.
Right click the Project in the Solution Explorer pane and set the TargetServerVersion Property to the required version. This works for reports SQL Server Reporting Services 2008 onwards. The designer will then manage what features are available to avoid using features from a later version of SSRS.
The .rdl files are nicely formated XML. You can use your favorite diff tool to compare reports generated in either version of the tool.
I'm pretty sure that Microsoft doesn't support moving a newer RDL to an older version server.
There were huge changes to the .rdl format between 2005 and 2008, moderate changes between 2008 and 2008R2, but I haven't really looked into 2008R2 versus 2012. From what I've seen these should be smaller changes yet.
If you do this you are off of the golden supported brick road. Since this server is production, and you don't have a good way to test this, I would find a 2008 server to develop with. I wouldn't want my name connected with the possible problems that could come up with a hack to move the rdl backwards.
I have a server that was configured by someone that is not on the company anymore and I need to check the TFS installation and enable that "dasboard" with reports, charts etc.
The only stuff working are: Source Control, issue tracking, web access.
As far as I could check, Reporting Services seems to be disabled (or not installed) and I don't know how to check SharePoint installation.
How can I verify and fix the TFS installation in order to make the reports work?
If Reporting Services are not installed or disabled, where can I install or enable it?
Use the Team Foundation Server 2010 Best Practices Analyzer included in the TFS Power Tools.
If you just open the TFS Admin Console, you can check for everything configured
SharePoint
Reports
Others
After that, start check this configuration per collection
If the SharePoint or Reporting not installed? You will need to install and configure them
For how to do this, there is a guide with videos on how to do enterprise installation, you can see the video of the SharePoint and Reporting only if you want, it will told you what exactly you will need to do?
http://tfs10enterprise.codeplex.com/releases/view/78529
I am trying to find out if it is better to deploy Reporting Services and Sharepoint Server on the same Server or not and what would the reason be for either case. Any help will be greatly appreciated.
The most common reason that Reporting Services is not integrated with SharePoint is licensing restrictions. I am not a licensing expert, but I believe any server on which Reporting Services is installed must have a SQL Server license. Since SQL Server is usually installed on servers other than the SharePoint app servers, this involves extra SQL costs.
SharePoint and SSRS integration allows reports to be stored in a SharePoint library and provides an easier way to store report output (subscriptions) to SharePoint libraries.