June 24, 2009 at 12:20 pm
First let me say that I have reports deployed to a website and they work with no problem. It's just that every time that I have to add or update a report I would have go to the web server and changed the access permissions to the default web site.
The problem is the site is getting to busy to continue to do this, if especially this would interrupt the site's access while this is being done.
My question, (I guess 2 questions); Is this the correct procedure to deploy reports to the report server, or do I have something set up wrong.
Also, if this is correct, does this permission change on the default website, block other websites access during this time frame to perform the deployment?
Thanks
R Barbre
June 24, 2009 at 12:57 pm
I am thinking this may be related to your employers security policy because deployment in one site should not affect other sites but IIS6 comes with most things disabled so check with your system admins and networking people because I do both Asp.net and SSRS and I have not seen such problems.
Kind regards,
Gift Peddie
June 25, 2009 at 5:33 am
At the present time, I am ALL that you mentioned. I guess somewhere I have set something worng and just not sure what. The only way I can deploy new / updated reports is to change the Directory Security on the Default Website from Anonymous Access to Integrated Windows Authentication. I then have to log in as the server administartor duing the deployment process from within the SQL Server Business Intelligence Development Studio IDE.
I mean this is no big deal for me to do, its just I do not know the effect on the 7 working websites on the server. Which none are actually tied to the Default Website. I feel / think that since I am not changing the directory secuity on those, that it should not have any effect.
Thanks
R Barbre
June 25, 2009 at 8:11 am
The only way I can deploy new / updated reports is to change the Directory Security on the Default Website from Anonymous Access to Integrated Windows Authentication.
Yep you have something to do with it because the SSRS site by default uses only integrated without anonymous access because you are supposed to ask your users to exclude the SSRS url in LAN configuration in IE security or add the url in Trusted site also in IE security that takes away the login prompt for most users. And define relevant permissions in Report Manager for each user. So here is default folder permissions in IIS 6 spend time with it and run some tests to see what you need.
http://support.microsoft.com/kb/812614
Kind regards,
Gift Peddie
June 25, 2009 at 8:52 am
Yep you have something to do with it because the SSRS site by default uses only integrated without anonymous access because you are supposed to ask your users to exclude the SSRS url in LAN configuration in IE security or add the url in Trusted site also in IE security that takes away the login prompt for most users. And define relevant permissions in Report Manager for each user. So here is default folder permissions in IIS 6 spend time with it and run some tests to see what you need.
Since the report server is used in an Internet and not a Intranet, the users do not need or have access to the Report Manager. The reports are called from the website by sending a URL to the report server with selected report and parameters.
That is working with no problems.
I was just questioning how I have to change the access on the IIS 6.0 default website since the report server is set up under it. And also, not being sure of how this effects any users of the other websites set up on this web server.
Not sure that has been answered yet. Did go ahead and deployed updated reports this morning while a user was in the process of going through a survey and it did not seem to bother or interrupt them.
Thanks for your help.
R Barbre
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply