Reporting Services - All Datasets Broken

Hello there.
We’re having some problems with Reporting Services on a prod site and I was hoping someone might be able to offer a suggestion.
Here are the facts :
We have a SP Server 2010 (not foundation) farm which uses Reporting Services. There is 1 web / application server and 1 SQL server. Reporting Services 2008 R2 is installed on the SQL box.
Sometime in the last 2 weeks the reports all stopped working (last known report run 2 weeks ago). This was picked up yesterday. I'm not aware of anything being manually changed in the farm to cause this.
The reports report directly on SP lists using datasets with SharePoint data connections. There is one dataset per list.
The SQL / Reporting Services box has previously had SP installed on it (Ouch! Inherited system – not sure why SP was installed on SQL box).
A few weeks ago we stopped all SP services on the SQL box but did not uninstall SP from it. This did not affect reporting at the time.
When a report fails, we see this message in the UI :
Looking in the reporting services log messages are like the following, one per dataset :
Query execution failed for dataset 'DataSet1'. ---> System.ArgumentException: Feature '22d91f57-00d1-4e0b-9c04-863a82deaa07' for list template '10001' is not installed in this farm.
The operation could not be completed.
This happens for all datasets for all reports. All datasets are complaining that the feature for the list the data set uses is missing. These are features with list definitions / instances for the lists used in the reports.
The initial thought was that someone had renamed a field or similar, but this would only impact that one dataset. What we are seeing is that
all datasets simultaneously broke.
The features Reporting Services are complaining about are indeed activated in SP in the relevant webs.
On the SQL box the folders for the features Reporting Services are complaining about are not present in the 14 hive at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES, but then as far as I know they never were. On
our dev environment we deleted these feature folders but this didn't reproduce the same error.
We modified an unrelated SP list view yesterday via the SP UI. It’s unlikely but I wonder if there is some kind of list definition XML / voodoo behind the scenes that was interrupted by this.
If you open the broken report in Report Builder directly from SP (via the list context menu), you can run the datasets OK, and do a test connection for the data source - but if you run the report itself you get the usual error. If I use Report Builder on
my local machine to try to save to the web where the reports are stored, I get one of the “feature…is not installed in this farm” errors. I can’t even browse to that web in Report Builder without getting the error.
Things I've tried so far (my infrastructure experience amounts to restart things until they work):
App pool recycle web server.
IISReset web server.
Restart reporting service on SQL box.
Delete the view I thought might have been somehow related.
In summary I have no idea what the root cause is here or what has changed recently. I’m a
programmer and someone else who is no longer available set up this environment so I’m a bit stuck!
Thanks for reading.
Lee

We've resolved this.
It turns out the features it was complaining about really were missing on the Reporting Services box and needed to be present. I wrongly concluded this wasn't the problem initially when we deleted these features on a dev box, restarted a few things and reports
didn't break. I guess something was still being cached somewhere.
Best guess as to why the features went away is that when we disabled all of the SP services on the reporting services box via Central Admin, one of these (probably SharePoint Foundation Web Application), all custom features / solutions were removed
from the box.
Moral of the story I think is make sure your reporting services box is a valid part of the SP farm and has all required features present.
Cheers
Lee

Similar Messages

Is the Export Quality for PDFs in Reporting Services 2005 only 96DPI?

I have been fighting with Reporting Services all day, and despite setting the PDF output quality to 300DPI, I have noticed that the image quality appears to be only 96DPI. I've noticed this because images with a size set for 300DPI are too large for the page, and images set for 96DPI fit just right.
Could someone please tell me if this is a limitation of Reporting Services 2005, or am I just doing something wrong?
I need to know this because I am up against a deadline with this project. I had ran several tests with Reporting Services but had never had assumed there would be problems with image quality.
Is there any other product that offers similar features to Microsoft Reporting Services that you could recommend?
My luck has not been very good with this project, and I'm assuming the response is going to be 96DPI is all that is supported...

