Chatta subito con l'assistenza
Chat con il supporto

Enterprise Reporter 3.5.1 - Report Manager User Guide

Quest Enterprise Reporter Report Manager Introducing the Report Manager Running and Scheduling Reports Creating and Editing Reports Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets

Publishing Reports to SSRS

Reporting administrators can publish any report to SSRS. Once published, users with access can generate these reports from a web browser.

You can publish an entire container at once. All reports in the container will appear in a flat list, even if they were originally in a subcontainer in Enterprise Reporter.

* 
CAUTION: The ability to publish reports to Quest Knowledge Portal and the integration with Quest Knowledge Portal has been removed from the product. After upgrade to Enterprise Reporter 3.5, all reports will have to be published to SSRS, as previously published reports to Quest Knowledge Portal will no longer be available and cannot be updated.

If you intend to publish reports to a custom path in SQL Server Reporting Services (SSRS), additional permissions must be configured.

•
For any path outside of the SSRS | Enterprise Reporter path and its subdirectories, the Reporter_Reporting_Admins and Reporter_Reporting_Operators groups must be given to the SSRS Browser role on the SSRS | Enterprise Reporter | Shared Resources location.
* 
TIP: Before publishing a report, verify that a report with the same name has not already been published. Reports with the same name will be overwritten automatically.
* 
CAUTION: Verify any reports that have been published with errors. Use the Open Log option to examine details in the log and determine what issues to resolve. Some features, such as scripts, which are possible in Enterprise Reporter, are not supported by SSRS. When you run a report in SSRS with filters, data types, fields or controls that are not supported, the field appears as undefined. You can modify the report to resolve the errors in Enterprise Reporter (see Editing Reports ) and then republish it. For example, you could change an operator.
To publish reports to SSRS
1
On the Report tab, right click any report or container.
You can select multiple reports.
You cannot publish the default containers: My Reports, Published Reports or Report Library.
2
Click Publish to SSRS.
3
If you are only publishing a single report, you can modify the name.
4
If you want to create or publish to a folder, type the path structure.
The full URL to the published report is shown.
5
Click OK.
6
A dialog box displays each step of progress during publishing.
Any errors encountered during publishing are also displayed.
7
If your report published successfully, click Close.

You can now run this report from SSRS. For details, see your SSRS administrator or see the SSRS User Guide in the Technical Documentation.

- OR -

If your report had errors, click Open Log and examine the details in the log to determine what issues to resolve, then click Close.

Troubleshooting Issues with Enterprise Reporter

•
Troubleshooting connectivity issues
•
Troubleshooting Connection Timeouts
•
Troubleshooting credential change failures
•
Auditing Report Manager Activity
•
Exporting Logs from the Report Manager
•
Resolving Issues in the Report Manager
•
Troubleshooting Issues with SSRS

Troubleshooting connectivity issues

Each console maintains connections to the Enterprise Reporter server and to the SQL Server database that stores Enterprise Reporter data. A loss of either connection causes problems. Figure 4 outlines the connections between the components and the server and database.

Figure 4. Connections between components and the server and database.
Topics:  
•
Restoring a connection to the Enterprise Reporter Server
•
Restoring a connection to the Enterprise Reporter database

Restoring a connection to the Enterprise Reporter Server

There are a number of reasons why a Enterprise Reporter server may be down. When a console loses its connection to the server, it becomes unusable and must be restarted. All users connected to the Enterprise Reporter server are affected. You should check the following connections:

•
Ensure that the computer hosting the server is turned on and running properly.
•
Ensure that the Enterprise Reporter server service is running. If necessary, restart it using the Services console.
•
Ensure that you can reach the host computer over your network.
•
Ensure that the server host computer meets the minimum system requirements.

If the server has gone down and been restored since you last logged in, then the next time you connect, you will be informed that the server went down. If you are the main Enterprise Reporter administrator, this allows you to be aware that your server has had issues. Intermittent failures over time may be due to instability in your network, problems on the server’s host computer, or your SQL Server deployment.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione