all groups > sql server reporting services > september 2004 >
sql server reporting services :
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
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... [quoted text, click to view] > 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. [quoted text, click to view] "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. [quoted text, click to view] "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. [quoted text, click to view] "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. [quoted text, click to view] "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? > > > > > > > >
Rob, What was the solution? Thank you, Keith Sirmons [quoted text, click to view] "Rob 'Spike' Stevens" wrote: > 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? > > > > > > > > > >
Keith, did you ever recieve the answer on this issue? I am running into the same issue. Thanks [quoted text, click to view] "Keith Sirmons" wrote: > Rob, > > What was the solution? > > Thank you, > Keith Sirmons > > "Rob 'Spike' Stevens" wrote: > > > 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? > > > > > > > > > > > >
SRS leaves behind some COM+ entries on uninstall that could be causing you headaches. On your web server, after SRS uninstall, go to START--ADMIN TOOLS--COMPONENT SERVICES, in the MMC console go to COMPONENT SERVICES--COMPUTERS--MY COMPUTER--COM+ APPLICATIONS. You will see 2 entries for the SRS virtual directories. Delete these before reinstall. Don't know if this helps, but it was causing me problems. [quoted text, click to view] "Jack Mac" wrote: > Keith, did you ever recieve the answer on this issue? I am running into the > same issue. Thanks > > "Keith Sirmons" wrote: > > > Rob, > > > > What was the solution? > > > > Thank you, > > Keith Sirmons > > > > "Rob 'Spike' Stevens" wrote: > > > > > 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? > > > > > > > > > > > > > >
Jack, I have figured my problem out. What problem are you having? I may be able to help now. I think I took the long way to fix the errors, but it worked. Keith "Using a sledgehammer to fix a sore tooth" Sirmons [quoted text, click to view] "Jack Mac" wrote: > Keith, did you ever recieve the answer on this issue? I am running into the > same issue. Thanks > > "Keith Sirmons" wrote: > > > Rob, > > > > What was the solution? > > > > Thank you, > > Keith Sirmons > > > > "Rob 'Spike' Stevens" wrote: > > > > > 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? > > > > > > > > > > > > > >
I had installed the eval RS Edition on the following systems o Win2000 Pro o SQL Server 2000 Standard I have recieved the RS Standard on CD and while trying to install, I recieve a message "Can not upgrade, web farms are not supported with this version". Now, I never had a web farm and have used the RS Eval on the same server as SQL Server. I have completed many reports, user management, etc. and wish to reuse the database (RS) for the Full Version. I need advice. Thanks -- ~Jack~ [quoted text, click to view] "Keith Sirmons" wrote: > Jack, > > I have figured my problem out. What problem are you having? I may be able > to help now. I think I took the long way to fix the errors, but it worked. > > Keith > "Using a sledgehammer to fix a sore tooth" > Sirmons > > "Jack Mac" wrote: > > > Keith, did you ever recieve the answer on this issue? I am running into the > > same issue. Thanks > > > > "Keith Sirmons" wrote: > > > > > Rob, > > > > > > What was the solution? > > > > > > Thank you, > > > Keith Sirmons > > > > > > "Rob 'Spike' Stevens" wrote: > > > > > > > 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? > > > > > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
|
|