OK, I have managed to get higher quality images from the PDF renderer. Here is what I have found:
1) The PDF renderer in Reporting Services 2005 will size all images that it is given at 96 DPI no matter what DPI the image is when you pass it to the renderer. That means that a 300 DPI image or even a 600 DPI image will be sized in the PDF as if it is only 96 DPI. That means your high DPI image will render much larger than you expect.
So you might expect a 300 DPI image that is 6.5 inches wide to render properly at 1950 pixels. Yet, the PDF renderer will size it as it were 96 DPI which would make the image 20.3 inches long!
2) There is good news though. Despite sizing the images as if they were 96 DPI, the PDF renderer appears to render higher DPI images at a higher quality than 96 DPI. So despite the sizing being wrong, the image actually is rendering at a higher quality.
This means that you should size the image to the proper number of inches based on 96 DPI calculations. Then you can use Bitmap.SetResolution to set your images to at least 300 DPI. That should give you a higher quality image that is the proper number of pixels to fit properly in your report.
I am able to do all of this sizing dynamically because I am using objects as my data sources, but I am sure there are VB functions you could use in the report itself to accomplish the same task.
It is late, and I've been at this project all day long, so forgive me if I have explained anything poorly or gotten any concepts long. Yet, at this late hour, I believe this is what the renderer is doing.
I hope this helps someone else in the future, or at least points them in the right direction.

[Forum FAQ] How do i use xml stored in database as dataset in SQL Server Reporting Services?

Introduction
There is a scenario that users want to create SSRS report, the xml used to retrieve data for the report is stored in table of database. Since the data source is not of XML type, when we create data source for the report, we could not select XML as Data Source
type. Is there a way that we can create a dataset that is based on data of XML type, and retrieve report data from the dataset?
Solution
In this article, I will demonstrate how to use xml stored in database as dataset in SSRS reports.
Supposing the original xml stored in database is like below:
<Customers>
<Customer ID="11">
<FirstName>Bobby</FirstName>
<LastName>Moore</LastName>
</Customer>
<Customer ID="20">
<FirstName>Crystal</FirstName>
<LastName>Hu</LastName>
</Customer>
</Customers>
Now we can create an SSRS report and use the data of xml type as dataset by following steps:
In database, create a stored procedure to retrieve the data for the report in SQL Server Management Studio (SSMS) with the following query:
CREATE PROCEDURE xml_report
AS
DECLARE @xmlDoc XML;
SELECT @xmlDoc = xmlVal FROM xmlTbl WHERE id=1;
SELECT T.c.value('(@ID)','int') AS ID,
T.c.value('(FirstName[1])','varchar(99)') AS firstName,
T.c.value('(LastName[1])','varchar(99)') AS lastName
FROM
@xmlDoc.nodes('/Customers/Customer') T(c)
GO
P.S. This is an example for a given structured XML, to retrieve node values from different structured XMLs, you can reference here.
Click Start, point to All Programs, point to Microsoft SQL Server, and then click Business Intelligence Development Studio (BIDS) OR SQL Server Data Tools (SSDT). If this is the first time we have opened SQL Server Data Tools, click Business Intelligence
Settings for the default environment settings.
On the File menu, point to New, and then click Project.
In the Project Types list, click Business Intelligence Projects.
In the Templates list, click Report Server Project.
In Name, type project name.
Click OK to create the project.
In Solution Explorer, right-click Reports, point to Add, and click New Item.
In the Add New Item dialog box, under Templates, click Report.
In Name, type report name and then click Add.
In the Report Data pane, right-click Data Sources and click Add Data Source.
For an embedded data source, verify that Embedded connection is selected. From the Type drop-down list, select a data source type; for example, Microsoft SQL Server or OLE DB. Type the connection string directly or click Edit to open the Connection Properties
dialog box and select Server name and database name from the drop down list.
For a shared data source, verify that Use shared data source reference is selected, then select a data source from the drop down list.
Right-click DataSets and click Add Dataset, type a name for the dataset or accept the default name, then check Use a dataset embedded in my report. Select the name of an existing Data source from drop down list. Set Query type to StoredProcedure, then select
xml_report from drop down list.
In the Toolbox, click Table, and then click on the design surface.
In the Report Data pane, expand the dataset we created above to display the fields.
Drag the fields from the dataset to the cells of the table.
Applies to
Reporting Services 2008
Reporting Services 2008 R2
Reporting Services 2012
Reporting Services 2014
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I have near about 30 matrics. so I need a paging. I did every thing as per this post and it really works for me.
I have total four columns. On one page it should show three and the remaining one will be moved to next page.
Problem occurs when in my first row i have 3 columns and in next page if I have one columns then it show proper on first page but on second page also it gives me three columns insted of one. the first column data is exactly what I have but in remaining two
columns it shows some garbage data.
I have data like below.
Metric ColumnNo RowNo
1 1
1
2 2
1
3 3
1
4 1
2
so while grouping i have a row parent group on RowNo and Column group on ColumnNo.
can anyone please advice on this.

Reporting Services through ISA server for All Authenticated Users

Hello colleagues.
I have MS SQL 2012 server with Reporting Services and it work via link:
https://reports2.domain.com/reports
In LAN all work fine, but I want publish this resource via ISA for All Authenticated Users.
When in publish rule I configure (in Condition) "All users" - all work fine, but when I configure "All Authenticated Users" - I have trouble on web form on
https://reports2.domain.com/reports/Pages/Report.aspx?ItemPat... - scripts not work, because it run how "anonymous" (I see on ISA logging) and ISA block scripts.
I can't use "All Users", because it's not secure.
Maybe somebody publish Reporting Services through ISA server for All Authenticated Users?
OR maybe - how on Reporting Services configure Negotiate authenticated for scripts?

Hi Alexander,
All users or applications who request access to report server content or operations must be authenticated using the authentication type configured on the report server before access is allowed. The AuthenticationType named RSWindowsNegotiate is supported
by Reporting Services. To configure Windows Authentication on the Report Server, please see:
http://msdn.microsoft.com/en-us/library/cc281253(v=sql.110).aspx
Besides, we can publish report server via ISA server. Please note that you should use a new web port number with a new listener which shouldn’t be used by other web site for report server. Reference:
http://social.technet.microsoft.com/Forums/forefront/en-US/1cc68996-1ce6-4d88-a30d-2bfd13fba06e/how-to-publish-ssrs-2008-through-isa-2006?forum=Forefrontedgegeneral
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support
Katherine thanks for answer.
Report Server service started as Domain account.
I have in RSReportServer.config this:
<Authentication>
<AuthenticationTypes>
<RSWindowsNegotiate />
</AuthenticationTypes>
<RSWindowsExtendedProtectionLevel>Allow</RSWindowsExtendedProtectionLevel>
<RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
In web.config I have this:
<authentication mode="Windows" />
<identity impersonate="true" />
I can go (from Internet through ISA) to
https://reports2.domain.com/reports and LogOn Authentication is work, but scripts not work, because it run how "anonymous" (I see this on ISA logging) and ISA block scripts.
Do you know where in Reporting Services configure run scripts with Negotiate authentication?

[Forum FAQ] How do I disable all subscriptions without disabling Reporting Services and SQL Server Agent?

Introduction
There is the scenario that users configured hundreds of subscriptions for reports. Now they want to disable all the subscriptions, but Reporting Services and SQL Server Agent service should be enable, so the subscriptions will not delivery reports to users
and users could run the reports and create jobs on the server.
Solution
To achieve this requirement, we need to list all subscriptions and their schedules by running query, then use loop statement to disable all the subscription schedules by Job name.
On the Start menu, point to All Programs, point to Microsoft SQL Server instance, and then click SQL Server Management Studio.
Type Server name and select Authentication, click Connect.
Click New Query in menu to open a new Query Editor window.
List all subscriptions and their schedules by running the following query:
Use ReportServer
go
SELECT   c.[Name] ReportName,
s.ScheduleID JobName,
ss.[Description] SubscriptionDescription,
ss.DeliveryExtension SubscriptionType,
c.[Path] ReportFolderPath,
row_number() over(order by s.ScheduleID) as rn
into
#Temp
FROM
ReportSchedule rs
INNER JOIN Schedule s ON rs.ScheduleID = s.ScheduleID
INNER JOIN Subscriptions ss ON rs.SubscriptionID = ss.SubscriptionID
INNER JOIN [Catalog] c ON rs.ReportID = c.ItemID AND ss.Report_OID = c.ItemID
select * from #temp
Use the loop statement to disable all the subscription schedules by Job name:
DECLARE
@count INT,
@maxCount INT
SET @COUNT=1
SELECT @maxCount=MAX(RN)
FROM
#temp
DECLARE
@job_name VARCHAR(MAX)
WHILE @COUNT <=@maxCount
BEGIN
SELECT @job_name=jobname FROM #temp WHERE RN=@COUNT
exec msdb..sp_update_job @job_name = @job_name,@enabled = 0
SET @COUNT=@COUNT+1   P
RINT @job_name
END
PRINT @COUNT
Reference
SQL Agent – Disable All Jobs
Applies to
Reporting Services 2008
Reporting Services 2008 R2
Reporting Services 2012
Reporting Services 2014
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Thanks,
Is this a supported scenario, or does it use unsupported features?
For example, can we call exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b64ce7ec-d598-45cd-bbc2-ea202e0c129d'
in a supported way?
Thanks! Josh

