Skip to Content

Reporting service is one of infrastructure of SAP BPC from 2004 – OutlookSoft CPM 4.1 journal. Now it is being primary reporting for status such as function audit, data audit, work status and BPF.

 

Fundamental BPC functions regarding numbers is working well even reporting service is not working well. But sometimes, people could see variety of errors at some points.

 

Below picture is one of examples. It is happening when administrator trying to publish report from web administration page but reporting service or underlying component is not configured properly

Error message

 

Most of case, I suggest to open reporting service configuration. It must be appear as below picture.

Reporting service configuration

The point of above screenshot is left panel that includes status of each step. From “Server Status” to “Database Setup” and “Initialization” must be green checked. If you could see red “X” mark for any of it, your reporting service is not healthy. And probably not will work properly with BPC.

 

If you have any problem in this screen, you must re-configure current reporting service with correct setting.

 

One other common issue is instance of SQL server. Your SQL server may have named instance. Then you must use “SERVER\INSTANCE” to connect that SQL server. Then what about reporting service?

In typical scenario, reporting service also has named instance. Then virtual directory of reporting service also includes name of instance. Basic rule is “reportserver$INSTANCE” for web service. And “reports$INSTANCE” for report manager.

But if you choose “configure later” option of reporting service when you install reporting service, the basic rule is very easy to break. For some reason, reporting service configuration do not includes name of instance for virtual folder names and you can initialize your reporting service without recognize it. And you are going to provide instance name of reporting service in your next step – install BPC – then at last, BPC application is going to use reporting service with wrong virtual folder name.

To prevent this small but critical issue, just choose “configure with default setting” option when you install reporting service with named instance. Then all virtual directories will be set to correct name.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply