Prev: NULL Parameter in Data Driven Subscription
Next: "Action Canceled" Message when running the Report
From: Steven Cheng[MSFT] on 19 Jul 2006 05:20
Thanks for your followup John,

I thank we've made some progress on this. As you can find the remote server
now correctly recognize and validate the user on your cilent dev machine
and no longer display the 401 error, you can also check the IIS server's
log to see whether it list the client user's username in the request log
entry.

For the new problem you mentioned, I think it is somewhat specific to the
reportServer (server-side configuration). Have you tried directly use the
IE browser to visit that report in reportserver(not reportManager)? And
you can test by using the same account as you developed in VS IDE to access
that server report in IE browser(on XP dev box ) to see whether it report
the same error. The reportserver's url is like below by default:

Http://servername/reportserver/

Please let me know what you get on this. If convenient, you can also attach
some screenshot on the error.

Looking forward to your reply.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.

From: JPS on 19 Jul 2006 13:08
Hello Steven,

I have no problems connecting to the remote ReportServer or ReportManager
from a browser.

Thanks,
John

"Steven Cheng[MSFT]" wrote:

> Thanks for your followup John,
>
> I thank we've made some progress on this. As you can find the remote server
> now correctly recognize and validate the user on your cilent dev machine
> and no longer display the 401 error, you can also check the IIS server's
> log to see whether it list the client user's username in the request log
> entry.
>
> For the new problem you mentioned, I think it is somewhat specific to the
> reportServer (server-side configuration). Have you tried directly use the
> IE browser to visit that report in reportserver(not reportManager)? And
> you can test by using the same account as you developed in VS IDE to access
> that server report in IE browser(on XP dev box ) to see whether it report
> the same error. The reportserver's url is like below by default:
>
> Http://servername/reportserver/
>
> Please let me know what you get on this. If convenient, you can also attach
> some screenshot on the error.
>
> Looking forward to your reply.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
From: Steven Cheng[MSFT] on 21 Jul 2006 09:50
Thanks for your reply John,

Since you can visit the reportserver correctly through webbrowser, the
problem should be specific to the reportviewer control. Based on my
investigation, the reportViewer control internally use a pregenerated
webservice proxy to call the reportserver's webservice (the ReportService
and ReportExecutionService), so we may perform some test against the
webservice call to the remote reportserver. To do this, you can still use
your ASP.NET web application (running under the certain user account that
has mapped account on remote server), add the webreference to the reporting
service webservice:

#Report Server Web Service
http://msdn2.microsoft.com/en-us/library/ms152787.aspx

You can reference the two main reporting service webservices through the
following two endpoints under the reportserver web root:

ReportService2005.asmx

ReportExecution2005.asmx

So, the url will be like:

http://servername/reportserver/ReportService2005.asmx or
http://servername/reportserver/ReportExecution2005.asmx

Please try calling some methods on it to see whether your ASP.NET
application can correctly consume the webmethods. You can also check the
reportserver's log files to see what's the error generated when your client
ASP.NET application fails to access it.

BTW, I've also found some other former issue which had the similar symptom
with yours. In those cases, their reportServer application's IIS virtual
directory or IIS site is using a custom host header(dosn't use the default
website/machine name). And we need to check the some URL settings(like the
reportserver virtual directory, UrlRoot ....) in the
RsWebApplication.config file, you can find those setting in the following
BOL reference:

#RSWebApplication Configuration File
http://msdn2.microsoft.com/en-us/library/ms155878.aspx

Based on my local test, the <UrlRoot> element in the rsreportserver.config
file should be conform to your reportserver's external url(to other
machines).

<UrlRoot>http://myservermachine/reportserver</UrlRoot>

the file is under the reportserver application directory(C:\Program
Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer)

Here are some related threads over the internet discussing on the similar
issue:


http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=256312&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=256312&SiteID=1

Hope this helps. If you there is anything unclear or have any further
question, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



From: rwiethorn on 25 Jul 2006 16:16
Steven,
I too am having the same problem. I''m getting the error: The request failed
with HTTP status 401: Unauthorized.

I'm very sure this is happening because I am not passing my Credentials to
the ReportViewer Control. I cannot seem to get the syntax correct.

Here is how I did it using the rs.render method:
Dim strUserName_Dev As String =
System.Configuration.ConfigurationManager.AppSettings("UserName_Dev")

Dim strPWD_Dev As String =
System.Configuration.ConfigurationManager.AppSettings("PWD_Dev")

Dim strDomain_Dev As String =
System.Configuration.ConfigurationManager.AppSettings("Domain_Dev")

RS.Credentials = New System.Net.NetworkCredential(strUserName_Dev,
strPWD_Dev, strDomain_Dev)

Dim data As Byte()
data = RS_Dev.Render(Path2, Format, Nothing, Nothing, Parameters, _
Nothing, Nothing, Encoding, MimeType,
ParametersUsed, _
Warnings, StreamIDs)

The above methods works very well when I'm sending the output to a binary
stream or writer.

I need to now use the ReportViewer Control.

Can you please help me assign the same credentials to the ReportViewer
Control? I cannot figure out the syntax. Here is what I'm trying:

Getting the credentials:
RS.Credentials = New System.Net.NetworkCredential(strUserName_Dev,
strPWD_Dev, strDomain_Dev)
ReportViewer1.ServerReport.ReportServerCredentials.NetworkCredentials =
RS.credentials

I get a compile error telling me this is a Read Only Property.
I'm not sure what to do next.


Thanks,
Rwiethorn




"Steven Cheng[MSFT]" wrote:

> Thanks for your reply John,
>
> Since you can visit the reportserver correctly through webbrowser, the
> problem should be specific to the reportviewer control. Based on my
> investigation, the reportViewer control internally use a pregenerated
> webservice proxy to call the reportserver's webservice (the ReportService
> and ReportExecutionService), so we may perform some test against the
> webservice call to the remote reportserver. To do this, you can still use
> your ASP.NET web application (running under the certain user account that
> has mapped account on remote server), add the webreference to the reporting
> service webservice:
>
> #Report Server Web Service
> http://msdn2.microsoft.com/en-us/library/ms152787.aspx
>
> You can reference the two main reporting service webservices through the
> following two endpoints under the reportserver web root:
>
> ReportService2005.asmx
>
> ReportExecution2005.asmx
>
> So, the url will be like:
>
> http://servername/reportserver/ReportService2005.asmx or
> http://servername/reportserver/ReportExecution2005.asmx
>
> Please try calling some methods on it to see whether your ASP.NET
> application can correctly consume the webmethods. You can also check the
> reportserver's log files to see what's the error generated when your client
> ASP.NET application fails to access it.
>
> BTW, I've also found some other former issue which had the similar symptom
> with yours. In those cases, their reportServer application's IIS virtual
> directory or IIS site is using a custom host header(dosn't use the default
> website/machine name). And we need to check the some URL settings(like the
> reportserver virtual directory, UrlRoot ....) in the
> RsWebApplication.config file, you can find those setting in the following
> BOL reference:
>
> #RSWebApplication Configuration File
> http://msdn2.microsoft.com/en-us/library/ms155878.aspx
>
> Based on my local test, the <UrlRoot> element in the rsreportserver.config
> file should be conform to your reportserver's external url(to other
> machines).
>
> <UrlRoot>http://myservermachine/reportserver</UrlRoot>
>
> the file is under the reportserver application directory(C:\Program
> Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer)
>
> Here are some related threads over the internet discussing on the similar
> issue:
>
>
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=256312&SiteID=1
>
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=256312&SiteID=1
>
> Hope this helps. If you there is anything unclear or have any further
> question, please feel free to post here.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
> ==================================================
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
From: JPS on 25 Jul 2006 16:26
Hello Steven,

I still haven't had any luck; however, the Report Services was not set up to
a default install. I am going to reinstall and see if that helps.

Thanks,
John

"Steven Cheng[MSFT]" wrote:

> Thanks for your reply John,
>
> Since you can visit the reportserver correctly through webbrowser, the
> problem should be specific to the reportviewer control. Based on my
> investigation, the reportViewer control internally use a pregenerated
> webservice proxy to call the reportserver's webservice (the ReportService
> and ReportExecutionService), so we may perform some test against the
> webservice call to the remote reportserver. To do this, you can still use
> your ASP.NET web application (running under the certain user account that
> has mapped account on remote server), add the webreference to the reporting
> service webservice:
>
> #Report Server Web Service
> http://msdn2.microsoft.com/en-us/library/ms152787.aspx
>
> You can reference the two main reporting service webservices through the
> following two endpoints under the reportserver web root:
>
> ReportService2005.asmx
>
> ReportExecution2005.asmx
>
> So, the url will be like:
>
> http://servername/reportserver/ReportService2005.asmx or
> http://servername/reportserver/ReportExecution2005.asmx
>
> Please try calling some methods on it to see whether your ASP.NET
> application can correctly consume the webmethods. You can also check the
> reportserver's log files to see what's the error generated when your client
> ASP.NET application fails to access it.
>
> BTW, I've also found some other former issue which had the similar symptom
> with yours. In those cases, their reportServer application's IIS virtual
> directory or IIS site is using a custom host header(dosn't use the default
> website/machine name). And we need to check the some URL settings(like the
> reportserver virtual directory, UrlRoot ....) in the
> RsWebApplication.config file, you can find those setting in the following
> BOL reference:
>
> #RSWebApplication Configuration File
> http://msdn2.microsoft.com/en-us/library/ms155878.aspx
>
> Based on my local test, the <UrlRoot> element in the rsreportserver.config
> file should be conform to your reportserver's external url(to other
> machines).
>
> <UrlRoot>http://myservermachine/reportserver</UrlRoot>
>
> the file is under the reportserver application directory(C:\Program
> Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer)
>
> Here are some related threads over the internet discussing on the similar
> issue:
>
>
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=256312&SiteID=1
>
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=256312&SiteID=1
>
> Hope this helps. If you there is anything unclear or have any further
> question, please feel free to post here.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
> ==================================================
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: NULL Parameter in Data Driven Subscription
Next: "Action Canceled" Message when running the Report