Report viewer and Visual Studio 2005

Hi, I developed ASP.Net web site project with Report Viewer,and i published the project and put it another system in my LAN, after creating the virtual directory in IIS i tried to browse. I am getting the following error:

[WebException: The request failed with HTTP status 401: Access Denied.] Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods() +211

The report server of my machine can be accessed thru http://sys40/reportserver from that system. But the published website is showing the above mentioned error, so i created the a new project, same as the one created in my system, in the other system. While debugging the project i am able to access the report server and view the report but wen the website is published and then browsed the above mentioned error is displayed.

Even the identity impersonate = true condition was made in web config file..

How can this issue be solved...

Thanks in advance.. Somu

HI,radmoorthy ：

You can give it a try with these following steps:

1. Verify your NTFS permissions for the users on the folder C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer.

He should have ("Read & Execute", "List Folder Content" and "Read").

2.In IIS for Reports and ReportServer app set Authenication method to "Basic authentication" from "Integrated Windows authentication".

If i misunderstand you about your question, please feel free to correct me and i will try to help you with more information.

I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance

|||

HI,radmoorthy ：

We are marking this issue as "Answered". If you have any new findings or concerns, please feel free to unmark the issue.
Thank you for your understanding!

Report Server renders incorrect URL for [Export] button

Good day,
We have a Report Server 2000 on a client site. The server is accessible
via server name (NetBIOS name) from the local LAN, but only via a DNS name
from outer regions of the WAN (these users are on a different but trusted
domain in the bigger forest). The reports render successfully when accessed
via either the NetBIOS or DNS name, but the URL rendered for the â'Exportâ'
functionality always refers to the NetBIOS (server) name. As a result users
on the WAN cannot use the â'Exportâ' functionality since the URL is not found
from that network location (without us adding a local host entry which is
against company policy).
The page source shows a number of variables, including dmRepUrl,
touchSessionUrl, printUrl, renderingUrl, exportUrl and docMapUrl â' these are
all incorrectly mapping to the server name.
I cannot find any matching entry in the Report Server configuration and it
seems as-if this code is output by a compiled assembly on the Report Server.
Are these URLs configurable at all?
Thank you,
James Avenant
GijimaAst ConsultantHi James,
Thank you for your posting!
From your description, my understanding of this issue is: You want to
deploy your report server on a WAN environment. If I misunderstood your
concern, please feel free to let me know.
Based on my experience, you need to specify a fully qualified domain name
instead of the Netbios name in the config file.
The first step is to change the following two registry values under this
key to the appropriate new values:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Reporting
Services\
RSVirtualDir = http://server.company.com/ReportServer (Old Value was
http://server/ReportServer)
WAVirtualDir = http://server.company.com/Reports (Old Value was
http://server/Reports)
The final piece is to make a change in the following to config files on
your reporting server:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\RSWebApplication.config
Each file will contain one instance of the server referenced by name
(http://server/ReportServer). Replace it with the fully qualified domain
name, keeping the trailing directory
(http://server.company.com/ReportServer)
Now just restart the service and you should be able to access the reports
inside or out using a fully qualified domain name.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.