Moving RS To A New Web Server Problems

Like several other users I have had problems moving to a new web server:
1) backup existing RS databases on database machine
2) delete existing RS databases on database machine
3) install RS on new Web Server
3a) allow RS to create databases on the original database machine using the
same connection ID
4) delete RS databases from database machine
5) restore original databases to database machine
6) access new web server and;
6a) receive a message that the database is not activated and get pointed to
BOL
6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
7) use the (unclear) BOL documentation to issue the command:
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
8) get back an error message:
Failure To Start Web Server.
NT Service Not Started.
9) kick a small dog and write this note.
thanks in advance for your help.
dlrDid you backup the keys using rskeymgmt.exe'
"Dennis Redfield" wrote:
> Like several other users I have had problems moving to a new web server:
> 1) backup existing RS databases on database machine
> 2) delete existing RS databases on database machine
> 3) install RS on new Web Server
> 3a) allow RS to create databases on the original database machine using the
> same connection ID
> 4) delete RS databases from database machine
> 5) restore original databases to database machine
> 6) access new web server and;
> 6a) receive a message that the database is not activated and get pointed to
> BOL
> 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> 7) use the (unclear) BOL documentation to issue the command:
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> 8) get back an error message:
> Failure To Start Web Server.
> NT Service Not Started.
> 9) kick a small dog and write this note.
>
> thanks in advance for your help.
> dlr
>
>|||yes! and...
dlr
"Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> Did you backup the keys using rskeymgmt.exe'
> "Dennis Redfield" wrote:
> > Like several other users I have had problems moving to a new web server:
> >
> > 1) backup existing RS databases on database machine
> > 2) delete existing RS databases on database machine
> > 3) install RS on new Web Server
> > 3a) allow RS to create databases on the original database machine using
the
> > same connection ID
> > 4) delete RS databases from database machine
> > 5) restore original databases to database machine
> > 6) access new web server and;
> > 6a) receive a message that the database is not activated and get pointed
to
> > BOL
> > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > 7) use the (unclear) BOL documentation to issue the command:
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > 8) get back an error message:
> > Failure To Start Web Server.
> > NT Service Not Started.
> > 9) kick a small dog and write this note.
> >
> >
> > thanks in advance for your help.
> >
> > dlr
> >
> >
> >|||Restore the keys to the new web server. You may need to restart
ReportService and IIS. I had to do the same thing before:
1) Backup the keys
2) install the RS on the new Web Server
3) Restore the keys
4) It worked for me. Did not need to use rsactivate.
"Dennis Redfield" wrote:
> yes! and...
> dlr
> "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > Did you backup the keys using rskeymgmt.exe'
> >
> > "Dennis Redfield" wrote:
> >
> > > Like several other users I have had problems moving to a new web server:
> > >
> > > 1) backup existing RS databases on database machine
> > > 2) delete existing RS databases on database machine
> > > 3) install RS on new Web Server
> > > 3a) allow RS to create databases on the original database machine using
> the
> > > same connection ID
> > > 4) delete RS databases from database machine
> > > 5) restore original databases to database machine
> > > 6) access new web server and;
> > > 6a) receive a message that the database is not activated and get pointed
> to
> > > BOL
> > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > 7) use the (unclear) BOL documentation to issue the command:
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > 8) get back an error message:
> > > Failure To Start Web Server.
> > > NT Service Not Started.
> > > 9) kick a small dog and write this note.
> > >
> > >
> > > thanks in advance for your help.
> > >
> > > dlr
> > >
> > >
> > >
>
>|||ok. I will try it.
dlr
"Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> Restore the keys to the new web server. You may need to restart
> ReportService and IIS. I had to do the same thing before:
> 1) Backup the keys
> 2) install the RS on the new Web Server
> 3) Restore the keys
> 4) It worked for me. Did not need to use rsactivate.
> "Dennis Redfield" wrote:
> > yes! and...
> > dlr
> > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > Did you backup the keys using rskeymgmt.exe'
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > Like several other users I have had problems moving to a new web
server:
> > > >
> > > > 1) backup existing RS databases on database machine
> > > > 2) delete existing RS databases on database machine
> > > > 3) install RS on new Web Server
> > > > 3a) allow RS to create databases on the original database machine
using
> > the
> > > > same connection ID
> > > > 4) delete RS databases from database machine
> > > > 5) restore original databases to database machine
> > > > 6) access new web server and;
> > > > 6a) receive a message that the database is not activated and get
pointed
> > to
> > > > BOL
> > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > > 7) use the (unclear) BOL documentation to issue the command:
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > 8) get back an error message:
> > > > Failure To Start Web Server.
> > > > NT Service Not Started.
> > > > 9) kick a small dog and write this note.
> > > >
> > > >
> > > > thanks in advance for your help.
> > > >
> > > > dlr
> > > >
> > > >
> > > >
> >
> >
> >|||Now This Is Fun.
Restored The Key File.
Exe reports success.
Start Web Browser and Receive Message:
This edition of Reporting Services does not support web farm deployment.
(rsInvalidRSEditionConfiguration) Get Online Help
Get Online Help returns:
You cannot use the Standard edition of Reporting Services to deploy multiple
report servers in a Web farms.
Web Farm! What Web Farm? Argh!
dlr
"Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> Restore the keys to the new web server. You may need to restart
> ReportService and IIS. I had to do the same thing before:
> 1) Backup the keys
> 2) install the RS on the new Web Server
> 3) Restore the keys
> 4) It worked for me. Did not need to use rsactivate.
> "Dennis Redfield" wrote:
> > yes! and...
> > dlr
> > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > Did you backup the keys using rskeymgmt.exe'
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > Like several other users I have had problems moving to a new web
server:
> > > >
> > > > 1) backup existing RS databases on database machine
> > > > 2) delete existing RS databases on database machine
> > > > 3) install RS on new Web Server
> > > > 3a) allow RS to create databases on the original database machine
using
> > the
> > > > same connection ID
> > > > 4) delete RS databases from database machine
> > > > 5) restore original databases to database machine
> > > > 6) access new web server and;
> > > > 6a) receive a message that the database is not activated and get
pointed
> > to
> > > > BOL
> > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > > 7) use the (unclear) BOL documentation to issue the command:
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > 8) get back an error message:
> > > > Failure To Start Web Server.
> > > > NT Service Not Started.
> > > > 9) kick a small dog and write this note.
> > > >
> > > >
> > > > thanks in advance for your help.
> > > >
> > > > dlr
> > > >
> > > >
> > > >
> >
> >
> >|||I will do the following to solve this problem (if possible)
- Remove Reporting Services Completely from the Web server machine.
- Reboot the computer
- Install SQL standard on the Web services machine (this is temp. only)
- Install reporting services and select the local SQL server
- It should work fine with no reports defined
- use rsconfig.exe to point to the rs database server
- use rskeysmgmt to restore the keys
- restart ReportService service and IIS
- If every thing works fine, you can remove SQL Server from the web server box
Hope this will help
"Dennis Redfield" wrote:
> Now This Is Fun.
> Restored The Key File.
> Exe reports success.
> Start Web Browser and Receive Message:
> This edition of Reporting Services does not support web farm deployment.
> (rsInvalidRSEditionConfiguration) Get Online Help
> Get Online Help returns:
> You cannot use the Standard edition of Reporting Services to deploy multiple
> report servers in a Web farms.
>
> Web Farm! What Web Farm? Argh!
> dlr
>
> "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > Restore the keys to the new web server. You may need to restart
> > ReportService and IIS. I had to do the same thing before:
> >
> > 1) Backup the keys
> > 2) install the RS on the new Web Server
> > 3) Restore the keys
> > 4) It worked for me. Did not need to use rsactivate.
> >
> > "Dennis Redfield" wrote:
> >
> > > yes! and...
> > > dlr
> > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in message
> > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > Did you backup the keys using rskeymgmt.exe'
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > Like several other users I have had problems moving to a new web
> server:
> > > > >
> > > > > 1) backup existing RS databases on database machine
> > > > > 2) delete existing RS databases on database machine
> > > > > 3) install RS on new Web Server
> > > > > 3a) allow RS to create databases on the original database machine
> using
> > > the
> > > > > same connection ID
> > > > > 4) delete RS databases from database machine
> > > > > 5) restore original databases to database machine
> > > > > 6) access new web server and;
> > > > > 6a) receive a message that the database is not activated and get
> pointed
> > > to
> > > > > BOL
> > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST! <834304>
> > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > >
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > 8) get back an error message:
> > > > > Failure To Start Web Server.
> > > > > NT Service Not Started.
> > > > > 9) kick a small dog and write this note.
> > > > >
> > > > >
> > > > > thanks in advance for your help.
> > > > >
> > > > > dlr
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||same results!
sad really.
I will open a support call on this monday.
dlr
"Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> I will do the following to solve this problem (if possible)
> - Remove Reporting Services Completely from the Web server machine.
> - Reboot the computer
> - Install SQL standard on the Web services machine (this is temp. only)
> - Install reporting services and select the local SQL server
> - It should work fine with no reports defined
> - use rsconfig.exe to point to the rs database server
> - use rskeysmgmt to restore the keys
> - restart ReportService service and IIS
> - If every thing works fine, you can remove SQL Server from the web server
box
> Hope this will help
> "Dennis Redfield" wrote:
> > Now This Is Fun.
> > Restored The Key File.
> > Exe reports success.
> >
> > Start Web Browser and Receive Message:
> > This edition of Reporting Services does not support web farm deployment.
> > (rsInvalidRSEditionConfiguration) Get Online Help
> >
> > Get Online Help returns:
> > You cannot use the Standard edition of Reporting Services to deploy
multiple
> > report servers in a Web farms.
> >
> >
> > Web Farm! What Web Farm? Argh!
> >
> > dlr
> >
> >
> > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > Restore the keys to the new web server. You may need to restart
> > > ReportService and IIS. I had to do the same thing before:
> > >
> > > 1) Backup the keys
> > > 2) install the RS on the new Web Server
> > > 3) Restore the keys
> > > 4) It worked for me. Did not need to use rsactivate.
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > yes! and...
> > > > dlr
> > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
message
> > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > Did you backup the keys using rskeymgmt.exe'
> > > > >
> > > > > "Dennis Redfield" wrote:
> > > > >
> > > > > > Like several other users I have had problems moving to a new web
> > server:
> > > > > >
> > > > > > 1) backup existing RS databases on database machine
> > > > > > 2) delete existing RS databases on database machine
> > > > > > 3) install RS on new Web Server
> > > > > > 3a) allow RS to create databases on the original database
machine
> > using
> > > > the
> > > > > > same connection ID
> > > > > > 4) delete RS databases from database machine
> > > > > > 5) restore original databases to database machine
> > > > > > 6) access new web server and;
> > > > > > 6a) receive a message that the database is not activated and get
> > pointed
> > > > to
> > > > > > BOL
> > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
<834304>
> > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > >
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > 8) get back an error message:
> > > > > > Failure To Start Web Server.
> > > > > > NT Service Not Started.
> > > > > > 9) kick a small dog and write this note.
> > > > > >
> > > > > >
> > > > > > thanks in advance for your help.
> > > > > >
> > > > > > dlr
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||This may be because of the edition of RS (Standard) as per below MSDN
link..Please check!
Sushil
"Dennis Redfield" wrote:
> same results!
> sad really.
> I will open a support call on this monday.
> dlr
> "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > I will do the following to solve this problem (if possible)
> >
> > - Remove Reporting Services Completely from the Web server machine.
> > - Reboot the computer
> > - Install SQL standard on the Web services machine (this is temp. only)
> > - Install reporting services and select the local SQL server
> > - It should work fine with no reports defined
> > - use rsconfig.exe to point to the rs database server
> > - use rskeysmgmt to restore the keys
> > - restart ReportService service and IIS
> > - If every thing works fine, you can remove SQL Server from the web server
> box
> >
> > Hope this will help
> >
> > "Dennis Redfield" wrote:
> >
> > > Now This Is Fun.
> > > Restored The Key File.
> > > Exe reports success.
> > >
> > > Start Web Browser and Receive Message:
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Get Online Help returns:
> > > You cannot use the Standard edition of Reporting Services to deploy
> multiple
> > > report servers in a Web farms.
> > >
> > >
> > > Web Farm! What Web Farm? Argh!
> > >
> > > dlr
> > >
> > >
> > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > Restore the keys to the new web server. You may need to restart
> > > > ReportService and IIS. I had to do the same thing before:
> > > >
> > > > 1) Backup the keys
> > > > 2) install the RS on the new Web Server
> > > > 3) Restore the keys
> > > > 4) It worked for me. Did not need to use rsactivate.
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > yes! and...
> > > > > dlr
> > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> message
> > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > >
> > > > > > "Dennis Redfield" wrote:
> > > > > >
> > > > > > > Like several other users I have had problems moving to a new web
> > > server:
> > > > > > >
> > > > > > > 1) backup existing RS databases on database machine
> > > > > > > 2) delete existing RS databases on database machine
> > > > > > > 3) install RS on new Web Server
> > > > > > > 3a) allow RS to create databases on the original database
> machine
> > > using
> > > > > the
> > > > > > > same connection ID
> > > > > > > 4) delete RS databases from database machine
> > > > > > > 5) restore original databases to database machine
> > > > > > > 6) access new web server and;
> > > > > > > 6a) receive a message that the database is not activated and get
> > > pointed
> > > > > to
> > > > > > > BOL
> > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> <834304>
> > > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > > >
> > > > >
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > 8) get back an error message:
> > > > > > > Failure To Start Web Server.
> > > > > > > NT Service Not Started.
> > > > > > > 9) kick a small dog and write this note.
> > > > > > >
> > > > > > >
> > > > > > > thanks in advance for your help.
> > > > > > >
> > > > > > > dlr
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Sorry! forgot to add link ..
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSerrors/htm/Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings_rsInvalidRSEditionConfiguration.asp
"Dennis Redfield" wrote:
> same results!
> sad really.
> I will open a support call on this monday.
> dlr
> "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > I will do the following to solve this problem (if possible)
> >
> > - Remove Reporting Services Completely from the Web server machine.
> > - Reboot the computer
> > - Install SQL standard on the Web services machine (this is temp. only)
> > - Install reporting services and select the local SQL server
> > - It should work fine with no reports defined
> > - use rsconfig.exe to point to the rs database server
> > - use rskeysmgmt to restore the keys
> > - restart ReportService service and IIS
> > - If every thing works fine, you can remove SQL Server from the web server
> box
> >
> > Hope this will help
> >
> > "Dennis Redfield" wrote:
> >
> > > Now This Is Fun.
> > > Restored The Key File.
> > > Exe reports success.
> > >
> > > Start Web Browser and Receive Message:
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Get Online Help returns:
> > > You cannot use the Standard edition of Reporting Services to deploy
> multiple
> > > report servers in a Web farms.
> > >
> > >
> > > Web Farm! What Web Farm? Argh!
> > >
> > > dlr
> > >
> > >
> > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > Restore the keys to the new web server. You may need to restart
> > > > ReportService and IIS. I had to do the same thing before:
> > > >
> > > > 1) Backup the keys
> > > > 2) install the RS on the new Web Server
> > > > 3) Restore the keys
> > > > 4) It worked for me. Did not need to use rsactivate.
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > yes! and...
> > > > > dlr
> > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> message
> > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > >
> > > > > > "Dennis Redfield" wrote:
> > > > > >
> > > > > > > Like several other users I have had problems moving to a new web
> > > server:
> > > > > > >
> > > > > > > 1) backup existing RS databases on database machine
> > > > > > > 2) delete existing RS databases on database machine
> > > > > > > 3) install RS on new Web Server
> > > > > > > 3a) allow RS to create databases on the original database
> machine
> > > using
> > > > > the
> > > > > > > same connection ID
> > > > > > > 4) delete RS databases from database machine
> > > > > > > 5) restore original databases to database machine
> > > > > > > 6) access new web server and;
> > > > > > > 6a) receive a message that the database is not activated and get
> > > pointed
> > > > > to
> > > > > > > BOL
> > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> <834304>
> > > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > > >
> > > > >
> > >
> rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > 8) get back an error message:
> > > > > > > Failure To Start Web Server.
> > > > > > > NT Service Not Started.
> > > > > > > 9) kick a small dog and write this note.
> > > > > > >
> > > > > > >
> > > > > > > thanks in advance for your help.
> > > > > > >
> > > > > > > dlr
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||indeed. that is the error page I AM GETTING NOW. What Web Farm?
I testing a realistic disaster recovery plan.
I started with a Web Server and a database server.
I simulate a database
crash and move backups of the existing database to a new machine and
Microsoft tells me I need a lic for a web farm!
Is this reasonable? In a pig's eye, perhaps.
thanks for playing.
dlr
"sushild" <sushild@.discussions.microsoft.com> wrote in message
news:91510B97-526F-4CCE-9638-880A73899022@.microsoft.com...
> Sorry! forgot to add link ..
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSerrors/htm/Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings_rsInvalidRSEditionConfiguration.asp
> "Dennis Redfield" wrote:
> > same results!
> > sad really.
> > I will open a support call on this monday.
> > dlr
> > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > > I will do the following to solve this problem (if possible)
> > >
> > > - Remove Reporting Services Completely from the Web server machine.
> > > - Reboot the computer
> > > - Install SQL standard on the Web services machine (this is temp.
only)
> > > - Install reporting services and select the local SQL server
> > > - It should work fine with no reports defined
> > > - use rsconfig.exe to point to the rs database server
> > > - use rskeysmgmt to restore the keys
> > > - restart ReportService service and IIS
> > > - If every thing works fine, you can remove SQL Server from the web
server
> > box
> > >
> > > Hope this will help
> > >
> > > "Dennis Redfield" wrote:
> > >
> > > > Now This Is Fun.
> > > > Restored The Key File.
> > > > Exe reports success.
> > > >
> > > > Start Web Browser and Receive Message:
> > > > This edition of Reporting Services does not support web farm
deployment.
> > > > (rsInvalidRSEditionConfiguration) Get Online Help
> > > >
> > > > Get Online Help returns:
> > > > You cannot use the Standard edition of Reporting Services to deploy
> > multiple
> > > > report servers in a Web farms.
> > > >
> > > >
> > > > Web Farm! What Web Farm? Argh!
> > > >
> > > > dlr
> > > >
> > > >
> > > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in
message
> > > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > > Restore the keys to the new web server. You may need to restart
> > > > > ReportService and IIS. I had to do the same thing before:
> > > > >
> > > > > 1) Backup the keys
> > > > > 2) install the RS on the new Web Server
> > > > > 3) Restore the keys
> > > > > 4) It worked for me. Did not need to use rsactivate.
> > > > >
> > > > > "Dennis Redfield" wrote:
> > > > >
> > > > > > yes! and...
> > > > > > dlr
> > > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> > message
> > > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > > >
> > > > > > > "Dennis Redfield" wrote:
> > > > > > >
> > > > > > > > Like several other users I have had problems moving to a new
web
> > > > server:
> > > > > > > >
> > > > > > > > 1) backup existing RS databases on database machine
> > > > > > > > 2) delete existing RS databases on database machine
> > > > > > > > 3) install RS on new Web Server
> > > > > > > > 3a) allow RS to create databases on the original database
> > machine
> > > > using
> > > > > > the
> > > > > > > > same connection ID
> > > > > > > > 4) delete RS databases from database machine
> > > > > > > > 5) restore original databases to database machine
> > > > > > > > 6) access new web server and;
> > > > > > > > 6a) receive a message that the database is not activated and
get
> > > > pointed
> > > > > > to
> > > > > > > > BOL
> > > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> > <834304>
> > > > > > > > 7) use the (unclear) BOL documentation to issue the command:
> > > > > > > >
> > > > > >
> > > >
> >
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > > 8) get back an error message:
> > > > > > > > Failure To Start Web Server.
> > > > > > > > NT Service Not Started.
> > > > > > > > 9) kick a small dog and write this note.
> > > > > > > >
> > > > > > > >
> > > > > > > > thanks in advance for your help.
> > > > > > > >
> > > > > > > > dlr
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||opps. actually simulate a web server crash (not a database crash) and move
web server to a new machine.
Microsoft tells me I need a lic for a web farm!
Is this reasonable? In a pig's eye, perhaps.
dlr
"Dennis Redfield" <dennis.redfield@.acadia-ins.com> wrote in message
news:uN6TkiBwEHA.2120@.TK2MSFTNGP14.phx.gbl...
> indeed. that is the error page I AM GETTING NOW. What Web Farm?
> I testing a realistic disaster recovery plan.
> I started with a Web Server and a database server.
> I simulate a database
> crash and move backups of the existing database to a new machine and
> Microsoft tells me I need a lic for a web farm!
> Is this reasonable? In a pig's eye, perhaps.
> thanks for playing.
> dlr
>
> "sushild" <sushild@.discussions.microsoft.com> wrote in message
> news:91510B97-526F-4CCE-9638-880A73899022@.microsoft.com...
> > Sorry! forgot to add link ..
> >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSerrors/htm/Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings_rsInvalidRSEditionConfiguration.asp
> >
> > "Dennis Redfield" wrote:
> >
> > > same results!
> > > sad really.
> > > I will open a support call on this monday.
> > > dlr
> > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in message
> > > news:35D10050-A54B-4757-AD09-2D28ED30EA25@.microsoft.com...
> > > > I will do the following to solve this problem (if possible)
> > > >
> > > > - Remove Reporting Services Completely from the Web server machine.
> > > > - Reboot the computer
> > > > - Install SQL standard on the Web services machine (this is temp.
> only)
> > > > - Install reporting services and select the local SQL server
> > > > - It should work fine with no reports defined
> > > > - use rsconfig.exe to point to the rs database server
> > > > - use rskeysmgmt to restore the keys
> > > > - restart ReportService service and IIS
> > > > - If every thing works fine, you can remove SQL Server from the web
> server
> > > box
> > > >
> > > > Hope this will help
> > > >
> > > > "Dennis Redfield" wrote:
> > > >
> > > > > Now This Is Fun.
> > > > > Restored The Key File.
> > > > > Exe reports success.
> > > > >
> > > > > Start Web Browser and Receive Message:
> > > > > This edition of Reporting Services does not support web farm
> deployment.
> > > > > (rsInvalidRSEditionConfiguration) Get Online Help
> > > > >
> > > > > Get Online Help returns:
> > > > > You cannot use the Standard edition of Reporting Services to
deploy
> > > multiple
> > > > > report servers in a Web farms.
> > > > >
> > > > >
> > > > > Web Farm! What Web Farm? Argh!
> > > > >
> > > > > dlr
> > > > >
> > > > >
> > > > > "Jamil Qasem" <JamilQasem@.discussions.microsoft.com> wrote in
> message
> > > > > news:CB748F7E-E9B2-4451-B9AC-32EE3F43E140@.microsoft.com...
> > > > > > Restore the keys to the new web server. You may need to restart
> > > > > > ReportService and IIS. I had to do the same thing before:
> > > > > >
> > > > > > 1) Backup the keys
> > > > > > 2) install the RS on the new Web Server
> > > > > > 3) Restore the keys
> > > > > > 4) It worked for me. Did not need to use rsactivate.
> > > > > >
> > > > > > "Dennis Redfield" wrote:
> > > > > >
> > > > > > > yes! and...
> > > > > > > dlr
> > > > > > > "Jamil Qasem" <Jamil Qasem@.discussions.microsoft.com> wrote in
> > > message
> > > > > > > news:CB9E0E1D-6966-4E9D-AA55-1EF7A9852F45@.microsoft.com...
> > > > > > > > Did you backup the keys using rskeymgmt.exe'
> > > > > > > >
> > > > > > > > "Dennis Redfield" wrote:
> > > > > > > >
> > > > > > > > > Like several other users I have had problems moving to a
new
> web
> > > > > server:
> > > > > > > > >
> > > > > > > > > 1) backup existing RS databases on database machine
> > > > > > > > > 2) delete existing RS databases on database machine
> > > > > > > > > 3) install RS on new Web Server
> > > > > > > > > 3a) allow RS to create databases on the original database
> > > machine
> > > > > using
> > > > > > > the
> > > > > > > > > same connection ID
> > > > > > > > > 4) delete RS databases from database machine
> > > > > > > > > 5) restore original databases to database machine
> > > > > > > > > 6) access new web server and;
> > > > > > > > > 6a) receive a message that the database is not activated
and
> get
> > > > > pointed
> > > > > > > to
> > > > > > > > > BOL
> > > > > > > > > 6b) get pointed to a KBase article THAT DOES NOT EXIST!
> > > <834304>
> > > > > > > > > 7) use the (unclear) BOL documentation to issue the
command:
> > > > > > > > >
> > > > > > >
> > > > >
> > >
>
rsactivate -udomain\username -ppassword -c"C:\{path}\rsreportserver.config"
> > > > > > > > > 8) get back an error message:
> > > > > > > > > Failure To Start Web Server.
> > > > > > > > > NT Service Not Started.
> > > > > > > > > 9) kick a small dog and write this note.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > thanks in advance for your help.
> > > > > > > > >
> > > > > > > > > dlr
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>