Reporting Services - Content Manager shows all reports for all domain users even without permissions

I have installed
reporting services 2008 in: Site
Settings option / Security only 3 users
have added:
BUILTIN \ Administrators
System Manager
MYDOMAIN \ user1
System Manager, System User
MYDOMAIN \ user2
System Manager, System User
I have the same settings in the "start
up" folder and inside the folder
where are my reports, however if I authenticate
any user with different domain
to user1 and user2 can see all content
of the report manager can even
manage it.
Help me, greetings
Jenny

however if I
authenticate any user with
different domain to user1 and user2 can see
all content of the report manager can
even manage it.
Hello,
Did you means that other domain user account (Other-Domain\user3) can access reports on the Report Manager without grant any permission? As per my understanding, it is not possible. SQL Server Reporting Services uses Windows Authentication
defaultly to determine who can perform operations and access items on a report server.
Based on your description, you grant the local Administrators group and two domain users with system-level role: System Administrator.  System-level role assignments grant access to global tasks and permissions that apply to a report
server site, That's may cause the user can access and manage all contents on the Report Manager.
If you want to set permissions for accessing conntents on Report Manager, you can just specify itme-level role assignments.For example, if you grant user with Browser role on a report, the user can view report and report properties, but cannot edit
report properties.
Reference:
Lesson 1: Setting System-Level Permissions on a Report Server
Lesson 2: Setting Item-Level Permissions on a Report Server
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

What all things I need to install for Report Services?

I just want to use Oracle 9IAS Release 2 for Reports purpose.Along with RDF reports I nee to use the report service for JSP reports also.
So just I want to know what all things I need to install from Oracle 9IAS CD?
Any suggestion.........

2ManyDogs wrote:Read the Beginners' Guide.
+1
I've used Linux for several years, but only recently installed Arch for the first time. I installed Bridge Linux, Chakra, and later ArchBang, and after getting a feel for pacman (I think it's great!) and, with Bridge and ArchBang, the Arch repos, I was convinced that I wanted to go ahead with an Arch installation. Not sure if this is an option for you or not, but I actually tried two "test" installations on a spare computer first, taking detailed notes, with tabs in my browser (on another computer) opened to the Beginners' Guide and the "official" Installation Guide. I also kept the Bridge and ArchBang installations; kinda nice to be able to take a look at them sometimes to see how things are set up there. I don't know if Arch users would recommend this type of approach, but it has worked out well here.

Latest Ccritical Update seems to have broken Reporting Services in SharePoint

The error I'm getting in my logs is: Cannot find site lookup info for request Uri
http://spapp-prod0:32843/29869a14ea294b42bf388f54c08b252d/ReportExecution.svc.
Here is a screen grab of the actual error. Can anyone help?

As I see the error,it seems that the RSS dependency is missing or not working after the patch.please check the links below for the same issue.
http://forums.asp.net/t/1496930.aspx?Could+not+load+file+or+assembly+Microsoft+ReportingServices+ProcessingObjectModel+
http://social.technet.microsoft.com/Forums/sharepoint/en-US/f38b205b-df47-46fe-aca2-ee7bf83f3d88/ql-server-reporting-services-2012-sharepoint-integrated-mode-error-when-viewing-report?forum=sharepointadminprevious
Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

How to merge multiple datasets in reporting services

we are having difficulty in developing a report because the dataset we needed for the report is coming from 2 separate stored procedure. these 2 stored procedure are returninga single table each, and we need 5 columns in the first table and 4 columns from
the second table, and present these 9 fields into a table in the report.
To give an illustration, let's say that my first stored procedure returns the following 5 fields from the customer table: first name, last name, address, email, phone. While, the second stored procedure returns the following 4 fields from the orders table:
item name, quantity, unit price, discount. The two tables are related by customer_id field which is present in both tables. Customer table has a one to many relationship with orders table.
This could have been easily implemented by using an inner join and writing a sql query. However, due to business requirements we need to generate the report using the 2 stored procedure mentioned. Please let me know if there is any workaround for this. We
are using SSRS 2012. Many Thanks in advance

I can see 2 ways of achieving this.
1. Using LookupSet function for 1:N relationship.
Refer
http://www.bidn.com/blogs/DustinRyan/bidn-blog/2037/lookup-and-lookupset-functions-new-in-ssrs-2008-r2
Refer http://technet.microsoft.com/en-us/library/ee240819.aspx
2. Working with both stored procedure and creating a new dataset. For example, Create temp tables and then,
INSERT INTO #Table1 EXEC PROC1
INSERT INTO #Table2 EXEC PROC2
SELECT * FROM #Table1 A INNER JOIN #Table2 B ON A.CustomerID = B.CustomerID
Refer
http://stackoverflow.com/questions/12621469/sql-server-insert-stored-procedure-results-into-table-based-on-parameters
Regards, RSingh

Reporting Services username and password prompting

We have several branch office locations and one reporting services server. All of the branch office locations can access the reporting services server, but we have one location for the passed week, each time they make a connection to this server, it prompts
them for a username and password and will not allow them to connect even if the correct username and password is correct.
I have tried adding the server to the IE intranet/trusted site list. Set IE security on all zones to automatically logon with current username and password.
What is strange is that this is the only branch office site that is having this issue. It is almost like kerberos is broken for this site location only.
DOes anyone has any suggestions what could be causing this problem for all computers in this one location. Nothing has changed on their local servers nor have we pushed any updates to the machines.

Hi bubba1984,
As per my understanding, I think this issue is caused by Kerberos authentication. Kerberos is an authentication protocol that allows clients that create authentication tokens to associate a specific destination to that token. In the failure case, there is
a mismatch between the destination specified in the token and the report server process configuration. Due to this mismatch, the underlying Kerberos authentication scheme supported by Windows prevents report server from authenticating the user.
To fix this issue, please try to remove RSWindowsNegotiate and ensure RSWindowsNTLM is specified in the rsreportserver.config file. For more details, please take the following article as reference:
http://blogs.msdn.com/b/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Upgrade 2010 to 2013 with SQL Reporting Services

I'm getting ready to upgrade to 2013.
When I run the Test-SPContentDatabase I get:
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [ab6d9dad-e23c-ce4f-ff98-f6575a1ccf4c] (class [
Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportView
erWebPart] from assembly
[Microsoft.ReportingServices.SharePoint.UI.WebParts,
Version=10.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91]) is referenced [24] times
in the database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this web part.
Remedy : One or more web parts are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
web parts.
Locations :
Category : MissingAssembly
Error : True
UpgradeBlocking : False
Message : Assembly
[Microsoft.ReportingServices.SharePoint.UI.ServerPages,
Version=10.50.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91] is referenced in the
database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this assembly.
Remedy : One or more assemblies are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
assemblies.
Locations :
Category : Configuration
Error : False
UpgradeBlocking : False
Message : The [is.photomask.com] web application is configured with
claims authentication mode however the content database you
are trying to attach is intended to be used against a
windows classic authentication mode.
Remedy : There is an inconsistency between the authentication mode of
target web application and the source web application.
Ensure that the authentication mode setting in upgraded web
application is the same as what you had in previous
SharePoint 2010 web application. Refer to the link
"http://go.microsoft.com/fwlink/?LinkId=236865" for more
information.
Locations :
The first two have to do with reporting services. I'm trying to workout how to go about getting these errors to go away. I don't want to remove SQL reporting or migrate a broken site and fix it later. FYI it does migrate but reporting services
is of course broken.
So what I was wanting to do was to upgrade SQL Reporting Services for SharePoint 2010 from 2008 SQL to 2014 SQL first. This would be in the hopes that it would make the migration to SharePoint 2013 work as the assemblies would change to the proper
version.
Can anyone elaborate on my upgrade path?
I'm still looking up the "Claims Based" authentication thing. I've found an article on how to migrate it so not a big deal. I do wonder however if this is tied to the issue I saw with default.aspx and home.aspx being denied to all users
after I did migrate a content db.
David Jenkins

Hi David,
The following sections describe the basic steps needed to upgrade or migrate from 2008 versions of Reporting Services SharePoint mode to 2014 version.
SQL Server 2008 R2 to SQL Server 2014
Starting environment: SQL Server 2008 R2, SharePoint 2010.
Ending environment: SQL Server 2014, SharePoint 2010.
In-place upgrade is supported and there is no down time for your SharePoint environment.
Install the SQL Server 2014 version of the Reporting Services add-in for SharePoint on each web front-end in the farm. You can install the add-in by using the SQL Server 2014 installation wizard or by downloading the add-in.
Run SQL Server 2014 installation to upgrade SharePoint mode for each “report server”. The SQL Server installation wizard will install the Reporting Services Service and create a new Service application.
If you also want the ending environment to run SharePoint 2013, you need to complete a database-attach upgrade of the SharePoint 2010 to SharePoint 2013.
For more scenarios information, please refer to:
http://msdn.microsoft.com/en-us/library/ms143747.aspx#bkmk_sharePoint_scenarios
Per the supported combinations of SharePoint and Reported Services Components, I’d recommend you firstly upgrade Reporting Services to 2014, then upgrade SharePoint to 2013.
For more information:
http://msdn.microsoft.com/en-us/library/gg492257.aspx
The link below is the reference for migrating a Reporting Services:
http://msdn.microsoft.com/en-us/library/hh759331.aspx
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

SQL Server Reporting Services FAQ

Hi All,
This thread is a summary of the Frequently Asked Questions on SQL Server Reporting Services. We consolidate them and post here for your reference. If you have any further questions, please kindly start a new thread so that more community members, MVPs, and MSFTs can join the discussion and share their ideas. Thanks for your understanding.
Part I: SQL Server Reporting Services General Topics
1. How to migrate SQL Server 2008 Reporting Services to another computer?
2. How to combine connecting string via parameter?
3. How to install a 32-bit version of SQL Server 2005 Reporting Services on a computer that is running a 64-bit version of Windows?
4. Error of EXECUTE permission denied on object 'xp_sqlagent_notify'.
5. Security consideration for anonymous access to Report Server.
6. How to create a custom report template in Reporting Services?
7. Does Reporting Services support horizontal tables which have fixed rows and dynamic columns?
8. How to reset the page number back to 1 every time the report gets a group break?
9. How to open the drill- through report in a new browser window?
10. How to verify the version of SQL Server?
11. How to use multiple datasets?
12. How to upgrade report from SQL Server 2000 to SQL Server 2005?
13. Out of memory error when exporting reports to Excel.
14. How to improve PDF quality of the report exported in Reporting Services 2005?
15. How to enable the Select All option for a multi-value parameter?
Part II: SQL Server Reporting Services SharePoint Integrated Mode Topics
1. How to deploy reports to SQL Server Reporting Services in SharePoint Services integrated mode?
2. How to integrate SQL Server Reporting Services and SharePoint Services?
3. How to refer the reports on the Report Server in SharePoint Services?
4. How to manage user to view reports in SharePoint integrated mode?
5. What information is needed when posting questions regarding SharePoint integrated mode?
6. Is Report Builder available in SharePoint Integrated Mode?
PLEASE NOTE: Microsoft does not offer formal support for the communities you'll find here. Instead, our role is to provide a platform for people who want to take advantage of the global community of Microsoft customers and product experts. Microsoft may monitor content to ensure the accuracy of the information you'll find, but any information provided by Microsoft staff is offered "AS IS" with no warranties, and no rights are conferred. You assume all risk for your use.
Microsoft Online Community Support

