I have a web page that has ReportViewer control in it. I load a report to it and it comes there nice and everything is ok. In report I have a link that opens another web page from the same web site where the original page is located (lets say that the original is in http//MySite and the page opened from the link is in MySite/Dialogs/MyDialog.aspx). The new page is opened with javascript function window.open(...) This new page contains reportviewer control, too and it's populated by the parameters given in the link url.
When I open the dialog page in the computer that has the web page and the report server on the same computer everything runs smoothly. But when I try to use the application from another computer it doesn't work right. The main page and the report opens to the browser in a proper way but when I click to the link that should open the dialog new browser window is opened but the reportviewer gives http 401 access denied error with ServerReport.SetProperties method.
I have set impersonate=true to the web config and I'm administrator in both computers that are used. What's the problem here? In another evironment it works nicely, but when the web site is used from another computer it gets broken...
Does ur report server have any credentials that u need to pass?
|||What credentials should you have? I'm using windows authentication in my web page (set in web.config). Does the report server has a user account that should be set to the control?
|||Suppose if i am trying to access my sql server data base from a different computer, windows authentication wont let me get into it... u will need a Username and password.. like sa or something like...
So i think u would need the same thing for report server... if i specify local host and the reports are hosted on ur computer i dont need any username or password to get in to the report server .. Suppose if u want to access it from a different computer and then give local host ... its gonna look in the local server and naturally not let u in to the report server...
regards,
Karen
|||The link url doesn't point to localhost. It has the name of the computer where the report server is running (like http//MyAnotherComputer/ReportPage/ReportDialog.aspx). So I'm not pointing to localserver at any time. Even in the environment where the the application is working I use the name of the computer in the link url.
then instead of the machine name ... try giving the ipaddress of that machine and one more when u try to access... http:/ServerName/Reports... does it prompt you for a username and password to get into it and view the reports?
|||Why would it make any difference to set ip address instead of computer name? The computers are both in the sam domain so there shouldn't be any problem with that. I gotta try the second test first time when I get back to my development computer. I'll let you know the result then.|||Why would it make any difference to set ip address instead of computer name? The computers are both in the same domain so there shouldn't be any problem with that. I gotta try the second test (accessing reports from another computer) first time when I get back to my development computer. I'll let you know the result then.|||Ok, I tried to access the report server with a browser on another computer (the url used washttp://computer_name/Reports) and worked just fine. Could it be possible that when I open another window from a report using a link, that the gredentials don't follow to the second window? If this is a case, what user account information should be forwarded to the dialog window? Should I use Web Service identity that is set for the Report Server? If I have set impersonate true in web.config, how does it affect to the behaviour of the control?|||I got this fixed! It seems that the application made a double hop. I made a mistake and called a report server on another computer instead of the one that was running on the web server.
No comments:
Post a Comment