cancel
Showing results for 
Search instead for 
Did you mean: 

Publishing reports is not possible

Former Member
0 Kudos

Hello experts,

We are installing BPC 7.0 SP3, all seem to work fine excepted the publishing of audit reports :

When we follow the steps below :

- Log into BPC for Administration

- Under Web Admin Task Click Publish Reports

- Select the reports and click the green check mark to publish them.

We get the following error message :

"The request failed with HTTP status 401: Unauthorized"

Do you know what can be the root cause of this issue or could you please give me some clues to get ahead with the investigations ?

Thanks in advance for your help.

Regards,

Lionel

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

It seems like reporting service issue. I suggest to check your current reporting service status by open "http://reportserver/reports" URL in your browser. If it is not working well, you should configure your reporting service prior to use any reports in RS.

"Unauthorized" error probably came from reporting service web service. Maybe your reporting service is not configured to accept certain authentication such as Integrated or basic.

Former Member
0 Kudos

Hello,

First of all, thank you very much for your reply.

Unfortunately, my issue still remains.

I checked the reporting services via "http://reportserver/reports" but it works fine.

Regarding the configuration of the reporting services in IIS, the "Reports" and "ReportServer" virtual directories are configured with the Integrated Windows authentication.

The IIS application pool "ReportServer" is set with the identity "Network Service".

I've tried to set the 2 vistual directories with the anonymous authentication but there is no change.

My reporting services and the Osoft web site are set with the SSL protocol.

All work fine excepted the publishing reports.

Thank you very much.

Former Member
0 Kudos

I think your case is little bit tough than usual.

Authentication with anonymous never helps. BPC is using SSRS with given credential which has to have enough rights. Maybe identity of ReportServer app pool need to change to something else that has more rights. Have you tried with same as BPC admin ID?

If SSRS associated with BPC is working fine, you can see folders in reporting service. "ApShell" must be there no matter what. And same name as your appset. Otherwise, I can assume BPC and SSRS is not communicating properly. That folder must be appeared in both of "reports" and "reportserver". Actually, "reportserver" is the folder of web service. "reports" is just consumer but prettier.

SSL can be issue. Is your reporting service service virtual directory (reports in typical) uses certification that associated to FQDN as well as your BPC server? And are you using your SQL server with named instance?

Former Member
0 Kudos

Hello,

Unfortunately the issue is not solved, and I do not know why.

To answer to Seongbae, indeed I'm using SSL, but all the other BPC features are working fine. I use also, a named instance for my SQL database.

Answers (1)

Answers (1)

Former Member
0 Kudos

SSRS with SSL needs specific configuration. Open SSRS configuration tool and check if it's correctly set for SSL (there is some kind of check box).

You will fond more about it in Microsoft KB (SSRS configuration is well documented)