SSRS 2008-Reporting Services网页为空白，标题除外

25-04-10 2

如果您对SSRS2008-ReportingServices网页为空白，标题除外感兴趣，那么这篇文章一定是您不可错过的。我们将详细讲解SSRS2008-ReportingServices网页为空白，标

如果您对SSRS 2008-Reporting Services网页为空白，标题除外感兴趣，那么这篇文章一定是您不可错过的。我们将详细讲解SSRS 2008-Reporting Services网页为空白，标题除外的各种细节，此外还有关于asp.net – 在网页上的ReportViewer控件中呈现时,Reporting Services图表文本模糊、How to grant permissions to a custom assembly that is referenced in a report in Reporting Services、Reporting Service 2000 的一些技巧总结、Reporting Service 2005到2008升级测试的实用技巧。

本文目录一览：

SSRS 2008-Reporting Services网页为空白，标题除外
asp.net – 在网页上的ReportViewer控件中呈现时,Reporting Services图表文本模糊
How to grant permissions to a custom assembly that is referenced in a report in Reporting Services
Reporting Service 2000 的一些技巧总结
Reporting Service 2005到2008升级测试

SSRS 2008-Reporting Services网页为空白，标题除外

打开报表管理器时，我得到的是空白页：我有一个标题-“ … Reporting … HOME”，然后只有空白。

我使用的是SQL 2008和Windows Server 2008 R2 Standard。

任何想法如何解决？我已经确认我以本地管理员身份登录。我尝试将URL添加到受信任的站点，但这似乎也无济于事。

更新

当我转到ReportServer URL时，出现以下错误消息：

Reporting Services Error--------------------------------------------------------------------------------The permissions granted to user ''DTNT\greg'' are insufficient for performing this operation. (rsAccessDenied) Get Online Help--------------------------------------------------------------------------------SQL Server Reporting Services

答案1

小编典典

解决了，有点！我尝试右键单击IE，然后选择以管理员身份运行，然后转到报表管理器URL，一切正常。

我单击页面右上方的站点设置，并将greg用户添加为系统管理员和系统用户。

我还将greg用户添加为根目录上的内容管理器。

IT部门仍然说我已经是该计算机上的本地管理员，但这似乎是使它正常运行所必需的。

有什么想法为什么有必要吗？

asp.net – 在网页上的ReportViewer控件中呈现时,Reporting Services图表文本模糊

问题

我们使用Reporting Services报告和ReportViewer控件在网页上呈现条形图.有时图表上的文字很清晰：

但大多数情况下,图表上的文字模糊不清：

到底是怎么回事？

采取的措施解决和其他信息

>广泛搜索网络和SO
>尝试了不同的浏览器,用户和机器;无法确定韵律或模糊的原因
>尝试了SSRS报告属性DynamicHeight和DynamicWidth的几个设置
>在Firefox中,右键单击图表图像并选择“查看图像”时,显示的图像始终清晰
>在有边界的图表上,这个问题似乎更为突出;删除图表上的边框,但问题仍然存在

影响浏览器

> Firefox 15.0
> Chrome 23.0.1271.97米
> IE 9但仅在浏览器模式下= IE9,文档模式= IE9标准

环境

> Visual Studio 2010专业版
> .NET 4.0
> IIS 7.0
> Reporting Services 2008
> ReportViewer控件版本10

解决方法

原因

ReportViewer控件将图表呈现为PNG图像. ReportViewer将宽度,高度和最小宽度属性添加到图像的CSS中.这些CSS属性会导致图像在浏览器中缩小到稍小的尺寸.图像缩放导致观察到的模糊.

解析度

通过使用额外的CSS来覆盖ReportViewer呈现的多个CSS属性,我们的环境中解决了该问题. Reporting Services图表在BIDS中被赋予一个特殊标记,因此CSS选择器可以找到受影响的图像.

步骤1.为图表提供其ToolTip属性的唯一值：

(此示例中的唯一值是MyOfficeChart.)

当图表呈现为< img>时,< img> tag的alt和title属性设置为此值.

第2步.创建CSS以选择< img>通过title属性的唯一值,并覆盖导致问题的CSS：

img[title$='MyOfficeChart']
{
    height:auto !important;
    width:auto !important;
    min-width:0 !important;
}

这些步骤解决了所有浏览器和用户的问题,以及图表是否具有边框.

How to grant permissions to a custom assembly that is referenced in a report in Reporting Services

Ref: http://support.microsoft.com/kb/842419/en-us

How to grant permissions to a custom assembly that is referenced in a report in Reporting Services

View products that this article applies to.

Article ID	:	842419
Last Review	:	April 3, 2007
Revision	:	2.1

This article describes a problem that occurs when you access a custom assembly in your report that does not have sufficient permissions on the resources in your environment. The article also provides steps to grant permissions to the custom assemblies that are used in the reports. To do this, follow these steps:

1.	Assert permissions in your custom assembly.
2.	Make the custom assembly available to Report Designer and to Report Server.
3.	Reference the custom assembly in your report.
4.	Modify the code access security settings for your custom assembly.

Back to the top

INTRODUCTION

Reports that access custom assemblies may not render successfully if the custom assemblies do not have sufficient permissions. This article describes how to modify the policy configuration files to grant additional permissions to a custom assembly that is accessed by a report.

Back to the top

MORE informatION

After you create a custom assembly by using the Microsoft .NET Framework, and then you access the custom assembly in your report and preview the report in Report Designer, the report may not render successfully. However, if you run the same report in DebugLocal mode in Report Designer or if you view the report by using Report Manager, the following error may be rendered in the report instead of the output of the referenced custom assembly:

#Error

Additionally, you may receive an error message that is similar to the following in Report Designer when you run the report in DebugLocal mode:

Request for the permission of type System.Security.Permissions.FileIOPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Failed.

This problem may occur when the custom assemblies that are referenced in your report do not have sufficient permissions.

Note If you preview the report in Report Designer, the report runs all the report expressions by using the FullTrust permission set. The report does not use the security policy settings.

To grant the required permissions to a custom assembly, follow these steps:

1.	Assert permissions in your custom assembly.
2.	Make the custom assembly available to Report Designer and to Report Server.
3.	Reference the custom assembly in your report.
4.	Modify the code access security settings for your custom assembly.

Back to the top

Assert permissions in your custom assembly

To acquire the required permissions to run the code in your custom assembly, you must assert the required permissions in your custom assembly code.

Note The examples provided in this section use C# code.

For example, if you access data in Microsoft sql Server tables by using the "System.Data.sqlClient" namespace in your custom assembly, you must add the following code to your custom assembly before you use the "System.Data.sqlClient" namespace:


System.Data.sqlClient.sqlClientPermission psql = new sqlClientPermission(System.Security.Permissions.PermissionState.Unrestricted);
psql.Assert();

If you access a file in your custom assembly, you must add the following code to your custom assembly before you access the file:


FileIOPermission filePerm = new FileIOPermission(FileIOPermissionAccess.Read, "C:\TestFile");
filePerm.Assert();

Similarly, if you access a Web service in your custom assembly, you must add code that is similar to the following to assert the Web permissions:


System.Text.RegularExpressions.Regex urlRegEx = new System.Text.RegularExpressions.Regex(@"http://www\.webcontinuum\.net/.*");
System.Net.WebPermission p = new System.Net.WebPermission(NetworkAccess.Connect,urlRegEx);
p.Assert();

For more information about asserting permissions in your custom assembly, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa179495(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa179495(sql.80).aspx)

Back to the top

Make the custom assembly available to Report Designer and to Report Server

To make your custom assembly available to Report Designer and to Report Server, you must copy the custom assembly to the following folders:

•	`Installation Drive`:\Program Files\Microsoft sql Server\80\Tools\Report Designer
•	`Installation Drive`:\Program Files\Microsoft sql Server\MSsql\Reporting Services\reportserver\bin

Back to the top

Reference the custom assembly in your report

To reference a custom assembly in your report, follow these steps:

1.	Open the report project in Microsoft Visual Studio .NET 2003.
2.	Open the report that must reference the custom assembly.
3.	On the Report menu, click Report Properties.
4.	In the Report Properties dialog Box, click the References tab.
5.	Under References, click the ellipsis button that is next to the Assembly name column header.
6.	In the Add References dialog Box, click browse.
7.	In the Select Component dialog Box, locate and click your custom assembly, and then click Open.
8.	In the Add References dialog Box, click OK.
9.	In the Report Properties dialog Box, click OK.

Back to the top

Modify the code access security settings for your custom assembly

To grant the required permissions to the custom assembly, you must modify the code access security settings in the policy configuration files that correspond to Report Designer and to Report Server. To do this, follow these steps:

Create the permission set element and the code group element for your custom assembly that specifies the required permissions. To do this, follow these steps:

Click Start, point to Settings, and then click Control Panel.

In Control Panel, double-click Administrative Tools.

In the Administrative Tools window, double-click Microsoft .NET Framework 1.1 Configuration.

In the left pane of the .NET Configuration 1.1 window, expand Runtime Security Policy.

Under Runtime Security Policy, expand Machine.

Under Machine, right-click Permission Sets, and then click New.

On the Identify the new Permission Set page, click Create a new permission set.

Type TestPermissions in the Name Box, and then click Next.

On the Assign Individual Permissions to Permission Set page, click Security in the Available Permissions list, and then click Add.

In the Permission Settings dialog Box, click Grant assemblies the following security permissions, and then click to select the following check Boxes:

•	Enable assembly execution
•	Assert any permission that has been granted

Note You can also turn on the other listed permission settings based on your requirements.

Click OK.

On the Assign Individual Permissions to Permission Set page, add any additional permissions from the Available Permissions list to the Assigned Permissions list.

Click Finish.

In the .NET Configuration 1.1 window, expand Code Groups under Machine.

Under Code Groups, right-click All_Code, and then click New.

On the Identify the new Code Group page, click Create a new code group, type TestCodeGroup in the Name Box, and then click Next.

On the Choose a condition type page, click URL in the Choose the condition type for this code group list.

Type the absolute path of your custom assembly (Installation Drive:\Program Files\Microsoft sql Server\80\Tools\Report Designer\Custom assembly name, for example) in the Report Designer folder in the URL Box, and then click Next.

On the Assign a Permission Set to the Code Group page, click Use existing permission set, and then click TestPermissions in the list.

Click Next, and then click Finish.

The permission set and the code group that correspond to your custom assembly are created according to your specifications in the Security.config file on your computer.

Add the permission set and the code group that correspond to your custom assembly in the security policy configuration files for your report server. To do this, follow these steps:

Open the Security.config file, the Rspreviewpolicy.config file, and the RSSrvpolicy.config file.

Note The following list provides the default locations of the Security.config file, the Rspreviewpolicy.config file, and the RSSrvpolicy.config file.

•	By default, the Security.config file is located in the `Installation Drive`:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\security.config folder.
•	By default, the Rspreviewpolicy.config is located in the `Installation Drive`:\Program Files\Microsoft sql Server\80\Tools\Report Designer\rspreviewpolicy.config folder.
•	By default, the RSSrvpolicy.config folder is located in the `Installation Drive`:\Program Files\Microsoft sql Server\MSsql\Reporting Services\reportserver\RSSrvpolicy.config folder.

copy the PermissionSet element that corresponds to the TestPermissions permission set from the Security.config file.

Paste the PermissionSet element that corresponds to the TestPermissions permission set in the Rspreviewpolicy.config file and the RSSrvpolicy.config file as the last sub-element of the NamedPermissionSets element.

copy the CodeGroup element that corresponds to the TestCodeGroup code group from the Security.config file.

Paste the CodeGroup element that corresponds to the TestCodeGroup code group in the Rspreviewpolicy.config file and in the RSSrvpolicy.config file after the first CodeGroup element.

Remove the PermissionSet element that corresponds to the TestPermissions permission set and the CodeGroup element that corresponds to the TestCodeGroup code group from the Security.config file.

Save the Security.config file, the Rspreviewpolicy.config file, and the RSSrvpolicy.config file.

After you access the custom assembly in your report and you run the report in DebugLocal mode, the report renders successfully.

Back to the top

REFERENCES

For more information about code access security in Reporting Services, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa902638(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa902638(sql.80).aspx)

For more information about the using custom assemblies with reports in Reporting Services, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa179513(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa179513(sql.80).aspx)

For more information about debugging the custom assemblies in Reporting Services, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa179526(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa179526(sql.80).aspx)

Reporting Service 2000 的一些技巧总结

在使用 Reporting Service 2000 过程中，对一些特殊的地方做了一些总结，下子把它贴出来，供大家参考：

1．IIF 表达式如何使用？
       在很多地方，都可以使用 IIF 表达式来实现一些特定的操作，比如图片的隐藏与显示，数据的条件显示等等。
IIF 表达式的语法为：IIF (Expression,value when true,value when false)，IIF 表达式可以嵌套使用。
2．Reporting Service 支持多语言吗？
支持，可以参见 Language 属性。该属性可以确定报表的一些基本格式，如货币符号，数字格式等。
如果 Language 确定该报表是美国的语言，那么它的货币符号是：$, 数字格式：20,000.00；而如果 Language 确定该报表是欧洲的语言时，那么它的货币符号是：€，数字格式：20.000,00。
那么如何动态设定报表的语言呢？报表的语言必须放在参数中，而不能来自于 DataSet
3．报表表头 / 脚可以处理 DataSet 中的数据吗？
       不可以。可以通过参数来间接处理。
4．如何设置混合内容脚本的格式呢？
如€ 20.000,00, 那么可以这么写：” €” & ““ & Format (number,”N2”)。
5．报表导出到 pdf 文件时，为什么中间会有空页出现呢？
       是由于报表的宽度过宽或长度过长所引出的问题。报表的页边距可以在报表属性中设置。
6．报表部署到 Report Server 上时，打开报表为什么会出错呢？
       有可能是因为报表模板的数据源没有设置正确的原因。
7．如何让报表的参数不显示出来呢？
       将参数的 Prompt 设置为空。
8．报表的参数可否依赖于其他参数呢？
       可以，比如有两个参数：LANGUAGE,LOGO，LANGUAGE 来自于客户输入，LOGO 的内容可以是根据 LANGUAGE 取出的数据。也可以说，在输入 LANGUAGE 前，LOGO 参数还没有数据可以供选择。
9．建立存储过程数据源有哪些方法？
       有两种方法，一种是存储过程，另一种是 TEXT。两种方法基本一样。但是在创建数据源的时候，有可能会出现一种情况，那就是输入了存储过程的名字，然后点来更新字段，结果字段为空，这种情况极有可能是 vs.net2003 的一个 bug，解决办法有：手动增加 Fields。
10．报表文件可以分文件夹存放吗？
       不可以。你即便添加了已存在的.rdl 文件，那么它会在项目根目录下重新加一条.rdl 文件。
11．报表中的数据格式有哪些？
       Cnum:C = 金额，num 为小数位数，如 C3=￥12,345.679
       Dnum:D = 整数，num 为整数的位数，如 D5=01234
       Enum:E = 科学记数法格式，num 为 E 前面数字的小数位数，如 E3=1.235E+004
       Fnum:F = 浮点数，num 为浮点数的小数位数，如 F2=12345.68
       Gnum:G = 数字，num 为精确位数，如 G2=1.2E004,G3=1.23E004,G5=12346…
       Mnum:M = 月日，num 不太清楚
       Nnum:N=Numeric,num 为小数位数，如 N2=12,345.68
       Pnum:P = 百分比，num 为百分比的小数位数，如 P3=1,234,567.890%
       R: 数字
       S: 日期，如：2006-10-13 T10:00:00
       T: 小时分钟，如：16：19
       U: 通用时间，如：2006-10-13 10:00:00Z
       X:
       Y: 年月，如：2006 年 10 月
12．Report 中有哪些内置函数可以使用？
       First,Sum,Count,Format,RowNumber,RunningValue 等。

---------------------
作者：zm820630
原文：https://blog.csdn.net/zm820630/article/details/2270632?utm_source=copy

Reporting Service 2005到2008升级测试

SQL Server 2008的Reporting不管是在功能性能还是管理上上都比2005有了很大的提高，所以很多公司都会将Reporting2005进行升级。我

SQL Server 2008的Reporting不管是在功能性能还是管理上上都比2005有了很大的提高，所以很多公司都会将Reporting2005进行升级。

我这次的测试是将Reporting的数据库从2005迁移到2008上(不是直接在原来的服务器升级)。

升级步骤：

1. 首先备份SQL Server 2008的ReprotServer和ReportServerTempDB数据库（防止升级失败可以回滚）。

2. 备份SQL Server 2008加密密钥.(ReportingServices使用加密密钥来保护存储在报表服务器数据库中的凭据和连接信息)。

3. 在SQL Server 2005上执行步骤2.3。

4. 将SQL Server 2008上的Reporting Service停掉（防止后面还原数据库无法获得独占锁）。

5. 将SQL Server 2005的两个数据库还原到SQL Server 2008.

6. 启动SQL Server 2008 Reporting Service。

7. 将SQL Server 2005备份的加密密钥还原到SQL Server 2008(否则Reporting无法正常工作)。

8. 测试报表正常工作。

由于我们没有使用第三方的工具做开发，所以升级非常顺利。但是有很多注意事项需要在升级之前参考一下：(v=sql.100).aspx

，

我们今天的关于SSRS 2008-Reporting Services网页为空白，标题除外的分享已经告一段落，感谢您的关注，如果您想了解更多关于asp.net – 在网页上的ReportViewer控件中呈现时,Reporting Services图表文本模糊、How to grant permissions to a custom assembly that is referenced in a report in Reporting Services、Reporting Service 2000 的一些技巧总结、Reporting Service 2005到2008升级测试的相关信息，请在本站查询。

本文标签：