|
|
You're in the
sql server reporting services
group:This edition of Reporting Services does not support web farm deplo
sql server reporting services:
I needed to move my IIS to a new server and upgrade it.
So this is what I did. Originally running on windows 2000 server w/ IIS 5 Backed up both the reportServer DB and the temp DB backed up the key file Installed a new server running server 2003 and IIS 6.0 deleted the orginal 2 databases installed SQL reporting resored both databases ran the following command: RSConfig -c -s Server name -d Reporting Services database name -a Sql|Windows -u User name -p User password (i did this in the bin direcotry) then ran this command: RSKeyMgmt.exe -e -f Path of file name -p Strong password now when i go to \\server\reports I get a login promt (not sure if this is part of IIS 6.0) but I log in and then it gives me the following error. This edition of Reporting Services does not support web farm deployment. (rsInvalidRSEditionConfiguration) Get Online Help Do i need to uninstall the reporting server from the first web server? I did stop the service once i installed the new server. Please help I need this back into production by tuesday. thanks Mike mike.fremont@trustile.com
Ok so what do i need to do to remove the information about the first web
server so it will work correctly and get rid of the error. Unfortunitly i only build and support the server and dont have the actaull reports to publish them. [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> I think you hit the nail on the head. Just stopping the first server doesn't > take away any of the information. > > When I bring up a new one I re-deploy the reports. If you are going to SP2 > the reports need to be re-deployed anyway to have the print control work > properly. My security is done with domain groups. I create a local reports > group on the reporting server and then I add the domain groups to that. Once > I have done that then deploying to a new server consists of installing it, > deploying reports, setting up data sources, setting up security. Doesn't > take too long. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Mike Fremont" <MikeFremont@discussions.microsoft.com> wrote in message > news:BEA20762-0492-4870-A7B5-47B763261F6A@microsoft.com... > >I needed to move my IIS to a new server and upgrade it. > > > > So this is what I did. > > Originally running on windows 2000 server w/ IIS 5 > > > > Backed up both the reportServer DB and the temp DB > > backed up the key file > > > > Installed a new server running server 2003 and IIS 6.0 > > deleted the orginal 2 databases > > installed SQL reporting > > > > resored both databases > > > > ran the following command: > > RSConfig -c -s Server name -d Reporting Services database name -a > > Sql|Windows -u User name -p User password > > (i did this in the bin direcotry) > > then ran this command: > > RSKeyMgmt.exe -e -f Path of file name -p Strong password > > > > now when i go to \\server\reports > > > > I get a login promt (not sure if this is part of IIS 6.0) > > but I log in and then it gives me the following error. > > > > This edition of Reporting Services does not support web farm deployment. > > (rsInvalidRSEditionConfiguration) Get Online Help > > > > Do i need to uninstall the reporting server from the first web server? I > > did stop the service once i installed the new server. > > > > Please help I need this back into production by tuesday. > > > > thanks > > Mike > > mike.fremont@trustile.com > > > > > > > > > > > > > >
I think you hit the nail on the head. Just stopping the first server doesn't
take away any of the information. When I bring up a new one I re-deploy the reports. If you are going to SP2 the reports need to be re-deployed anyway to have the print control work properly. My security is done with domain groups. I create a local reports group on the reporting server and then I add the domain groups to that. Once I have done that then deploying to a new server consists of installing it, deploying reports, setting up data sources, setting up security. Doesn't take too long. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Mike Fremont" <MikeFremont@discussions.microsoft.com> wrote in message news:BEA20762-0492-4870-A7B5-47B763261F6A@microsoft.com... >I needed to move my IIS to a new server and upgrade it. > > So this is what I did. > Originally running on windows 2000 server w/ IIS 5 > > Backed up both the reportServer DB and the temp DB > backed up the key file > > Installed a new server running server 2003 and IIS 6.0 > deleted the orginal 2 databases > installed SQL reporting > > resored both databases > > ran the following command: > RSConfig -c -s Server name -d Reporting Services database name -a > Sql|Windows -u User name -p User password > (i did this in the bin direcotry) > then ran this command: > RSKeyMgmt.exe -e -f Path of file name -p Strong password > > now when i go to \\server\reports > > I get a login promt (not sure if this is part of IIS 6.0) > but I log in and then it gives me the following error. > > This edition of Reporting Services does not support web farm deployment. > (rsInvalidRSEditionConfiguration) Get Online Help > > Do i need to uninstall the reporting server from the first web server? I > did stop the service once i installed the new server. > > Please help I need this back into production by tuesday. > > thanks > Mike > mike.fremont@trustile.com > > > > > >
Sorry, I am afraid I can't help you. Maybe someone else will jump in.
-- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Mike Fremont" <MikeFremont@discussions.microsoft.com> wrote in message news:243CAD16-4997-4664-AFDD-906956586538@microsoft.com... > Ok so what do i need to do to remove the information about the first web > server so it will work correctly and get rid of the error. Unfortunitly i > only build and support the server and dont have the actaull reports to > publish them. > > > > "Bruce L-C [MVP]" wrote: > >> I think you hit the nail on the head. Just stopping the first server >> doesn't >> take away any of the information. >> >> When I bring up a new one I re-deploy the reports. If you are going to >> SP2 >> the reports need to be re-deployed anyway to have the print control work >> properly. My security is done with domain groups. I create a local >> reports >> group on the reporting server and then I add the domain groups to that. >> Once >> I have done that then deploying to a new server consists of installing >> it, >> deploying reports, setting up data sources, setting up security. Doesn't >> take too long. >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> "Mike Fremont" <MikeFremont@discussions.microsoft.com> wrote in message >> news:BEA20762-0492-4870-A7B5-47B763261F6A@microsoft.com... >> >I needed to move my IIS to a new server and upgrade it. >> > >> > So this is what I did. >> > Originally running on windows 2000 server w/ IIS 5 >> > >> > Backed up both the reportServer DB and the temp DB >> > backed up the key file >> > >> > Installed a new server running server 2003 and IIS 6.0 >> > deleted the orginal 2 databases >> > installed SQL reporting >> > >> > resored both databases >> > >> > ran the following command: >> > RSConfig -c -s Server name -d Reporting Services database name -a >> > Sql|Windows -u User name -p User password >> > (i did this in the bin direcotry) >> > then ran this command: >> > RSKeyMgmt.exe -e -f Path of file name -p Strong password >> > >> > now when i go to \\server\reports >> > >> > I get a login promt (not sure if this is part of IIS 6.0) >> > but I log in and then it gives me the following error. >> > >> > This edition of Reporting Services does not support web farm >> > deployment. >> > (rsInvalidRSEditionConfiguration) Get Online Help >> > >> > Do i need to uninstall the reporting server from the first web server? >> > I >> > did stop the service once i installed the new server. >> > >> > Please help I need this back into production by tuesday. >> > >> > thanks >> > Mike >> > mike.fremont@trustile.com >> > >> > >> > >> > >> > >> > >> >> >>
You can delete the old machine from the farm by using rskeymgmt.
-- Brian Welcker Group Program Manager Microsoft SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Mike Fremont" <MikeFremont@discussions.microsoft.com> wrote in message news:243CAD16-4997-4664-AFDD-906956586538@microsoft.com... > Ok so what do i need to do to remove the information about the first web > server so it will work correctly and get rid of the error. Unfortunitly i > only build and support the server and dont have the actaull reports to > publish them. > > > > "Bruce L-C [MVP]" wrote: > >> I think you hit the nail on the head. Just stopping the first server >> doesn't >> take away any of the information. >> >> When I bring up a new one I re-deploy the reports. If you are going to >> SP2 >> the reports need to be re-deployed anyway to have the print control work >> properly. My security is done with domain groups. I create a local >> reports >> group on the reporting server and then I add the domain groups to that. >> Once >> I have done that then deploying to a new server consists of installing >> it, >> deploying reports, setting up data sources, setting up security. Doesn't >> take too long. >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> "Mike Fremont" <MikeFremont@discussions.microsoft.com> wrote in message >> news:BEA20762-0492-4870-A7B5-47B763261F6A@microsoft.com... >> >I needed to move my IIS to a new server and upgrade it. >> > >> > So this is what I did. >> > Originally running on windows 2000 server w/ IIS 5 >> > >> > Backed up both the reportServer DB and the temp DB >> > backed up the key file >> > >> > Installed a new server running server 2003 and IIS 6.0 >> > deleted the orginal 2 databases >> > installed SQL reporting >> > >> > resored both databases >> > >> > ran the following command: >> > RSConfig -c -s Server name -d Reporting Services database name -a >> > Sql|Windows -u User name -p User password >> > (i did this in the bin direcotry) >> > then ran this command: >> > RSKeyMgmt.exe -e -f Path of file name -p Strong password >> > >> > now when i go to \\server\reports >> > >> > I get a login promt (not sure if this is part of IIS 6.0) >> > but I log in and then it gives me the following error. >> > >> > This edition of Reporting Services does not support web farm >> > deployment. >> > (rsInvalidRSEditionConfiguration) Get Online Help >> > >> > Do i need to uninstall the reporting server from the first web server? >> > I >> > did stop the service once i installed the new server. >> > >> > Please help I need this back into production by tuesday. >> > >> > thanks >> > Mike >> > mike.fremont@trustile.com >> > >> > >> > >> > >> > >> > >> >> >>
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |