Report Manager: Unable to communicate with report server.

Hello,
I'm using forms authentication with Reporting Services for integration
within an application. The integration is working -- I'm able to
access reports server through URL access from the app, and any
attempts to access reports server before authenticating redirect the
user to the login page.
My problem is that Report Manager is not working. Any attempt to
access it yields the "Unable to communicate with report server. Please
verify that the report server is operational".
I've seen lots of references in posts to the error that I'm receiving
but none that have solved the problem for me. Most threads indicate
that it is a configuration file error.
I have gone over the MSDN article
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp)
tens of times to make sure I performed all the steps and to ensure
that all my configuration settings are correct.
All of my configuration settings for the reports server URL matches up
(and call the machine name not 'localhost').
Reports server seems to be working correctly. I can access it
directly from the URL. I'm also confident that my authentication
extension is working. When attempting to login to Report Manager, I
have verified that the 'LogonUser' web service call is being made and
returns true. The authentication ticket is being forwarded back to
the client browser.
Something must be configured incorrectly in Report Manager but there
are not that many settings and I've checked them all dozens of times!
;-)
One difference between my implementation and the sample is that I'm
using SSL to access the reports server everywhere. I'm assuming that
this would not cause problems for Report Manager. Does it?
I'd appreciate any help. Anyone have any ideas? Attached is the
trace of the error message from Report Manager's log.
Thanks,
Stefan
--
w3wp!ui!5a4!11/12/2004-18:09:20:: e ERROR: Unable to communicate with
report server. Please verify that the report server is operational.
w3wp!ui!5a4!11/12/2004-18:09:21:: e ERROR: HTTP status code --> 500
--Details--
CantCommunicateWithReportServerException: Unable to communicate with
report server. Please verify that the report server is operational.
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!5a4!11/12/2004-18:09:23:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)I had the same problem but when I commented the <deny users="?"> line in the
web.config under the ReportServer folder, I was able to logon onto the
Report Manager using the same Forms auth. But now, the reports will not
work. If I undo the change, we are back to square one. Let me know if you
find a solution to this one.
DC
"Stefan Leyhane" <sleyhane@.gmail.com> wrote in message
news:b3f9a06e.0411121551.2a1e3381@.posting.google.com...
> Hello,
> I'm using forms authentication with Reporting Services for integration
> within an application. The integration is working -- I'm able to
> access reports server through URL access from the app, and any
> attempts to access reports server before authenticating redirect the
> user to the login page.
> My problem is that Report Manager is not working. Any attempt to
> access it yields the "Unable to communicate with report server. Please
> verify that the report server is operational".
> I've seen lots of references in posts to the error that I'm receiving
> but none that have solved the problem for me. Most threads indicate
> that it is a configuration file error.
> I have gone over the MSDN article
>
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/ht
ml/ufairs.asp)
> tens of times to make sure I performed all the steps and to ensure
> that all my configuration settings are correct.
> All of my configuration settings for the reports server URL matches up
> (and call the machine name not 'localhost').
> Reports server seems to be working correctly. I can access it
> directly from the URL. I'm also confident that my authentication
> extension is working. When attempting to login to Report Manager, I
> have verified that the 'LogonUser' web service call is being made and
> returns true. The authentication ticket is being forwarded back to
> the client browser.
> Something must be configured incorrectly in Report Manager but there
> are not that many settings and I've checked them all dozens of times!
> ;-)
> One difference between my implementation and the sample is that I'm
> using SSL to access the reports server everywhere. I'm assuming that
> this would not cause problems for Report Manager. Does it?
> I'd appreciate any help. Anyone have any ideas? Attached is the
> trace of the error message from Report Manager's log.
> Thanks,
> Stefan
> --
> w3wp!ui!5a4!11/12/2004-18:09:20:: e ERROR: Unable to communicate with
> report server. Please verify that the report server is operational.
> w3wp!ui!5a4!11/12/2004-18:09:21:: e ERROR: HTTP status code --> 500
> --Details--
> CantCommunicateWithReportServerException: Unable to communicate with
> report server. Please verify that the report server is operational.
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!5a4!11/12/2004-18:09:23:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)|||DC,
I saw your posting from November. Did you ever find a solution for
this? I have the same issue and it's driving me nuts. Every time I
want to use ReportManager I have to comment out the
deny user=? line in the web config. I assume this is due to my using
forms authentication and messing up a config file somehow...
Can any Forma auth users shed some light on this one?
thanks,
Vince
Thomson Delmar Learning
DC wrote:
> I had the same problem but when I commented the <deny users="?"> line
in the
> web.config under the ReportServer folder, I was able to logon onto
the
> Report Manager using the same Forms auth. But now, the reports will
not
> work. If I undo the change, we are back to square one. Let me know if
you
> find a solution to this one.
> DC
>
> "Stefan Leyhane" <sleyhane@.gmail.com> wrote in message
> news:b3f9a06e.0411121551.2a1e3381@.posting.google.com...
> > Hello,
> >
> > I'm using forms authentication with Reporting Services for
integration
> > within an application. The integration is working -- I'm able to
> > access reports server through URL access from the app, and any
> > attempts to access reports server before authenticating redirect
the
> > user to the login page.
> >
> > My problem is that Report Manager is not working. Any attempt to
> > access it yields the "Unable to communicate with report server.
Please
> > verify that the report server is operational".
> >
> > I've seen lots of references in posts to the error that I'm
receiving
> > but none that have solved the problem for me. Most threads
indicate
> > that it is a configuration file error.
> >
> > I have gone over the MSDN article
> >
>
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/ht
> ml/ufairs.asp)
> > tens of times to make sure I performed all the steps and to ensure
> > that all my configuration settings are correct.
> >
> > All of my configuration settings for the reports server URL matches
up
> > (and call the machine name not 'localhost').
> >
> > Reports server seems to be working correctly. I can access it
> > directly from the URL. I'm also confident that my authentication
> > extension is working. When attempting to login to Report Manager,
I
> > have verified that the 'LogonUser' web service call is being made
and
> > returns true. The authentication ticket is being forwarded back to
> > the client browser.
> >
> > Something must be configured incorrectly in Report Manager but
there
> > are not that many settings and I've checked them all dozens of
times!
> > ;-)
> >
> > One difference between my implementation and the sample is that I'm
> > using SSL to access the reports server everywhere. I'm assuming
that
> > this would not cause problems for Report Manager. Does it?
> >
> > I'd appreciate any help. Anyone have any ideas? Attached is the
> > trace of the error message from Report Manager's log.
> >
> > Thanks,
> >
> > Stefan
> >
> > --
> > w3wp!ui!5a4!11/12/2004-18:09:20:: e ERROR: Unable to communicate
with
> > report server. Please verify that the report server is
operational.
> > w3wp!ui!5a4!11/12/2004-18:09:21:: e ERROR: HTTP status code --> 500
> > --Details--
> > CantCommunicateWithReportServerException: Unable to communicate
with
> > report server. Please verify that the report server is
operational.
> >
> > at
> Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at
>
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname)
> > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > at
>
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level)
> > at
>
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args)
> > at System.EventHandler.Invoke(Object sender, EventArgs e)
> > at System.Web.UI.Control.OnInit(EventArgs e)
> > at System.Web.UI.Control.InitRecursive(Control namingContainer)
> > at System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!5a4!11/12/2004-18:09:23:: e ERROR: Exception in
ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> > preserveForm)
> > at
Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> > preserveForm)
> > at
Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)|||I was able to find a workaround to the problem.
To get over the error that I had reported to you, I had to add the
following element to the ReportServer web.config file:
<!-- Allow anonymous access to the web service. Report Manager seems
to require this. -->
<location path="ReportService.asmx">
<system.web>
<authorization>
<allow users="?" />
</authorization>
</system.web>
</location>
It seems that Report Manager makes a call to the Report Server web
service on initialization. With only the "<deny users="?" />" rule
that was specified in the MSDN article
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp),
Report Manager was not authorized to contact the web service.
I worked with Microsoft partner services but I wasn't able to get
confirmation that my assumption was correct. My support contact was
not able to duplicate the problem using the sample forms authentication
app.
Good luck,
Stefan Leyhane
Firmwater Inc.|||Thanks! I really appreciate your tip- this problem was really
bothering me. I thought I must have messed up a config file- I guess I
put to much trust in that Microsoft Whitepaper
having complete directions. If you're listening, MS, please add this
to the Whitepaper. I was on the verge of giving up on Report
Services...
sleyhane@.gmail.com wrote:
> I was able to find a workaround to the problem.
> To get over the error that I had reported to you, I had to add the
> following element to the ReportServer web.config file:
> <!-- Allow anonymous access to the web service. Report Manager seems
> to require this. -->
> <location path="ReportService.asmx">
> <system.web>
> <authorization>
> <allow users="?" />
> </authorization>
> </system.web>
> </location>
> It seems that Report Manager makes a call to the Report Server web
> service on initialization. With only the "<deny users="?" />" rule
> that was specified in the MSDN article
>
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp),
> Report Manager was not authorized to contact the web service.
> I worked with Microsoft partner services but I wasn't able to get
> confirmation that my assumption was correct. My support contact was
> not able to duplicate the problem using the sample forms
authentication
> app.
> Good luck,
> Stefan Leyhane
> Firmwater Inc.|||Where in the nesting of the web.config did you place this additional
configuration information?
Also, are you using IP address or machine name when specifying the
ReportServerUrl in rsWebApp.config for ReportManager?
Thanks,
Jessica
"sleyhane@.gmail.com" wrote:
> I was able to find a workaround to the problem.
> To get over the error that I had reported to you, I had to add the
> following element to the ReportServer web.config file:
> <!-- Allow anonymous access to the web service. Report Manager seems
> to require this. -->
> <location path="ReportService.asmx">
> <system.web>
> <authorization>
> <allow users="?" />
> </authorization>
> </system.web>
> </location>
> It seems that Report Manager makes a call to the Report Server web
> service on initialization. With only the "<deny users="?" />" rule
> that was specified in the MSDN article
> (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp),
> Report Manager was not authorized to contact the web service.
> I worked with Microsoft partner services but I wasn't able to get
> confirmation that my assumption was correct. My support contact was
> not able to duplicate the problem using the sample forms authentication
> app.
> Good luck,
> Stefan Leyhane
> Firmwater Inc.
>|||Hello Guys AoA!
The only thing i had to do is as follows:
1) Open configuration file as C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager\RSWebApplication.config in
NotePad.Exe
2) ReportingServices by default install as :
<UI>
<ReportServerUrl>
http://localhost/ReportServer
</ReportServerUrl>
</UI>
3) Check about your directory structure , replace it if it is different from
yours.
4) Save and browse for report manager it should work now.
5) Best of luck
Thanks, Regards and AH
--
Allah Pakistan Ki Hifazat Farmay
"Jessica Landisman" wrote:
> Where in the nesting of the web.config did you place this additional
> configuration information?
> Also, are you using IP address or machine name when specifying the
> ReportServerUrl in rsWebApp.config for ReportManager?
> Thanks,
> Jessica
> "sleyhane@.gmail.com" wrote:
> > I was able to find a workaround to the problem.
> >
> > To get over the error that I had reported to you, I had to add the
> > following element to the ReportServer web.config file:
> >
> > <!-- Allow anonymous access to the web service. Report Manager seems
> > to require this. -->
> > <location path="ReportService.asmx">
> > <system.web>
> > <authorization>
> > <allow users="?" />
> > </authorization>
> > </system.web>
> > </location>
> >
> > It seems that Report Manager makes a call to the Report Server web
> > service on initialization. With only the "<deny users="?" />" rule
> > that was specified in the MSDN article
> > (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp),
> > Report Manager was not authorized to contact the web service.
> >
> > I worked with Microsoft partner services but I wasn't able to get
> > confirmation that my assumption was correct. My support contact was
> > not able to duplicate the problem using the sample forms authentication
> > app.
> >
> > Good luck,
> >
> > Stefan Leyhane
> > Firmwater Inc.
> >
> >