Renaming a SQL2005 - Unable to connect to RS from Management Studi

We have several 2005 boxes that have been renamed. RS works fine from a
browser and I can deplopy reports to it and see it with the config manager.
What I can't do is reference it from Management Studio. On the one box that
I restarted after sp_drop and sp_add, a message box pops up referring to the
old name. on the other box, niether the old name no the new name are found.
Where does the Studio get these names?For anyone who cares, I had to chnge the rsreportserver.config file. It was
referencing the old server names in the ulrroot section. This also impacted
the SAC tool's ability to manage the rs instance.
"Jeff Ericson" wrote:
> We have several 2005 boxes that have been renamed. RS works fine from a
> browser and I can deplopy reports to it and see it with the config manager.
> What I can't do is reference it from Management Studio. On the one box that
> I restarted after sp_drop and sp_add, a message box pops up referring to the
> old name. on the other box, niether the old name no the new name are found.
> Where does the Studio get these names?

Renamed SQL server and reporting services web site is down?

I renamed my SQL server (MOM 2005 server) and everything works fine execpt
the reporting services. If I type http://server/reports I get an error page
which says:
Error:
The request failed with HTTP status 401: Unauthorized.I'm assuming your reporting service is on the same server that you renamed?
If so, follow these steps.
I've used the steps on a couple of occassions and they work fine.
http://msdn2.microsoft.com/en-us/library/ms345235.aspx
Immy
"Gonzo" <no@.no.com> wrote in message
news:eWhERBVZHHA.3968@.TK2MSFTNGP06.phx.gbl...
>I renamed my SQL server (MOM 2005 server) and everything works fine execpt
>the reporting services. If I type http://server/reports I get an error
>page which says:
> Error:
>
> The request failed with HTTP status 401: Unauthorized.
>
>|||Hi, first of all I can't locate the Reporting Services Configuration tool
and where would the RSReportServer.config be?
"Immy" <therealasianbabe@.hotmail.com> wrote in message
news:OSdX6MVZHHA.5060@.TK2MSFTNGP04.phx.gbl...
> I'm assuming your reporting service is on the same server that you
> renamed? If so, follow these steps.
> I've used the steps on a couple of occassions and they work fine.
> http://msdn2.microsoft.com/en-us/library/ms345235.aspx
> Immy
> "Gonzo" <no@.no.com> wrote in message
> news:eWhERBVZHHA.3968@.TK2MSFTNGP06.phx.gbl...
>>I renamed my SQL server (MOM 2005 server) and everything works fine execpt
>>the reporting services. If I type http://server/reports I get an error
>>page which says:
>> Error:
>>
>> The request failed with HTTP status 401: Unauthorized.
>>
>>
>|||Immy, sorry I found them. A bog thanks as it all works now!!!
"Immy" <therealasianbabe@.hotmail.com> wrote in message
news:OSdX6MVZHHA.5060@.TK2MSFTNGP04.phx.gbl...
> I'm assuming your reporting service is on the same server that you
> renamed? If so, follow these steps.
> I've used the steps on a couple of occassions and they work fine.
> http://msdn2.microsoft.com/en-us/library/ms345235.aspx
> Immy
> "Gonzo" <no@.no.com> wrote in message
> news:eWhERBVZHHA.3968@.TK2MSFTNGP06.phx.gbl...
>>I renamed my SQL server (MOM 2005 server) and everything works fine execpt
>>the reporting services. If I type http://server/reports I get an error
>>page which says:
>> Error:
>>
>> The request failed with HTTP status 401: Unauthorized.
>>
>>
>

Removing Parameter Dependencies

