Why does Reporting Services in SharePoint integration mode require a minimal install of SharePoint?

  • Why does Reporting Services in SharePoint integration mode require a minimal install of SharePoint? ngm

    I have a two machine set-up, with MOSS 2007 installed on one server (Machine A), and SQL Server 2008 installed on the other (Machine B).

    In order to run SS Reporting Services in SharePoint integration mode on Machine B, I've read that I need to perform a minimal install of SharePoint on Machine B, and am wondering why.

    From a couple of error messages I see that it seems like Reporting Services in integration mode makes use of the SharePoint Object Model, but I haven't explored any further.

    So, purely just out of interest, why is it that I need to have a minimal SP install if my report server is on a separate machine from main SP install?

  • Reports that are deployed to the Report Server are actually stored in Sharepoint document libraries in integrated mode, and SSRS uses the Sharepoint object model to access those libraries.

2007 reports reporting-services sql-server
Related questions and answers
  • On a single Windows 2008 Server I'm running SharePoint 2007 Enterprise (SP2, December 2009 CU) and SQL Server 2005 (SP3, CU 7). Authentication is NTLM. I've been trying to get SharePoint Reporting Services integration to work without success. The Reporting Services configuration tool has all ticks. It is possible to browse to the ReportServer IIS directory and see a list of SharePoint sites... and SharePoint (as it is impossible to only uninstall the Reporting Services component with SQL Server 2005) used the same service account for all SQL services and the same for all SharePoint services given all

  • I am trying to test a SharePoint package installation on a VPC environment. I have set up an NLB cluster with two VPC's. One problem may be that I have only one network card configured on the VPC's.(using multicast) When we run the install on one of the NLB web we are unable to give the nlb address, when we give the address of one of the servers, the package only gets installed on that server. Should we run the package from a machine outside the cluster, or is there another way to fix this?

  • We have two servers: Server1: MOSS 2007 content with ESP web parts Server2: SP 2010 acting as query server We need to crawl the Server1 content from Server2, and installed ESP web parts on Server1 need to refer to Server2 as the query server. So user queries from MOSS 2007 go to the SP2010 box (where content is crawled) and return the result on the MOSS 2007 server. Please advise?

  • Powershell as domain administrator (so I have rights to access domain accounts) I didn't install SQL Server 2008 KB 970315 x64, because I'm running R2 version - as I understand this is SQL Server 2008 SP2...I'd really like to prepare development environment for Sharepoint 2010. This is what I did: I installed Windows 7 x64 I installed VMWare Workstation Created a VM domain controller based on Windows Server 2008 R2 Server Core run the VM and joined my Windows 7 machine to that domain Installed SQL Server 2008 R2 on Wind7 machine Followed instructions http://msdn.microsoft.com/en-us

  • like to create a Search Service Application after installing Search Server Express 2010. Do I need to run the Farm Configuration Wizard and install the below if I can create a Search Service... migrated WSS v3 to SharePoint Foundation 2010 and then installed Search Express 2010 on top of it. I am logged in with an account that has full farm administration access. Update 2: I migrated WSS v3 to Sharepoint Foundation 2010 and then installed Search Express 2010 on top of it. Update 3: Yes the farm admin acct is the member of the local admin. What services are required to start to have

  • For the past couple of days I have been setting up a brand new SharePoint Server 2010 running on top of Server 2008. This installation is intended to be used with Active Directory and will be used as an intranet for our organization. Everything installed correctly and the SharePoint install itself went fine. I'm at the point now where I am running the SharePoint 2010 Products Configuration Wizard. The thing that is bothering me is that the configuration wizard runs without me needing to enter any information (Service Accounts, Database Server, Admin Site Port, etc). Should I have done

  • Running SharePoint on .NET 4 Michael Broschat

    I installed .NET 4 on the server I would be installing SP 2010, and everything worked out just fine. Later, I learned that just putting 4 on a machine doesn't change the IIS setting from .NET 2 to (the new) 4. I tried that, and get HTTP 500 errors. PUtting IIS back to .NET 2 fixes the problem, but I suspect there must be a way to use .NET 4?

  • I've got 3 servers: - DB1 - SharePoint1 - SharePoint2 On SharePoint1 I've installed WSS, using DB1 as database. Now I want to install WSS onto SharePoint2 and use DB1 as database storage as well. My question is: Does it conflict to have the databases from two SharePoint installations located on the same instance of the same SQL server? The two SharePoint installations have nothing in common except they use the same SQL server (both not the same databases, of course). I can't create a new instance on the SQL server...

  • I have a new SharePoint 2010 server farm that I'm trying to configure. Installation went fine. But I'm having trouble getting the user profiles to import. I've created the User Profile service application, and the two user profile services are running. However, whenever I try to create a synchronization connection to our AD servers, I'm getting the following error: "The operation was aborted because the client side timeout limit was exceeded." In the SharePoint logs, when I filter based on the correlation ID, I get the following messages: Name=Request (POST:http://poc-bi-sp:8080/_layouts

Data information