1.        Question 3: How to install a 32-bit version of SQL Server 2005 Reporting Services on a computer that is running a 64-bit version of Windows?
Answer:
To install the 32-bit version of Reporting Services on a computer that is running the 64-bit version of IIS 6.0, we can follow these following steps:
1.       Uninstall the 64-bit version of Reporting Services.
Note: Side-by-side installations of 32-bit versions of Reporting Services and 64-bit versions of Reporting Services are not supported.
2.       Run the Dotnetfx64.exe file to manually install the .NET Framework.
The Dotnetfx64.exe file is in the Tools\redist\2.0 folder on the SQL Server 2005 Setup media. To download the Dotnetfx64.exe file, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=70186
3.       In IIS Manager, click Web Server Extensions.
4.       In the Details pane, right-click ASP.NET V2.0.50727, and then click Allow.
5.       Right-click Web Sites, and then click Properties.
6.       Click the ISAPI Filters tab.
7.       In the Filter Name column, click ASP.NET_2.0.50727, and then click Edit.
8.       Replace C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_filter.dll with C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll.
Note: The Aspnet_filter.dll file in the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ folder is a 32-bit version of the file.
9.       Click OK two times, and then close IIS Manager.
10.   At a command prompt, run the following command:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
11.   Install the 32-bit version of Reporting Services.
12.   After setup is complete, open IIS Manager, and then click Web Server Extensions.
13.   In the Details pane, right-click ASP.NET V2.0.50727 (32-bit), and then click Allow.
To install the 32-bit version of Reporting Services on a computer that is running the 64-bit version of IIS 7.0, follow these steps:
1.       Enable ASP.NET and IIS before you install Reporting Services.
2.       Open a command prompt. To do this, click Start, point to All Programs, point to Accessories, right-click Command Prompt, and then click Run as administrator.
3.       In the User Account Control dialog box, click Continue.
4.       Copy the following script:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
5.       In the upper-left corner of the Command Prompt window, right-click the command prompt icon, click Edit, and then click Paste.
6.       Press ENTER to run the script.
7.       Install the 32-bit version of Reporting Services. You must apply SQL Server 2005 Service Pack 2 (SP2) after you install Reporting Services in Windows Vista. If you install SQL Server 2005 Express Edition with Advanced Services, you can run SQL Server 2005 Express Edition with Advanced Services SP2.
For more information, visit the following Microsoft Web site:
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2
http://go.microsoft.com/fwlink/?LinkID=63922
8.       Reset IIS.
9.       Configure the report server for local administration. To access the report server and Report Manager locally, follow these steps:
a.       Start Microsoft Internet Explorer.
b.      On the Tools menu, click Internet Options.
c.       Click Security.
d.      Click Trusted Sites.
e.      Click Sites.
f.        Under Add this website to the zone, type http://servername.
g.       If you are not using HTTPS for the default site, click to clear the Require server certification (https:) for all sites in this zone check box.
h.      Click Add.
i.         Repeat steps f and g to add http://localhost, and then click Close.
10.   This step lets you start Internet Explorer either to localhost or to the network computer name of the server for both Report Server and Report Manager.
a.       Create role assignments that explicitly grant you full-permissions access. To do this, follow these steps:
b.      Start Internet Explorer by using the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator.
c.       Start Report Manager.
d.      Note By default, the Report Manager URL is http://servername/reports. If you are using SQL Server 2005 Express Edition with Advanced Services SP2, the Report Manager URL is http://servername/reports$sqlexpress. If you are using a named instance of Reporting Services, the Report Manager URL is http://servername/reports$InstanceName
e.      On the Home page, click Properties.
f.        Click New Role Assignment.
g.       Type a Windows user account in the following format: domain\user
h.      Click to select the Content Manager check box.
i.         Click OK.
j.        In the upper-right corner of the Home page, click Site Settings.
k.       Click Configure site-wide security.
l.         Click New Role Assignment.
m.    Type a Windows user account in the following format: domain\user
n.      Click to select the System Administrator check box.
o.      Click OK.
p.      Close Report Manager.
11.   Open Report Manager in Internet Explorer without using the Run as administrator option.
Microsoft Online Community Support

Report Builder 1.0 for SQL Server Reporting Services 2008 R2

We are trying to implement Ad-Hoc Reporting using SSRS 2008 R2.
First of all, it is very unhelpful that all SSRS books are for either 2008 or 2012, even though SSRS has major changes in 2008 R2 compared to 2008.
Our instructional materials indicate that we should build Report Models to abstract out our databases into terms familiar to our business users.
The problem we are having is the difference in functionality between Report Builder 1.0 and Report Builder 3.0. Report Builder 3.0 is touted as having the modern, ribbon based interface that is supposed to make end-users feel more comfortable. However,
all the documentation says that end users are supposed to use Report Builder 1.0 for Ad-Hoc Reporting. And, it seems, that the reports generated by Report Builder 1.0 are not round-trip compatible with all the other reporting tools for SSRS 2008 R2.
The documentation we have illustrates that Report Builder 1.0 is nice for Ad-Hoc reporting, because is based on connecting directly to Report Models, and the end users can directly drag-and-drop entities and fields into their reports.
When we try working with Report Builder 3.0, it seems we must first connect to the Report Model as a Data Source and then build a Dataset query on the Report Model. Only then are some entity attributes available to be dropped into the report.
If the user decides another source column is needed, they have to go back, edit the query, save the query, and then drag the column from the Dataset to the report. This does not seem end user friendly at all!
We are also concerned that if we train our users on the seemingly soon-to-be-obsolete Report Builder 1.0, and get them used to having direct Report Model access, that at some point we will have to move them to the Dataset-interrupted approach of Report Builder
2+. Highlighting this perception of impending obsolescence of Report Builder 1.0 is that in our shop that is starting with SSRS 2008 R2, we cannot figure out how to get a copy of Report Builder 1.0 in the first place.
We just don't see our end users being savvy enough to handle the steps involved with creating Datasets on top of Report Model Data Sources. So we would have to build the Datasets for them. But in that case, what point is there in creating any
Report Models in the first place if DBAs are the ones to make Datasets?
As such, it is hard to envision a forward-looking SSRS implementation that has the end user ease-of-use Ad-Hoc reporting that the SSRS 2008 documentation presents.
What is it that Microsoft actually wants/expects SSRS implementers to do?
Dan Jameson
Manager SQL Server DBA
CureSearch for Children's Cancer
http://www.CureSearch.org

Hi Dan,
Report Builder 1.0
Simple template-based reports
Requires report model
Supports only SQL Server, Oracle, and Analysis Services as data sources
Supports RDL 2005
Bundled in SSRS
Report Builder 2.0 or later
Full-featured reports as the BIDS Report Designer
Doesn't require (but supports) report models
Supports any data source
Supports RDL 2008
Available as a separate web download
In your scenario, you want to use Report Builder 1.0 in SQL Server Reporting Services 2008 R2, I am afraid this cannot achieve. Report Builder 1.0 is available in the box in either SQL 2005 or SQL 2008. It is not available as a separate client apps and is
only available as a click once application.
Report Builder 1.0
Report Builder 3.0
Thank you for your understanding.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Report Services Integrated mode : Error 503 after 100 seconds

Hello,
After resolving an issue with some timeouts in shared datasets (updated value not taken into account), i am now facing another timeout (?) issue with our production sharepoint server and reporting services :
If a report takes more than 100 seconds to display, the following message is displayed on the top of the page :
"Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 503"
The exception is triggered by the scriptmanager, but i don't know why : all the applications pool are running fine, and if i look in SSRS log, it shows that the task completed successfully !
Our development server is not affected by this strange behavior.
Is there a secret timeout switch hidden somewhere ??

Hi Raphael,
In Reporting Services, if the report server is under high memory pressure, the report server will refuse new requests until the current application domain is unloaded and a new one instantiated. While requests are refused, you will receive HTTP 503 errors.
To avoid this issue, you can add more memory, move the report server installation to a computer that has more memory, or change the memory configuration settings. For the detail information about it, please see HTTP 503 Service is Unavailable section on the
link below:
http://technet.microsoft.com/en-us/library/ms159778(v=sql.105).aspx
Besides, for the timeout issue, you can refer to the links below to troubleshooting it.
http://blogs.msdn.com/b/mariae/archive/2009/09/24/troubleshooting-timeout-errors-in-reporting-services.aspx
http://geekswithblogs.net/ssrs/archive/2009/10/30/steps-to-resolve-ssrs-timeout-issues.aspx
If you have any questions, please feel free to ask.
Regards,
Charlie Liao
TechNet Community Support

How to fix a report textbox aggregate expression error in SQL server reporting with multiple datasets?

I have a SQL Server Reporting Services report that has a textbox within a Report with variations of the following expression
=Sum(IiF(Fields!RegisterID.Value = 6000, 1, 0)
and
Iif(Fields!PointID.Value = 500, 1, 0)) / Sum(Iif(Fields!PointID.Value = 500, 1, 0))
I see the following error when I try to preview the report:
The Value expression for the text box ‘Textbox2’ uses an aggregate expression without a scope. A scope is required for all aggregates used outside of a data region unless the report contains exactly one dataset.
What am I missing in this this expression to make it run incorrectly

Can you include dataset name in your sum functions? e.g. Sum(IiF(Fields!RegisterID.Value = 6000, 1, 0)
and
Iif(Fields!PointID.Value = 500, 1, 0)) should include your dataset name as Sum(IiF(Fields!RegisterID.Value = 6000, 1, 0) and Iif(Fields!PointID.Value = 500, 1, 0),"datasetname")Like wise Sum(Iif(Fields!PointID.Value = 500, 1, 0)) should also have dataset name Sum(Iif(Fields!PointID.Value = 500, 1, 0),"datasetname")
Gaur

Reporting Services - All Datasets Broken

Similar Messages

Maybe you are looking for