- Introduction
- Installation
- crossAdmin
- Setting up Across Modes
- Softkeys
- Generating crossGrid Certificates
- Creating Generic Softkeys
- Changing the Across Database User
- Defragmenting Database Files
- Running a Backup
- Auto-Deployment
- Automatic Client Update
- Windows Authentication
- Uninstalling
- Reference: Menus in crossAdmin
- Appendix
Reporting Services Troubleshooting
Error message rsAccessDenied
After requesting a report, the following error message appears: "The permissions granted to user 'user' are insufficient for performing this operation. (rsAccessDenied)"
This error occurs because the user or user group does not have the permissions for accessing the reports.
To solve this problem, you need to grant the user the needed permissions.
- To do this, open the Report Manager in your browser (e.g. http://<<server name SQL Server>>//reports) and click Folder Settings.
- Then click New Role Assignment and enter the respective Windows domain user or Windows domain user group (in the form domain\account).
- Activate the role in your browser.
- Click OK.
HTTP error 404
In the browser, the report page (e.g. localhost/reports) and the Report Server page (e.g. http://<<server name SQL Server>>//reportserver) cannot be reached, and HTTP error 404 is displayed. The report page in the crossAnalytics module in Across is not displayed either. Furthermore, the Reporting Services cannot be configured with crossAdmin.
This may be because the Reporting Services are not running on default port 80, but on another port. Therefore, the respective pages cannot be reached. (This problem only occurs in connection with SQL Server 2008.)
- To solve this problem, you should first determine the port on which the Reporting Services are running.
- To do this, go to the Web Service URL section in the Reporting Services.
The port is indicated under TCP Port.
- Go to the Report ManagerURL section and click Advanced.
- If the Reporting Services are not running on the default port, but on another port (e.g. 8080), you need to make two adjustments:
- First, adapt the configuration file user.config in the subdirectory crossAnalyticsWebApp of the Across folder (e.g. C:\Program Files\Across) by adding the port on which the Reporting Services are running.
To do this, open the file (e.g. in a text editor). Under reportingserver the port should be entered in the URL for the ReportServer as in the following example:
<?xml version="1.0"?> <userconfig> <crossanalytics reportingserver="http://<<Servername SQL Server>>:<<port>>/ReportServer/ReportService2005.asmx" xmlconfigurationfilepath="crossAnalytics.xml"/> </userconfig>
Replace <<Port>> with the respective port, e.g. http://<<server name SQL Server>>:8080/ReportServer.
- Then adapt the value of the registry key RSUrl in the registry under [HKLM\Software\Across] or [HKLM\Software\ Wow6432Node\Across] by inserting the port in the URL (be sure to back up the registry first):
http://<<Servername SQL Server>>:<<port>>/ReportServer/ ReportService2005.asmx
Replace <<Port>> with the respective port.
- First, adapt the configuration file user.config in the subdirectory crossAnalyticsWebApp of the Across folder (e.g. C:\Program Files\Across) by adding the port on which the Reporting Services are running.