SSRS报告的定义无效
当我尝试使用 BIDS 将报表部署到我们的 报表服务器 时，如何解决收到的以下错误消息？
消息：
错误：报告“/OrderAnalysis”的定义无效。
报告元素：
<Report xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner" xmlns:cl="http://schemas.microsoft.com/sqlserver/reporting/2010/01/componentdefinition" xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition">
How can I resolve the below error message that I receive when I try to deploy my report to our our Reporting Server using BIDS?
Message:
Error : The definition of the report '/OrderAnalysis' is invalid.
Report Element:
<Report xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner" xmlns:cl="http://schemas.microsoft.com/sqlserver/reporting/2010/01/componentdefinition" xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition">
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（10）
我发现了这个问题...由于 .rdl 中对数据 conns 等的引用不正确/失败。还发现 BIDS 不喜欢在某些项目/报告文件名中包含空格...所以任何面临此问题的人问题请确保您的命名中没有空格，并检查您的 rdl 文件、连接以及所有失败/过时的引用！ Visual Studio 在保持所有引用最新方面似乎很糟糕......上帝禁止你必须重命名任何东西！
I found the problem to this... due to a incorrect/failed reference in .rdl to data conns etc. Also found that BIDS wasn't happy about having spaces in some of the project/report filenames... so anyone facing this issue make sure you have no spaces in your naming and check your rdl files, connections, everything for failed/out of date references! Visual Studio seems crap at keeping all of it's references up to date... god forbid you have to rename anything!
我只是更改了报告参数之一中一个字符的大小写，并且无法再部署。将单个字符更改回大写允许我重新部署。
卓越。
I had simply changed the capitalization of ONE character in one of my report parameters and could no longer deploy. Changing the single character back to uppercase allowed me to redeploy.
Remarkable.
我刚刚在 MS CRM Dynamics 2011 的自定义报告的 SSRS 开发过程中遇到了同样的问题。
发生这种情况的原因是因为我使用了一些隐藏参数，其中一些我忘记了给出默认值。
因此，由于我几乎没有时间完成报告，所以我忘记为某些参数设置默认值，并且我冒着失去更多时间来修复它的风险。
幸运的是，我很快就发现了它，因为错误显示了文本框和带有第一个错误参数的段落，但它没有显示参数的名称：
“我无法发布错误的图像，因为该网站不允许我”
一般来说，在 SSRS 开发过程中，记住以下几点非常重要：
- 将报告参数按正确的顺序排列（从主报告继承的第一个es参数或子数据集的参数要点）
- 为隐藏参数和内部参数分配默认值。
I just had this same problem during a SSRS development of a Custom Report for MS CRM Dynamics 2011.
The reason because it occurred is because I am using some Hidden Parameters and for some of them I forget to give a default value.
So, because of I have few time to finish the report I forget to put the default value for some Parameters and I risked to lost more time to fix it.
Luckily I found it very fast because the error shows the textbox and the paragraph with the first wrong parameter but it didn't shows the name of the parameter:
"I cannot post the image of the error because this website don't allows me"
In general during SSRS developments it's very important to remember:
- To put the report parameters in the correct sequence (the referred ones for first es. parameters inherited from master report or parameters essentials for sub-datasets)
- To assign a default value to the Hide and Internal Parameters.
我在从另一个项目复制并更改数据源的报告中收到此错误。我通过打开数据集的属性，转到“参数”部分，然后从字面上重新选择右列中的所有参数来解决这个问题，就像我刚刚单击下拉列表并选择同一列一样。然后我点击预览，结果成功了！
I got this error on a report I copied from another project and changed the data source. I solved it by opening the properties of my dataset, going to the Parameters section, and literally just reselecting all the parameters in the right column, like I just clicked the dropdown and selected the same column. Then I hit preview, and it worked!
关于我的问题的一个非常神秘的消息。
我更改了参数的名称，但没有更新数据集中的这些名称。
A very cryptic message for what my issue was.
I had changed the names of the parameters, but did not update these names in the dataset.
我之所以发生这种情况，是因为更改了参数引用的 BIDS 中某些数据集字段的名称。我忘记进入参数并重新分配默认值（参数的默认值不会自动更改为新重命名的数据集字段。而是。
This occurred for me due to changing the names of certain dataset fields within BIDS that were being referenced by parameters. I forgot to go into the parameters and reassign a default value (the default value of the parameter didn't automatically change to the newly renamed dataset field. Instead .
我也刚刚遇到这个问题。有一个“刷新字段”选项，我发现它很有用。一开始我觉得不直观的是，必须以刷新字段的方式输入用于执行查询的值。一旦我弄清楚了这一点，并刷新了字段 - 事情就成功了。数据集和正在调用的共享数据集必须关联。
I just ran into this issue as well. There's an option to "refresh fields", which I found useful. What I didn't find intuitive at first was that one has to enter values used to execute the query in such a fashion as to refresh the fields. Once I figured this out, and refreshed the fields - things worked. The data sets and the shared dataset that's being called have to correlate.
当我使用 ReportSync 将一些 .rdl 文件上传到 SQL Server Report Services 时，出现此错误。就我而言，问题是这些 .rdl 文件有一些文本框，其中包含诸如
©、—（破折号）、–（ En dash) 字符等。使用 ReportSync 上传 .rdl 文件时，我必须对这些字符进行编码 (©、—、& ;ndash;等）并使用占位符属性将标记类型设置为 HTML 以消除此错误。如果我使用 SQL Server Reporting Services 手动逐一上传每个 .rdl 文件，则不会收到此错误。但我有很多 .rdl 文件，单独上传每个文件会非常耗时，这就是为什么我使用 ReportSync 批量上传所有 .rdl 文件。
抱歉，如果我的答案看起来不相关，但我希望这可以帮助其他人在处理 SSRS .rdl 文件时收到此错误消息。
I got this error when I used ReportSync to upload some .rdl files to SQL Server Report Services. In my case, the issue was that these .rdl files had some Text Box containing characters like
©,—(Em dash),–(En dash) characters, etc. When uploading .rdl files using ReportSync, I had to encode these characters (©,—,–, etc.) and use Placeholder Properties to set the Markup type to HTML in order to get rid of this error.I wouldn't get this error If I manually uploaded each of the .rdl files one-by-one using SQL Server Reporting Services. But I have a lot of .rdl files and uploading each one individually would be time-consuming, which is why I use ReportSync to mass upload all .rdl files.
Sorry, if my answer doesn't seem relevant, but I hope this helps anyone else getting this error message when dealing with SSRS .rdl files.
我收到此错误并尝试了此处的大部分建议。最后我对报表项目进行了“清理”并再次尝试。终于成功了！！
I was getting this error and tried most of the suggestions here. Finally I did a "Clean" on the report project and tried again. It finally worked!!
当我尝试部署来自 BIDS 的报告时，我刚刚收到了这条晦涩的消息。
经过一番搜寻后，我通过进入“预览”窗口发现了一个更具描述性的错误。
I just received this obscure message when trying to deploy a report from BIDS.
After a little hunting I found a more descriptive error by going into the Preview window.