Chat now with support
Chat with Support

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.

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.
2
Click Publish to SSRS.
5

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

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.

Topics:  

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:

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.

Select Rating

I easily found the information I needed.

Select Rating