HELP - SRS for Developer Ed installed instead of for Standard Ed.

I have been getting ready to finally put into my company's Production
Environment all the reports I have been developing in our Test Environment.
The Test Environment is SQL 2000 Developer Edition, and SRS was installed via
the CD that came in the box - I read that it said "For SQL Server 2000
Developer Edition only."
The decision was made that we did not need Enterprise Edition features, so a
Standard Edition SQL Server 2000 license was purchased and installed, be my
supervisor. He then used the SAME CD for SRS to install that I did. His
logic was "These Microsoft disks can detect what version of SQL Server is
running, and only install the components for the version detected."
I was unaware of this and have been loading the new server with reports and
running the Report Snapshots for the LONG RUNNING REPORTS, and setting up the
Shared Schedules and Permissions for the 125+ reports. I was about to start
creating the Manual Subscriptions for the various reports when I noticed the
'New Data-driven Subscription' button, and then realized what happened.
I would like to avoid redoing work, if possible. Is there a way to
over-install the Standard Edition Version of SQL Reporting Services on top of
the Developer Edition, so I don't have to re-setup everything? Is there a
way to downgrade/upgrade Editions without having to re-build the site?It is possible to do this. Before starting anything, of course, backup your
databases and the report server encryption key (see help topics on backing
up report server).
1. Uninstall the developer edition (this will not remove the report server
databases)
2. Install the standard edition. When asked for a database, use a new one.
Do NOT use the one from the developer install
3. After installation is complete, run rsconfig to point the new
installation at the old database
4. Delete the temporary database that you created as part of step 2.
If you created any data driven subscriptions, they will no longer run with
standard installed.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> I have been getting ready to finally put into my company's Production
> Environment all the reports I have been developing in our Test
Environment.
> The Test Environment is SQL 2000 Developer Edition, and SRS was installed
via
> the CD that came in the box - I read that it said "For SQL Server 2000
> Developer Edition only."
> The decision was made that we did not need Enterprise Edition features, so
a
> Standard Edition SQL Server 2000 license was purchased and installed, be
my
> supervisor. He then used the SAME CD for SRS to install that I did. His
> logic was "These Microsoft disks can detect what version of SQL Server is
> running, and only install the components for the version detected."
> I was unaware of this and have been loading the new server with reports
and
> running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
the
> Shared Schedules and Permissions for the 125+ reports. I was about to
start
> creating the Manual Subscriptions for the various reports when I noticed
the
> 'New Data-driven Subscription' button, and then realized what happened.
> I would like to avoid redoing work, if possible. Is there a way to
> over-install the Standard Edition Version of SQL Reporting Services on top
of
> the Developer Edition, so I don't have to re-setup everything? Is there a
> way to downgrade/upgrade Editions without having to re-build the site?|||I followed your instructions, except I hadn't yet deleted the 'temp' database
yet - didn't want to get rid of it until I knew things are working. They
aren't. I get the following error now:
This edition of Reporting Services does not support web farm deployment.
(rsInvalidRSEditionConfiguration) Get Online Help
Online help says the following:
You cannot use the Standard edition of Reporting Services to deploy multiple
report servers in a Web farms.
I am not using a Web Farm. I have one server that houses the source
databases for my company, and this SRS server that hosts the IIS website and
the SRS databases, both with standard edition. The RDS file points to the
source database server. Is this what SRS consideres a Web Farm? According
to your schemeatics on Reporting Services I have a proper license for both
servers.
"Brian Hartman [MSFT]" wrote:
> It is possible to do this. Before starting anything, of course, backup your
> databases and the report server encryption key (see help topics on backing
> up report server).
> 1. Uninstall the developer edition (this will not remove the report server
> databases)
> 2. Install the standard edition. When asked for a database, use a new one.
> Do NOT use the one from the developer install
> 3. After installation is complete, run rsconfig to point the new
> installation at the old database
> 4. Delete the temporary database that you created as part of step 2.
> If you created any data driven subscriptions, they will no longer run with
> standard installed.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > I have been getting ready to finally put into my company's Production
> > Environment all the reports I have been developing in our Test
> Environment.
> > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> via
> > the CD that came in the box - I read that it said "For SQL Server 2000
> > Developer Edition only."
> >
> > The decision was made that we did not need Enterprise Edition features, so
> a
> > Standard Edition SQL Server 2000 license was purchased and installed, be
> my
> > supervisor. He then used the SAME CD for SRS to install that I did. His
> > logic was "These Microsoft disks can detect what version of SQL Server is
> > running, and only install the components for the version detected."
> >
> > I was unaware of this and have been loading the new server with reports
> and
> > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> the
> > Shared Schedules and Permissions for the 125+ reports. I was about to
> start
> > creating the Manual Subscriptions for the various reports when I noticed
> the
> > 'New Data-driven Subscription' button, and then realized what happened.
> >
> > I would like to avoid redoing work, if possible. Is there a way to
> > over-install the Standard Edition Version of SQL Reporting Services on top
> of
> > the Developer Edition, so I don't have to re-setup everything? Is there a
> > way to downgrade/upgrade Editions without having to re-build the site?
>
>|||I went ahead and deleted the new 'temp' databases after running rsconfig
again. I still get the same errors listed below.
"Rob 'Spike' Stevens" wrote:
> I followed your instructions, except I hadn't yet deleted the 'temp' database
> yet - didn't want to get rid of it until I knew things are working. They
> aren't. I get the following error now:
> This edition of Reporting Services does not support web farm deployment.
> (rsInvalidRSEditionConfiguration) Get Online Help
> Online help says the following:
> You cannot use the Standard edition of Reporting Services to deploy multiple
> report servers in a Web farms.
> I am not using a Web Farm. I have one server that houses the source
> databases for my company, and this SRS server that hosts the IIS website and
> the SRS databases, both with standard edition. The RDS file points to the
> source database server. Is this what SRS consideres a Web Farm? According
> to your schemeatics on Reporting Services I have a proper license for both
> servers.
> "Brian Hartman [MSFT]" wrote:
> > It is possible to do this. Before starting anything, of course, backup your
> > databases and the report server encryption key (see help topics on backing
> > up report server).
> >
> > 1. Uninstall the developer edition (this will not remove the report server
> > databases)
> > 2. Install the standard edition. When asked for a database, use a new one.
> > Do NOT use the one from the developer install
> > 3. After installation is complete, run rsconfig to point the new
> > installation at the old database
> > 4. Delete the temporary database that you created as part of step 2.
> >
> > If you created any data driven subscriptions, they will no longer run with
> > standard installed.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights
> >
> > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > I have been getting ready to finally put into my company's Production
> > > Environment all the reports I have been developing in our Test
> > Environment.
> > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > via
> > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > Developer Edition only."
> > >
> > > The decision was made that we did not need Enterprise Edition features, so
> > a
> > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > my
> > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > running, and only install the components for the version detected."
> > >
> > > I was unaware of this and have been loading the new server with reports
> > and
> > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > the
> > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > start
> > > creating the Manual Subscriptions for the various reports when I noticed
> > the
> > > 'New Data-driven Subscription' button, and then realized what happened.
> > >
> > > I would like to avoid redoing work, if possible. Is there a way to
> > > over-install the Standard Edition Version of SQL Reporting Services on top
> > of
> > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > way to downgrade/upgrade Editions without having to re-build the site?
> >
> >
> >|||Also, Iâ'm finding this error message in the application log:
Reporting Services components from different editions cannot be used together.
"Rob 'Spike' Stevens" wrote:
> I went ahead and deleted the new 'temp' databases after running rsconfig
> again. I still get the same errors listed below.
> "Rob 'Spike' Stevens" wrote:
> > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > yet - didn't want to get rid of it until I knew things are working. They
> > aren't. I get the following error now:
> >
> > This edition of Reporting Services does not support web farm deployment.
> > (rsInvalidRSEditionConfiguration) Get Online Help
> >
> > Online help says the following:
> > You cannot use the Standard edition of Reporting Services to deploy multiple
> > report servers in a Web farms.
> >
> > I am not using a Web Farm. I have one server that houses the source
> > databases for my company, and this SRS server that hosts the IIS website and
> > the SRS databases, both with standard edition. The RDS file points to the
> > source database server. Is this what SRS consideres a Web Farm? According
> > to your schemeatics on Reporting Services I have a proper license for both
> > servers.
> >
> > "Brian Hartman [MSFT]" wrote:
> >
> > > It is possible to do this. Before starting anything, of course, backup your
> > > databases and the report server encryption key (see help topics on backing
> > > up report server).
> > >
> > > 1. Uninstall the developer edition (this will not remove the report server
> > > databases)
> > > 2. Install the standard edition. When asked for a database, use a new one.
> > > Do NOT use the one from the developer install
> > > 3. After installation is complete, run rsconfig to point the new
> > > installation at the old database
> > > 4. Delete the temporary database that you created as part of step 2.
> > >
> > > If you created any data driven subscriptions, they will no longer run with
> > > standard installed.
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no rights
> > >
> > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > I have been getting ready to finally put into my company's Production
> > > > Environment all the reports I have been developing in our Test
> > > Environment.
> > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > via
> > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > Developer Edition only."
> > > >
> > > > The decision was made that we did not need Enterprise Edition features, so
> > > a
> > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > my
> > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > running, and only install the components for the version detected."
> > > >
> > > > I was unaware of this and have been loading the new server with reports
> > > and
> > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > the
> > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > start
> > > > creating the Manual Subscriptions for the various reports when I noticed
> > > the
> > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > >
> > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > of
> > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > way to downgrade/upgrade Editions without having to re-build the site?
> > >
> > >
> > >|||I was able to find a solution. Thanks for the help you did provide.
"Rob 'Spike' Stevens" wrote:
> Also, Iâ'm finding this error message in the application log:
> Reporting Services components from different editions cannot be used together.
>
> "Rob 'Spike' Stevens" wrote:
> > I went ahead and deleted the new 'temp' databases after running rsconfig
> > again. I still get the same errors listed below.
> >
> > "Rob 'Spike' Stevens" wrote:
> >
> > > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > > yet - didn't want to get rid of it until I knew things are working. They
> > > aren't. I get the following error now:
> > >
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Online help says the following:
> > > You cannot use the Standard edition of Reporting Services to deploy multiple
> > > report servers in a Web farms.
> > >
> > > I am not using a Web Farm. I have one server that houses the source
> > > databases for my company, and this SRS server that hosts the IIS website and
> > > the SRS databases, both with standard edition. The RDS file points to the
> > > source database server. Is this what SRS consideres a Web Farm? According
> > > to your schemeatics on Reporting Services I have a proper license for both
> > > servers.
> > >
> > > "Brian Hartman [MSFT]" wrote:
> > >
> > > > It is possible to do this. Before starting anything, of course, backup your
> > > > databases and the report server encryption key (see help topics on backing
> > > > up report server).
> > > >
> > > > 1. Uninstall the developer edition (this will not remove the report server
> > > > databases)
> > > > 2. Install the standard edition. When asked for a database, use a new one.
> > > > Do NOT use the one from the developer install
> > > > 3. After installation is complete, run rsconfig to point the new
> > > > installation at the old database
> > > > 4. Delete the temporary database that you created as part of step 2.
> > > >
> > > > If you created any data driven subscriptions, they will no longer run with
> > > > standard installed.
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no rights
> > > >
> > > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > > I have been getting ready to finally put into my company's Production
> > > > > Environment all the reports I have been developing in our Test
> > > > Environment.
> > > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > > via
> > > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > > Developer Edition only."
> > > > >
> > > > > The decision was made that we did not need Enterprise Edition features, so
> > > > a
> > > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > > my
> > > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > > running, and only install the components for the version detected."
> > > > >
> > > > > I was unaware of this and have been loading the new server with reports
> > > > and
> > > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > > the
> > > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > > start
> > > > > creating the Manual Subscriptions for the various reports when I noticed
> > > > the
> > > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > > >
> > > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > > of
> > > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > > way to downgrade/upgrade Editions without having to re-build the site?
> > > >
> > > >
> > > >