I was wondering if anyone knows of a way to remove parameter dependencies.
I'm making a lot of reports for my company, but for some reason the Reports
Server is setting up a bunch of parameter dependencies, and it's causing
parameter entry to be extremely tedious (when you change a parameter that
another is dependent on, it'll reset the dependent parameter to its default
value).
So far the only way I've found is to manually edit the field in the report
server database - but I can't do that for all of the reports or ensure that
it'll stay updated in the future. Is there a way to edit parameter
dependencies?Any parameter which is used in a SQL statement will be re-evaluated often...
You can tell Reporting Services that it is NOT used in SQL by changing the
RDL...In SQL 2005 this will be an attribute in the dialog box...
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Kyle" <Kyle@.discussions.microsoft.com> wrote in message
news:B619A389-EB95-4DE8-AE05-5E46BB1A4208@.microsoft.com...
>I was wondering if anyone knows of a way to remove parameter dependencies.
> I'm making a lot of reports for my company, but for some reason the
> Reports
> Server is setting up a bunch of parameter dependencies, and it's causing
> parameter entry to be extremely tedious (when you change a parameter that
> another is dependent on, it'll reset the dependent parameter to its
> default
> value).
> So far the only way I've found is to manually edit the field in the report
> server database - but I can't do that for all of the reports or ensure
> that
> it'll stay updated in the future. Is there a way to edit parameter
> dependencies?|||All of the parameters are used in the SQL, and we're not using 2005 (and
won't be in the near future).
I've noticed that the report server doesn't automatically set up parameter
dependencies when no default value is given for the parameter. However, as
we would like to have default values for our parameters, this doesn't help me
much.
Kyle
"Wayne Snyder" wrote:
> Any parameter which is used in a SQL statement will be re-evaluated often...
> You can tell Reporting Services that it is NOT used in SQL by changing the
> RDL...In SQL 2005 this will be an attribute in the dialog box...
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Kyle" <Kyle@.discussions.microsoft.com> wrote in message
> news:B619A389-EB95-4DE8-AE05-5E46BB1A4208@.microsoft.com...
> >I was wondering if anyone knows of a way to remove parameter dependencies.
> > I'm making a lot of reports for my company, but for some reason the
> > Reports
> > Server is setting up a bunch of parameter dependencies, and it's causing
> > parameter entry to be extremely tedious (when you change a parameter that
> > another is dependent on, it'll reset the dependent parameter to its
> > default
> > value).
> >
> > So far the only way I've found is to manually edit the field in the report
> > server database - but I can't do that for all of the reports or ensure
> > that
> > it'll stay updated in the future. Is there a way to edit parameter
> > dependencies?
>
>|||Kyle,
I'm not sure what sort of defaults you are setting up, or if any of them are
dependant upon other parameters, but I ran into a similar situation, and here
is how I fixed it.
We have many reports where we wanted to display defalut dates (such as Date
From and Date To parameters being set to the first and last day of the
current month). If you set the parameter default using VB code as a
Non-Queried default value, it will assume that the parameter may be dependant
upon another parameter, and reevaluate the default whenever you edit
parameters before it. So, we created a dataset called DateParameters, and
used SQL to return two columns (BeginningOfMonth and EndOfMonth). For the
parameters, we set the default to "From Query" and used the columns of the
DateParameters data set to set the defaults. This prevented the parameters
as being labeled as dependant, and kept our reports from refreshing. If you
actually have defaults that are dependant upon other parameter values, you
can still use a dataset to do the computations, but your page will refresh
these parameters if their dependant values change.
Sorry this was so long-winded, but I hope it helps you.
David
"Kyle" wrote:
> All of the parameters are used in the SQL, and we're not using 2005 (and
> won't be in the near future).
> I've noticed that the report server doesn't automatically set up parameter
> dependencies when no default value is given for the parameter. However, as
> we would like to have default values for our parameters, this doesn't help me
> much.
> Kyle
> "Wayne Snyder" wrote:
> > Any parameter which is used in a SQL statement will be re-evaluated often...
> > You can tell Reporting Services that it is NOT used in SQL by changing the
> > RDL...In SQL 2005 this will be an attribute in the dialog box...
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "Kyle" <Kyle@.discussions.microsoft.com> wrote in message
> > news:B619A389-EB95-4DE8-AE05-5E46BB1A4208@.microsoft.com...
> > >I was wondering if anyone knows of a way to remove parameter dependencies.
> > > I'm making a lot of reports for my company, but for some reason the
> > > Reports
> > > Server is setting up a bunch of parameter dependencies, and it's causing
> > > parameter entry to be extremely tedious (when you change a parameter that
> > > another is dependent on, it'll reset the dependent parameter to its
> > > default
> > > value).
> > >
> > > So far the only way I've found is to manually edit the field in the report
> > > server database - but I can't do that for all of the reports or ensure
> > > that
> > > it'll stay updated in the future. Is there a way to edit parameter
> > > dependencies?
> >
> >
> >|||Thank you very much!
That solved almost every single problem I was having with parameters. Now
if I can just figure out how to get tooltips to display for the parameter
form boxes...
Thanks again!
Kyle
"David Siebert" wrote:
> Kyle,
> I'm not sure what sort of defaults you are setting up, or if any of them are
> dependant upon other parameters, but I ran into a similar situation, and here
> is how I fixed it.
> We have many reports where we wanted to display defalut dates (such as Date
> From and Date To parameters being set to the first and last day of the
> current month). If you set the parameter default using VB code as a
> Non-Queried default value, it will assume that the parameter may be dependant
> upon another parameter, and reevaluate the default whenever you edit
> parameters before it. So, we created a dataset called DateParameters, and
> used SQL to return two columns (BeginningOfMonth and EndOfMonth). For the
> parameters, we set the default to "From Query" and used the columns of the
> DateParameters data set to set the defaults. This prevented the parameters
> as being labeled as dependant, and kept our reports from refreshing. If you
> actually have defaults that are dependant upon other parameter values, you
> can still use a dataset to do the computations, but your page will refresh
> these parameters if their dependant values change.
> Sorry this was so long-winded, but I hope it helps you.
> David
> "Kyle" wrote:
> > All of the parameters are used in the SQL, and we're not using 2005 (and
> > won't be in the near future).
> >
> > I've noticed that the report server doesn't automatically set up parameter
> > dependencies when no default value is given for the parameter. However, as
> > we would like to have default values for our parameters, this doesn't help me
> > much.
> >
> > Kyle
> >
> > "Wayne Snyder" wrote:
> >
> > > Any parameter which is used in a SQL statement will be re-evaluated often...
> > > You can tell Reporting Services that it is NOT used in SQL by changing the
> > > RDL...In SQL 2005 this will be an attribute in the dialog box...
> > >
> > > --
> > > Wayne Snyder MCDBA, SQL Server MVP
> > > Mariner, Charlotte, NC
> > > (Please respond only to the newsgroup.)
> > >
> > > I support the Professional Association for SQL Server ( PASS) and it's
> > > community of SQL Professionals.
> > > "Kyle" <Kyle@.discussions.microsoft.com> wrote in message
> > > news:B619A389-EB95-4DE8-AE05-5E46BB1A4208@.microsoft.com...
> > > >I was wondering if anyone knows of a way to remove parameter dependencies.
> > > > I'm making a lot of reports for my company, but for some reason the
> > > > Reports
> > > > Server is setting up a bunch of parameter dependencies, and it's causing
> > > > parameter entry to be extremely tedious (when you change a parameter that
> > > > another is dependent on, it'll reset the dependent parameter to its
> > > > default
> > > > value).
> > > >
> > > > So far the only way I've found is to manually edit the field in the report
> > > > server database - but I can't do that for all of the reports or ensure
> > > > that
> > > > it'll stay updated in the future. Is there a way to edit parameter
> > > > dependencies?
> > >
> > >
> > >

