The web interface for ReportServer does not work in Mozilla Firefox 1.0:
reports appear as blank pages.
Is this due to use of ActiveX controls in the browser, or is there some
other reason - and who's problem is it?
brianSomeone awhile back investigated this pretty extensively and I gather it has
to do with how the web interface was designed. It is not an active x
problem. If you want to provide support for Mozilla you will need to use
your own front end instead of the one provided by MS.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brian Smith" <bsmith@.NO.SPAM.schemiotics.co.uk> wrote in message
news:uwkkBk5OFHA.580@.TK2MSFTNGP15.phx.gbl...
> The web interface for ReportServer does not work in Mozilla Firefox 1.0:
> reports appear as blank pages.
> Is this due to use of ActiveX controls in the browser, or is there some
> other reason - and who's problem is it?
> brian
Showing posts with label web. Show all posts
Showing posts with label web. Show all posts
Friday, March 30, 2012
Mozilla allignment problem with reports
Hello,
I have generated reports in my web application using SQL Server Reporting services. Its working and displaying fine when I open the application in Internet Explorer. But with Firefox Mozilla, the display of report contents is not working proper. Please advise.
Thanks in advance,
Ambili.
Hi,
In Reporting Services, you use a Web browser to view reports and run Report Manager. Not all report functionality is supported by all browsers. The following table describes report functionality restrictions for the supported browsers.
So please make sure if your explorer type match the needs to run reporting service.
For details, see
http://msdn2.microsoft.com/en-us/library/ms156511.aspx
Thanks.
Hello,
Thanks for the prompt response.
As you have specified, I could see that Searching within thereport is not possible with Mozilla, which is possible in IE.
But my major issue is that the data inside the report is notdisplaying properly ( i mean, the formatting of the report contents). In IE, data inside the report is displaying properly. But in Mozilla, only first character of each column is displayed in each row. Any help on this issue will be appreciated.
Thanks in advance,
Ambili.
If the output is mushed height-wise, add this to the ReportServices.css file:
* Fix report IFRAME height for Firefox */
.DocMapAndReportFrame
{
min-height: 860px;
}
For output mushed width-wise, add an empty textbox the width of the expected output.
Hope that helps.
|||Hello,
Thanks a lot for the valuable information.It helped me to solve the problem in case of height-wise alignment in mozilla and I am working with the case of width-wise alignment issue using the idea which you have specified.
Thanks again.
-Ambili.
|||Hi Corwin:
Thank you for the code help in the ReportServices.css file. It worked for me using:
/* Fix report IFRAME height for Firefox */
.DocMapAndReportFrame
{
min-height: 860px;
}
I just had to put the forward slash ( / ) in front of * Fix report IFRAME height for Firefox */
Wednesday, March 21, 2012
Moving SQL Server/Report Server off public IP
We are planning on moving our SQL Server off of the same machine as our web
server and securing it behind a firewall, removing all accessibility by
public IP. However, our web app uses the report viewer control to render
reports, and it points to <default IP of the web server>/ReportServer, which
was set up by Reporting Services. The client does in fact make a connection
to that IP. If SQL Server (and consequently Reporting Services) moves to
where it cannot be accessed by a client, how can they view reports?So, does the lack of answer here mean that I must have SQL Server on a
public IP, or does it mean the answer's already somewhere else, waiting for
me to look?
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:ePnImS54EHA.1192@.tk2msftngp13.phx.gbl...
> We are planning on moving our SQL Server off of the same machine as our
> web server and securing it behind a firewall, removing all accessibility
> by public IP. However, our web app uses the report viewer control to
> render reports, and it points to <default IP of the web
> server>/ReportServer, which was set up by Reporting Services. The client
> does in fact make a connection to that IP. If SQL Server (and
> consequently Reporting Services) moves to where it cannot be accessed by a
> client, how can they view reports?
>|||There are two ways to integrate with RS. URL integration and web services. I
have not used the report viewer control but my impression (and your
description of the issue you are having confirms it) is that it uses URL
integration. The advantage of URL integration is simplicity plus drill
through (jump to report) works as well. With web services you basically have
to implement your own jump to report (drill through). Web services takes
more work but you have more control. With web services you can create an
application where your web server integrates to reporting services behind
the firewall where the client PCs never directly access the server behind
the firewall. That is one option for you.
Another option for you is to have the SQL Server Database behind the
firewall and the Reporting Services application on the public IP. You have
to buy another license but it resolves your problem. Plus, given the cost to
rework your solution to use web services would most likely cost more than
purchasing another license. Also, keep in mind that your data you report
against (which most likely is what you want behind the firewall) does not
have to be on the same SQL Server that is used by RS. So you could still
have SQL Server on the public IP but use it only for RS and have all the
data used by the reports on a second SQL Server that is behind the firewall.
HTH,
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:OC73ygQ6EHA.1120@.TK2MSFTNGP11.phx.gbl...
> So, does the lack of answer here mean that I must have SQL Server on a
> public IP, or does it mean the answer's already somewhere else, waiting
for
> me to look?
> "DJM" <msnews@.puddlestheshark.com> wrote in message
> news:ePnImS54EHA.1192@.tk2msftngp13.phx.gbl...
> > We are planning on moving our SQL Server off of the same machine as our
> > web server and securing it behind a firewall, removing all accessibility
> > by public IP. However, our web app uses the report viewer control to
> > render reports, and it points to <default IP of the web
> > server>/ReportServer, which was set up by Reporting Services. The
client
> > does in fact make a connection to that IP. If SQL Server (and
> > consequently Reporting Services) moves to where it cannot be accessed by
a
> > client, how can they view reports?
> >
>|||Thank you so much for the response. I was hoping to avoid having to get
another SQL Server license for the front end simply for Reporting Services
(not to mention it would mean pushing reports to the web server[s] instead
of keeping it on the SQL Server close to the data), but that looks like it
would be the easiest.
Thanks again for the info.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ewzXvrQ6EHA.1408@.TK2MSFTNGP10.phx.gbl...
> There are two ways to integrate with RS. URL integration and web services.
> I
> have not used the report viewer control but my impression (and your
> description of the issue you are having confirms it) is that it uses URL
> integration. The advantage of URL integration is simplicity plus drill
> through (jump to report) works as well. With web services you basically
> have
> to implement your own jump to report (drill through). Web services takes
> more work but you have more control. With web services you can create an
> application where your web server integrates to reporting services behind
> the firewall where the client PCs never directly access the server behind
> the firewall. That is one option for you.
> Another option for you is to have the SQL Server Database behind the
> firewall and the Reporting Services application on the public IP. You have
> to buy another license but it resolves your problem. Plus, given the cost
> to
> rework your solution to use web services would most likely cost more than
> purchasing another license. Also, keep in mind that your data you report
> against (which most likely is what you want behind the firewall) does not
> have to be on the same SQL Server that is used by RS. So you could still
> have SQL Server on the public IP but use it only for RS and have all the
> data used by the reports on a second SQL Server that is behind the
> firewall.
> HTH,
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "DJM" <msnews@.puddlestheshark.com> wrote in message
> news:OC73ygQ6EHA.1120@.TK2MSFTNGP11.phx.gbl...
>> So, does the lack of answer here mean that I must have SQL Server on a
>> public IP, or does it mean the answer's already somewhere else, waiting
> for
>> me to look?
>> "DJM" <msnews@.puddlestheshark.com> wrote in message
>> news:ePnImS54EHA.1192@.tk2msftngp13.phx.gbl...
>> > We are planning on moving our SQL Server off of the same machine as our
>> > web server and securing it behind a firewall, removing all
>> > accessibility
>> > by public IP. However, our web app uses the report viewer control to
>> > render reports, and it points to <default IP of the web
>> > server>/ReportServer, which was set up by Reporting Services. The
> client
>> > does in fact make a connection to that IP. If SQL Server (and
>> > consequently Reporting Services) moves to where it cannot be accessed
>> > by
> a
>> > client, how can they view reports?
>> >
>>
>
server and securing it behind a firewall, removing all accessibility by
public IP. However, our web app uses the report viewer control to render
reports, and it points to <default IP of the web server>/ReportServer, which
was set up by Reporting Services. The client does in fact make a connection
to that IP. If SQL Server (and consequently Reporting Services) moves to
where it cannot be accessed by a client, how can they view reports?So, does the lack of answer here mean that I must have SQL Server on a
public IP, or does it mean the answer's already somewhere else, waiting for
me to look?
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:ePnImS54EHA.1192@.tk2msftngp13.phx.gbl...
> We are planning on moving our SQL Server off of the same machine as our
> web server and securing it behind a firewall, removing all accessibility
> by public IP. However, our web app uses the report viewer control to
> render reports, and it points to <default IP of the web
> server>/ReportServer, which was set up by Reporting Services. The client
> does in fact make a connection to that IP. If SQL Server (and
> consequently Reporting Services) moves to where it cannot be accessed by a
> client, how can they view reports?
>|||There are two ways to integrate with RS. URL integration and web services. I
have not used the report viewer control but my impression (and your
description of the issue you are having confirms it) is that it uses URL
integration. The advantage of URL integration is simplicity plus drill
through (jump to report) works as well. With web services you basically have
to implement your own jump to report (drill through). Web services takes
more work but you have more control. With web services you can create an
application where your web server integrates to reporting services behind
the firewall where the client PCs never directly access the server behind
the firewall. That is one option for you.
Another option for you is to have the SQL Server Database behind the
firewall and the Reporting Services application on the public IP. You have
to buy another license but it resolves your problem. Plus, given the cost to
rework your solution to use web services would most likely cost more than
purchasing another license. Also, keep in mind that your data you report
against (which most likely is what you want behind the firewall) does not
have to be on the same SQL Server that is used by RS. So you could still
have SQL Server on the public IP but use it only for RS and have all the
data used by the reports on a second SQL Server that is behind the firewall.
HTH,
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:OC73ygQ6EHA.1120@.TK2MSFTNGP11.phx.gbl...
> So, does the lack of answer here mean that I must have SQL Server on a
> public IP, or does it mean the answer's already somewhere else, waiting
for
> me to look?
> "DJM" <msnews@.puddlestheshark.com> wrote in message
> news:ePnImS54EHA.1192@.tk2msftngp13.phx.gbl...
> > We are planning on moving our SQL Server off of the same machine as our
> > web server and securing it behind a firewall, removing all accessibility
> > by public IP. However, our web app uses the report viewer control to
> > render reports, and it points to <default IP of the web
> > server>/ReportServer, which was set up by Reporting Services. The
client
> > does in fact make a connection to that IP. If SQL Server (and
> > consequently Reporting Services) moves to where it cannot be accessed by
a
> > client, how can they view reports?
> >
>|||Thank you so much for the response. I was hoping to avoid having to get
another SQL Server license for the front end simply for Reporting Services
(not to mention it would mean pushing reports to the web server[s] instead
of keeping it on the SQL Server close to the data), but that looks like it
would be the easiest.
Thanks again for the info.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ewzXvrQ6EHA.1408@.TK2MSFTNGP10.phx.gbl...
> There are two ways to integrate with RS. URL integration and web services.
> I
> have not used the report viewer control but my impression (and your
> description of the issue you are having confirms it) is that it uses URL
> integration. The advantage of URL integration is simplicity plus drill
> through (jump to report) works as well. With web services you basically
> have
> to implement your own jump to report (drill through). Web services takes
> more work but you have more control. With web services you can create an
> application where your web server integrates to reporting services behind
> the firewall where the client PCs never directly access the server behind
> the firewall. That is one option for you.
> Another option for you is to have the SQL Server Database behind the
> firewall and the Reporting Services application on the public IP. You have
> to buy another license but it resolves your problem. Plus, given the cost
> to
> rework your solution to use web services would most likely cost more than
> purchasing another license. Also, keep in mind that your data you report
> against (which most likely is what you want behind the firewall) does not
> have to be on the same SQL Server that is used by RS. So you could still
> have SQL Server on the public IP but use it only for RS and have all the
> data used by the reports on a second SQL Server that is behind the
> firewall.
> HTH,
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "DJM" <msnews@.puddlestheshark.com> wrote in message
> news:OC73ygQ6EHA.1120@.TK2MSFTNGP11.phx.gbl...
>> So, does the lack of answer here mean that I must have SQL Server on a
>> public IP, or does it mean the answer's already somewhere else, waiting
> for
>> me to look?
>> "DJM" <msnews@.puddlestheshark.com> wrote in message
>> news:ePnImS54EHA.1192@.tk2msftngp13.phx.gbl...
>> > We are planning on moving our SQL Server off of the same machine as our
>> > web server and securing it behind a firewall, removing all
>> > accessibility
>> > by public IP. However, our web app uses the report viewer control to
>> > render reports, and it points to <default IP of the web
>> > server>/ReportServer, which was set up by Reporting Services. The
> client
>> > does in fact make a connection to that IP. If SQL Server (and
>> > consequently Reporting Services) moves to where it cannot be accessed
>> > by
> a
>> > client, how can they view reports?
>> >
>>
>
moving SQL Server to remote web server
I'm very new to using SQL Server and have a very basic question that I was hoping someone could help answer or point me in the right direction.
Ive been searching for the information and have been unable to find what Im looking for. I might be using the wrong keywords.
This is what Im trying to find. I have found some information on building a database in Access and porting it over to SQL Server. The information that I've found discusses on a simple level how to use Enterprise Manager to port over using the following steps:
Enterprise Manager:
1) Database level >> Action Menu >> New Database setup a name
2) Highlight new database name
3) Tools Menu >> Data Transformation Services >> Import Data
Data Source = Microsoft Access
Okay, so that is pretty straightforward. If I created the web page using the Access DB and I am using an OLE-DB connection string then once I port over to SQL Server all I should need to change is the connection string to a SQL Server connection string. Is that correct? Anyone know where I can find some information about this process and specifically how to upload the new SQL Server DB to the remote web server? To upload an Access DB, I just FTP the DB to the site directory. Pretty easy. If I understand right, you dont do that with a SQL Server DB, but rather replicate the DB to the remote server. I would like to understand how to move the SQL Server DB to a remote web server. Im trying to learn the steps and how it is done? Thanks in advance for any help.
-D-Follow these links :
http://support.microsoft.com/default.aspx?scid=kb;en-us;247931
http://www.faqts.com/knowledge_base/view.phtml/aid/3332
If this is not what you're looking then kindly come up with more explanation.sql
Ive been searching for the information and have been unable to find what Im looking for. I might be using the wrong keywords.
This is what Im trying to find. I have found some information on building a database in Access and porting it over to SQL Server. The information that I've found discusses on a simple level how to use Enterprise Manager to port over using the following steps:
Enterprise Manager:
1) Database level >> Action Menu >> New Database setup a name
2) Highlight new database name
3) Tools Menu >> Data Transformation Services >> Import Data
Data Source = Microsoft Access
Okay, so that is pretty straightforward. If I created the web page using the Access DB and I am using an OLE-DB connection string then once I port over to SQL Server all I should need to change is the connection string to a SQL Server connection string. Is that correct? Anyone know where I can find some information about this process and specifically how to upload the new SQL Server DB to the remote web server? To upload an Access DB, I just FTP the DB to the site directory. Pretty easy. If I understand right, you dont do that with a SQL Server DB, but rather replicate the DB to the remote server. I would like to understand how to move the SQL Server DB to a remote web server. Im trying to learn the steps and how it is done? Thanks in advance for any help.
-D-Follow these links :
http://support.microsoft.com/default.aspx?scid=kb;en-us;247931
http://www.faqts.com/knowledge_base/view.phtml/aid/3332
If this is not what you're looking then kindly come up with more explanation.sql
Monday, March 19, 2012
Moving SQL Reporting services databases
Hi
I need to do a SQL Migration for a client and they use SQL Reporting
Services. I cannot find anything on the web on how to move the Reporting
services databases (reconfigure the front end to point to the new RPT
Services databases).
Can you please advise?
Many Thanks
--
Regards
James[MVP]
Visit MBS Blog Central
http://mbscentral.blogs.comYOu have to do a backup and restore in order to use the same Report
definitions as definied in the "old" report server. I big think is to backup
the encryption key where data is encrypted within the ReportServer database.
A good step by step guide is presented here:
http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlreportingservices.asp
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
> Hi
> I need to do a SQL Migration for a client and they use SQL Reporting
> Services. I cannot find anything on the web on how to move the Reporting
> services databases (reconfigure the front end to point to the new RPT
> Services databases).
> Can you please advise?
> Many Thanks
> --
> Regards
> James[MVP]
> Visit MBS Blog Central
> http://mbscentral.blogs.com
>|||Can you confirm i dont need to worry about the encrption keys since i am
only moving the databases and not the front end of SQL reporting services?
--
Regards
James[MVP]
Visit MBS Blog Central
http://mbscentral.blogs.com
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23QbAg7gWFHA.3676@.TK2MSFTNGP10.phx.gbl...
> YOu have to do a backup and restore in order to use the same Report
> definitions as definied in the "old" report server. I big think is to
> backup the encryption key where data is encrypted within the ReportServer
> database. A good step by step guide is presented here:
> http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlreportingservices.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
> news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> I need to do a SQL Migration for a client and they use SQL Reporting
>> Services. I cannot find anything on the web on how to move the
>> Reporting services databases (reconfigure the front end to point to the
>> new RPT Services databases).
>> Can you please advise?
>> Many Thanks
>> --
>> Regards
>> James[MVP]
>> Visit MBS Blog Central
>> http://mbscentral.blogs.com
>|||Jens,
Do we need to move the visual studio projects physically to new server?
I've copied the encrypted keys and was able to access the web page. I
haven't copied the visual studio projects yet. The old server has two
drives whereas the new one has single drive. I have to change the path
for source cs projects. Any ideas?
Thanks
Tram
Jens S=FC=DFmeyer wrote:
> YOu have to do a backup and restore in order to use the same Report
> definitions as definied in the "old" report server. I big think is to
backup
> the encryption key where data is encrypted within the ReportServer
database.
> A good step by step guide is presented here:
>
http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlr=
eportingservices.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
> news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
> > Hi
> >
> > I need to do a SQL Migration for a client and they use SQL
Reporting
> > Services. I cannot find anything on the web on how to move the
Reporting
> > services databases (reconfigure the front end to point to the new
RPT
> > Services databases).
> >
> > Can you please advise?
> >
> > Many Thanks
> >
> > --
> > Regards
> >
> > James[MVP]
> > Visit MBS Blog Central
> >
> > http://mbscentral.blogs.com
> >|||There is no need to reside the VS projects on the server. I our projects we
have the VS projects stored in the VS SourceSafe and on the DevClients.
If you really want to store the projects on the server, just copy them and
change the project / solution source to the new path.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"tram" <tram_e@.hotmail.com> schrieb im Newsbeitrag
news:1116251644.128877.57710@.g44g2000cwa.googlegroups.com...
Jens,
Do we need to move the visual studio projects physically to new server?
I've copied the encrypted keys and was able to access the web page. I
haven't copied the visual studio projects yet. The old server has two
drives whereas the new one has single drive. I have to change the path
for source cs projects. Any ideas?
Thanks
Tram
Jens Süßmeyer wrote:
> YOu have to do a backup and restore in order to use the same Report
> definitions as definied in the "old" report server. I big think is to
backup
> the encryption key where data is encrypted within the ReportServer
database.
> A good step by step guide is presented here:
>
http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlreportingservices.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
> news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
> > Hi
> >
> > I need to do a SQL Migration for a client and they use SQL
Reporting
> > Services. I cannot find anything on the web on how to move the
Reporting
> > services databases (reconfigure the front end to point to the new
RPT
> > Services databases).
> >
> > Can you please advise?
> >
> > Many Thanks
> >
> > --
> > Regards
> >
> > James[MVP]
> > Visit MBS Blog Central
> >
> > http://mbscentral.blogs.com
> >|||Thanks for the quick reply. If I don't copy the projects, if we
shutdown the old server, does it still work?|||When you deploy everything the server needs is stored in the database. The
source is not needed or used. Obviously you want to keep the source for the
reports somewhere to be able to modify easily (although you can extract the
source via the server at a later date).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"tram" <tram_e@.hotmail.com> wrote in message
news:1116268553.385098.290120@.g44g2000cwa.googlegroups.com...
> Thanks for the quick reply. If I don't copy the projects, if we
> shutdown the old server, does it still work?
>|||Hi
Thanks for your replies, I am just moving the databases, not the report
services website. I will just do a database restore and follow
http://support.microsoft.com/default.aspx?scid=842425
--
Regards
James[MVP]
Visit MBS Blog Central
http://mbscentral.blogs.com
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23XcFGzkWFHA.712@.TK2MSFTNGP14.phx.gbl...
> When you deploy everything the server needs is stored in the database. The
> source is not needed or used. Obviously you want to keep the source for
> the reports somewhere to be able to modify easily (although you can
> extract the source via the server at a later date).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "tram" <tram_e@.hotmail.com> wrote in message
> news:1116268553.385098.290120@.g44g2000cwa.googlegroups.com...
>> Thanks for the quick reply. If I don't copy the projects, if we
>> shutdown the old server, does it still work?
>
I need to do a SQL Migration for a client and they use SQL Reporting
Services. I cannot find anything on the web on how to move the Reporting
services databases (reconfigure the front end to point to the new RPT
Services databases).
Can you please advise?
Many Thanks
--
Regards
James[MVP]
Visit MBS Blog Central
http://mbscentral.blogs.comYOu have to do a backup and restore in order to use the same Report
definitions as definied in the "old" report server. I big think is to backup
the encryption key where data is encrypted within the ReportServer database.
A good step by step guide is presented here:
http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlreportingservices.asp
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
> Hi
> I need to do a SQL Migration for a client and they use SQL Reporting
> Services. I cannot find anything on the web on how to move the Reporting
> services databases (reconfigure the front end to point to the new RPT
> Services databases).
> Can you please advise?
> Many Thanks
> --
> Regards
> James[MVP]
> Visit MBS Blog Central
> http://mbscentral.blogs.com
>|||Can you confirm i dont need to worry about the encrption keys since i am
only moving the databases and not the front end of SQL reporting services?
--
Regards
James[MVP]
Visit MBS Blog Central
http://mbscentral.blogs.com
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23QbAg7gWFHA.3676@.TK2MSFTNGP10.phx.gbl...
> YOu have to do a backup and restore in order to use the same Report
> definitions as definied in the "old" report server. I big think is to
> backup the encryption key where data is encrypted within the ReportServer
> database. A good step by step guide is presented here:
> http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlreportingservices.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
> news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> I need to do a SQL Migration for a client and they use SQL Reporting
>> Services. I cannot find anything on the web on how to move the
>> Reporting services databases (reconfigure the front end to point to the
>> new RPT Services databases).
>> Can you please advise?
>> Many Thanks
>> --
>> Regards
>> James[MVP]
>> Visit MBS Blog Central
>> http://mbscentral.blogs.com
>|||Jens,
Do we need to move the visual studio projects physically to new server?
I've copied the encrypted keys and was able to access the web page. I
haven't copied the visual studio projects yet. The old server has two
drives whereas the new one has single drive. I have to change the path
for source cs projects. Any ideas?
Thanks
Tram
Jens S=FC=DFmeyer wrote:
> YOu have to do a backup and restore in order to use the same Report
> definitions as definied in the "old" report server. I big think is to
backup
> the encryption key where data is encrypted within the ReportServer
database.
> A good step by step guide is presented here:
>
http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlr=
eportingservices.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
> news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
> > Hi
> >
> > I need to do a SQL Migration for a client and they use SQL
Reporting
> > Services. I cannot find anything on the web on how to move the
Reporting
> > services databases (reconfigure the front end to point to the new
RPT
> > Services databases).
> >
> > Can you please advise?
> >
> > Many Thanks
> >
> > --
> > Regards
> >
> > James[MVP]
> > Visit MBS Blog Central
> >
> > http://mbscentral.blogs.com
> >|||There is no need to reside the VS projects on the server. I our projects we
have the VS projects stored in the VS SourceSafe and on the DevClients.
If you really want to store the projects on the server, just copy them and
change the project / solution source to the new path.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"tram" <tram_e@.hotmail.com> schrieb im Newsbeitrag
news:1116251644.128877.57710@.g44g2000cwa.googlegroups.com...
Jens,
Do we need to move the visual studio projects physically to new server?
I've copied the encrypted keys and was able to access the web page. I
haven't copied the visual studio projects yet. The old server has two
drives whereas the new one has single drive. I have to change the path
for source cs projects. Any ideas?
Thanks
Tram
Jens Süßmeyer wrote:
> YOu have to do a backup and restore in order to use the same Report
> definitions as definied in the "old" report server. I big think is to
backup
> the encryption key where data is encrypted within the ReportServer
database.
> A good step by step guide is presented here:
>
http://www.sqlservercentral.com/columnists/mpearson/recoveryplanningforsqlreportingservices.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "James[MVP]" <hushdontspamme@.Hotmail.com> schrieb im Newsbeitrag
> news:ObCdfnfWFHA.228@.TK2MSFTNGP12.phx.gbl...
> > Hi
> >
> > I need to do a SQL Migration for a client and they use SQL
Reporting
> > Services. I cannot find anything on the web on how to move the
Reporting
> > services databases (reconfigure the front end to point to the new
RPT
> > Services databases).
> >
> > Can you please advise?
> >
> > Many Thanks
> >
> > --
> > Regards
> >
> > James[MVP]
> > Visit MBS Blog Central
> >
> > http://mbscentral.blogs.com
> >|||Thanks for the quick reply. If I don't copy the projects, if we
shutdown the old server, does it still work?|||When you deploy everything the server needs is stored in the database. The
source is not needed or used. Obviously you want to keep the source for the
reports somewhere to be able to modify easily (although you can extract the
source via the server at a later date).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"tram" <tram_e@.hotmail.com> wrote in message
news:1116268553.385098.290120@.g44g2000cwa.googlegroups.com...
> Thanks for the quick reply. If I don't copy the projects, if we
> shutdown the old server, does it still work?
>|||Hi
Thanks for your replies, I am just moving the databases, not the report
services website. I will just do a database restore and follow
http://support.microsoft.com/default.aspx?scid=842425
--
Regards
James[MVP]
Visit MBS Blog Central
http://mbscentral.blogs.com
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23XcFGzkWFHA.712@.TK2MSFTNGP14.phx.gbl...
> When you deploy everything the server needs is stored in the database. The
> source is not needed or used. Obviously you want to keep the source for
> the reports somewhere to be able to modify easily (although you can
> extract the source via the server at a later date).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "tram" <tram_e@.hotmail.com> wrote in message
> news:1116268553.385098.290120@.g44g2000cwa.googlegroups.com...
>> Thanks for the quick reply. If I don't copy the projects, if we
>> shutdown the old server, does it still work?
>
Moving SQL Express data to SQL Server 2005 Dev?
Hi gang,
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegroups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegroups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David
Moving SQL Express data to SQL Server 2005 Dev?
Hi gang,
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall
"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegr oups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall
"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegr oups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David
Moving SQL Express data to SQL Server 2005 Dev?
Hi gang,
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegroups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegroups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David
Monday, March 12, 2012
Moving SQL 7.0 to New Hardware
Hi,
I've read some articles on the web but none seem to fit my
situation.
We have an application upgrade and at the same time need
to move our SQL 7.0 to new hardware.
The new server will have Windows 2000 and SQL 7.0
installed and then we will upgrade to SQL 2000 at some
point during our application upgrade.
What is the best method of moving our SQL 7.0 databases to
our new hardware?
Thanks in advance.You can either use BACKUP and RESTORE, or sp_detach_db and sp_attach_db.
Make sure you sync users after transferring databases.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Larry" <sloberman@.email.chop.edu> wrote in message
news:582901c40081$dd8e7ae0$a301280a@.phx.gbl...
> Hi,
> I've read some articles on the web but none seem to fit my
> situation.
> We have an application upgrade and at the same time need
> to move our SQL 7.0 to new hardware.
> The new server will have Windows 2000 and SQL 7.0
> installed and then we will upgrade to SQL 2000 at some
> point during our application upgrade.
> What is the best method of moving our SQL 7.0 databases to
> our new hardware?
> Thanks in advance.
I've read some articles on the web but none seem to fit my
situation.
We have an application upgrade and at the same time need
to move our SQL 7.0 to new hardware.
The new server will have Windows 2000 and SQL 7.0
installed and then we will upgrade to SQL 2000 at some
point during our application upgrade.
What is the best method of moving our SQL 7.0 databases to
our new hardware?
Thanks in advance.You can either use BACKUP and RESTORE, or sp_detach_db and sp_attach_db.
Make sure you sync users after transferring databases.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Larry" <sloberman@.email.chop.edu> wrote in message
news:582901c40081$dd8e7ae0$a301280a@.phx.gbl...
> Hi,
> I've read some articles on the web but none seem to fit my
> situation.
> We have an application upgrade and at the same time need
> to move our SQL 7.0 to new hardware.
> The new server will have Windows 2000 and SQL 7.0
> installed and then we will upgrade to SQL 2000 at some
> point during our application upgrade.
> What is the best method of moving our SQL 7.0 databases to
> our new hardware?
> Thanks in advance.
Moving SQL 7.0 to New Hardware
Hi,
I've read some articles on the web but none seem to fit my
situation.
We have an application upgrade and at the same time need
to move our SQL 7.0 to new hardware.
The new server will have Windows 2000 and SQL 7.0
installed and then we will upgrade to SQL 2000 at some
point during our application upgrade.
What is the best method of moving our SQL 7.0 databases to
our new hardware?
Thanks in advance.You can either use BACKUP and RESTORE, or sp_detach_db and sp_attach_db.
Make sure you sync users after transferring databases.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"Larry" <sloberman@.email.chop.edu> wrote in message
news:582901c40081$dd8e7ae0$a301280a@.phx.gbl...
> Hi,
> I've read some articles on the web but none seem to fit my
> situation.
> We have an application upgrade and at the same time need
> to move our SQL 7.0 to new hardware.
> The new server will have Windows 2000 and SQL 7.0
> installed and then we will upgrade to SQL 2000 at some
> point during our application upgrade.
> What is the best method of moving our SQL 7.0 databases to
> our new hardware?
> Thanks in advance.
I've read some articles on the web but none seem to fit my
situation.
We have an application upgrade and at the same time need
to move our SQL 7.0 to new hardware.
The new server will have Windows 2000 and SQL 7.0
installed and then we will upgrade to SQL 2000 at some
point during our application upgrade.
What is the best method of moving our SQL 7.0 databases to
our new hardware?
Thanks in advance.You can either use BACKUP and RESTORE, or sp_detach_db and sp_attach_db.
Make sure you sync users after transferring databases.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"Larry" <sloberman@.email.chop.edu> wrote in message
news:582901c40081$dd8e7ae0$a301280a@.phx.gbl...
> Hi,
> I've read some articles on the web but none seem to fit my
> situation.
> We have an application upgrade and at the same time need
> to move our SQL 7.0 to new hardware.
> The new server will have Windows 2000 and SQL 7.0
> installed and then we will upgrade to SQL 2000 at some
> point during our application upgrade.
> What is the best method of moving our SQL 7.0 databases to
> our new hardware?
> Thanks in advance.
Friday, March 9, 2012
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
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
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
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
Moving Reporting Services Virtual Directories
Hi
I have followed the aritcle
http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk to
a tee, but when i run the new web site i get a page not found for
http://localhost/reports/home.aspx
If i run it on the default web server everything is fine.
I tried testing it by placing an html file in the report manager folder eg
test.html and http://localhost/reports/test.html worked fine.
Has anyone successfully completed this operation? I can access
http://localhost/reportserver/ ok
I'm guessing it's a permissions/execution problem.
Any ideas?
Cheers
JonnyIt's okay
I've sorted it. I hadn't got the ASP.NET server extension enabled in IIS.
Not sure how it worked at all?
Jonny
"Jonny" <jonny@.nospam.jonnywilk.co.uk> wrote in message
news:d8crpk$6d0$1$8300dec7@.news.demon.co.uk...
> Hi
> I have followed the aritcle
> http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk
> to a tee, but when i run the new web site i get a page not found for
> http://localhost/reports/home.aspx
> If i run it on the default web server everything is fine.
> I tried testing it by placing an html file in the report manager folder eg
> test.html and http://localhost/reports/test.html worked fine.
> Has anyone successfully completed this operation? I can access
> http://localhost/reportserver/ ok
> I'm guessing it's a permissions/execution problem.
> Any ideas?
> Cheers
> Jonny
>
I have followed the aritcle
http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk to
a tee, but when i run the new web site i get a page not found for
http://localhost/reports/home.aspx
If i run it on the default web server everything is fine.
I tried testing it by placing an html file in the report manager folder eg
test.html and http://localhost/reports/test.html worked fine.
Has anyone successfully completed this operation? I can access
http://localhost/reportserver/ ok
I'm guessing it's a permissions/execution problem.
Any ideas?
Cheers
JonnyIt's okay
I've sorted it. I hadn't got the ASP.NET server extension enabled in IIS.
Not sure how it worked at all?
Jonny
"Jonny" <jonny@.nospam.jonnywilk.co.uk> wrote in message
news:d8crpk$6d0$1$8300dec7@.news.demon.co.uk...
> Hi
> I have followed the aritcle
> http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk
> to a tee, but when i run the new web site i get a page not found for
> http://localhost/reports/home.aspx
> If i run it on the default web server everything is fine.
> I tried testing it by placing an html file in the report manager folder eg
> test.html and http://localhost/reports/test.html worked fine.
> Has anyone successfully completed this operation? I can access
> http://localhost/reportserver/ ok
> I'm guessing it's a permissions/execution problem.
> Any ideas?
> Cheers
> Jonny
>
Saturday, February 25, 2012
moving ms SQL databases
I've created a web application with Visual Studio 2003. Uploading my application to the server is easy enough. I use the Copy Project utility from the Project selection on the menu bar.
I'm using a remote server-- and hosting account that supports ASP.NET and ms SQL. But now I want to copy my ms SQL database and can't find any way to copy my DB to the server.
What do the best way to to this?
Paul
Tucson, AZ
Ask your hoster. Some options are hoster specific.
The Enterprise Manager has a tool to copy databases between two servers. This is one way - but do you have the rights for this on the server?
Then there is attach/detach. Same issue.
As you are not interested in theoretical discussions what could be possible (if your hoster would not disallow it), ask your hoster.
Subscribe to:
Posts (Atom)