Part 4: Reporting
My last blog in this series focuses on typical Reporting issues.
Creating Report Server database fails
Go to SQL Server Management Studio, access Databases, remove all Reportserver* databases and run Report Server Configuration Manager again. Report Server Configuration Manager does not run properly, before the non-functioning databases are removed.
Standard Reports do not install
Installing Standard Reports fails to postinstall error.
Check that you have filled in the PATH: -prefix to Reporting Services Instance Name or Path in Infrastructure Administrator.
In case it is missing, do as follows:
Reports do not work
In case reporting was meant to be installed with Windows authentication, check that Reporting Database settings in Infrastructure Administrator have “Use Windows authentication” checked and Reporting Database Password field is empty.
If you have an entry in Reporting Database Password field, do as follows:
The last digits of phone numbers are masked in reports
Go to System Configurator/Reporting/Data Protection Rules and adjust how data should be protected.
If you create a new Data Protection Rule, make sure to also assign it to appropriate Data Destination. Changes do not effect data already collected, but only the data will be collected from then on.
For more info see Data protection rules: http://help.sap.com/saphelp_bcm70/helpdata/en/b1/e5856b9c134a8b82165bc118c36804/content.htm
Note that Volume 7 - Contact log –report is different to other reports and must be edited on the server.
The previous blogs can be found here:
Certificates, SQL and prerequisites:
https://blogs.sap.com/2017/01/09/installation-troubleshooting-certificates/
IA and System Configurator:
https://blogs.sap.com/2017/01/16/installation-troubleshooting-ia-and-sc/
CDT, Call recording and Voicemail:
https://blogs.sap.com/2017/01/30/installation-troubleshooting-cdt-call-recording-and-voicemail/
This is the last blog in this series, I hope you find extra guidance to your installation and those will go smoothly from now on.
My last blog in this series focuses on typical Reporting issues.
Creating Report Server database fails
Go to SQL Server Management Studio, access Databases, remove all Reportserver* databases and run Report Server Configuration Manager again. Report Server Configuration Manager does not run properly, before the non-functioning databases are removed.
Standard Reports do not install
Installing Standard Reports fails to postinstall error.
Check that you have filled in the PATH: -prefix to Reporting Services Instance Name or Path in Infrastructure Administrator.
PATH: prefix
In case it is missing, do as follows:
- Check that the path itself is correct.
- Add the PATH: prefix.
- Synchronize Instances and Apply Changes.
Reports do not work
In case reporting was meant to be installed with Windows authentication, check that Reporting Database settings in Infrastructure Administrator have “Use Windows authentication” checked and Reporting Database Password field is empty.
Choose only one authentication mode - IA
If you have an entry in Reporting Database Password field, do as follows:
- Remove the password and save settings.
- Synchronize instances and Apply Changes.
- Go to System Configurator, choose Reporting Data Destinations, remove SQL entries and save.
Choose only one authentication mode - SC
The last digits of phone numbers are masked in reports
Go to System Configurator/Reporting/Data Protection Rules and adjust how data should be protected.
If you create a new Data Protection Rule, make sure to also assign it to appropriate Data Destination. Changes do not effect data already collected, but only the data will be collected from then on.
For more info see Data protection rules: http://help.sap.com/saphelp_bcm70/helpdata/en/b1/e5856b9c134a8b82165bc118c36804/content.htm
Note that Volume 7 - Contact log –report is different to other reports and must be edited on the server.
The previous blogs can be found here:
Certificates, SQL and prerequisites:
https://blogs.sap.com/2017/01/09/installation-troubleshooting-certificates/
IA and System Configurator:
https://blogs.sap.com/2017/01/16/installation-troubleshooting-ia-and-sc/
CDT, Call recording and Voicemail:
https://blogs.sap.com/2017/01/30/installation-troubleshooting-cdt-call-recording-and-voicemail/
This is the last blog in this series, I hope you find extra guidance to your installation and those will go smoothly from now on.
- SAP Managed Tags:
| User | Count |
|---|---|
| 5 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