Removing deployed reports

Hi All,

I deployed many reports on sql server reporting services. I want to remove some of the unnecessary reports. How to remove it?

thanking You,

Thanks,

Muniappan Kandasamy

SQL 2005? If so, in SQL Server Management Studio you can attach to your reporting server instance and then select the report and set its hidden property to true, or delete it outright:

On the login popup, check out your list of Server Types provided, you should see a 'Reporting Services' item. If you are already in the Mgmt studio, on the object explorer, click the Connect button and in the dropdown you'll see a reporting services item. Once you are in, you should be able to find your report objects and do whatever you need to them.

Cheers!

Wayne

|||

Thank you

Removing deployed reports

Hi All,

I deployed many reports in sql server 2005 reporting services. I want to remove some of the unnecessary reports. How to remove those reports?

thank you

thanks,

Muniappan Kandasamy

1. Open report manager (http://localhost/reports).

2. Navigate to your report server project.

3. Click the Show Details button.

4. Check the reports you want to delete then click delete.

Removing BUILTIN\Administrators

We need to remove the BUILTIN\Administrators from reporting services. I.T. personnel do not want to be able to see restricted reports. We have two department users that have been added as Content Managers and we are running reporting services under a created domain user account that we created and not a system service. I have removed BUILTIN\Administrators from the Home folder and when I check, it comes right back. Do I need to deny access to BUILTIN\Administrator on SQL Server 2005 itself? I would apprecate any suggestions.

I used the link below and followed the steps to remove the BUILTIN\Administrators group from SQL Server 2005 and SRS 2005. Hopefully this will be helpful to others.

http://www.mssqltips.com/tip.asp?tip1017