Showing posts with label upgrade. Show all posts

Friday, March 23, 2012

RS2008 with SQL 2005 (different question)

Slightly different than the post before it.
If we have SQL 2005 and we don't want to upgrade to 2008 what options
do we have with regards to using RS2008? Can it be purchased
separately or something? Our reporting server is running 2005 great
but we want to benefit from the advances in RS2008 without having to
upgrade and pay a ton of money for it and take up a lot of time and
effort to upgrade everything, including the DB engine.
Thanksbased on the webcasts i have seen, I don't think RS 2008 will be available
separately.
"SQL Guy" <aymantg@.gmail.com> wrote in message
news:35ac9e28-4e09-4098-930f-9de83298236a@.w28g2000hsf.googlegroups.com...
> Slightly different than the post before it.
> If we have SQL 2005 and we don't want to upgrade to 2008 what options
> do we have with regards to using RS2008? Can it be purchased
> separately or something? Our reporting server is running 2005 great
> but we want to benefit from the advances in RS2008 without having to
> upgrade and pay a ton of money for it and take up a lot of time and
> effort to upgrade everything, including the DB engine.
> Thanks|||I don't have the definitive word on this but my guess (and I am counting on
it) will be that this will be the same as RS2005 and SQL 2000. With that
combination you could run RS 2005 and have it use SQL 2000 database for its
metadata/object caching. This was/is fully supported and I ran that way for
6 months. My guess is that RS 2008 will be similar, that it will allow SQL
2005 to be used for its metadata/object caching.
Now, as far as licensing. I am assuming no change in licensing. Today you
have to have a SQL 2005 license for whatever server is running RS. So if it
is a web farm and you have 5 web servers all using the same DB, then all 5
web servers have to have a SQL 2005 server license. If you run RS 2005 on
the same server as SQL 2000, you have to have a SQL 2005 license. You just
have the option not to upgrade the database but you still have to have a
license.
HTH,
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"SQL Guy" <aymantg@.gmail.com> wrote in message
news:35ac9e28-4e09-4098-930f-9de83298236a@.w28g2000hsf.googlegroups.com...
> Slightly different than the post before it.
> If we have SQL 2005 and we don't want to upgrade to 2008 what options
> do we have with regards to using RS2008? Can it be purchased
> separately or something? Our reporting server is running 2005 great
> but we want to benefit from the advances in RS2008 without having to
> upgrade and pay a ton of money for it and take up a lot of time and
> effort to upgrade everything, including the DB engine.
> Thanks

Monday, March 12, 2012

RS upgrade Eval to Stnd?

A couple months ago we started a report server MS SQL Reporting Services.
The MS SQL is of course licenced but the Microsoft dealer by mistake sent us
an evaluation version of RS. We've used it for a couple of months and
yestarday it stopped working - its evaluation period passed. As it is
already a production system we are worried how to install the Stadard
Edition RS. How can we preserve all our reports and all their permissions?
Would a RS database backup and after RS reinstallation DB restore work?
Thanks for any help.
MarcinToo bad nobady answered :( Already came up with a solution.
U¿ytkownik "pexiak" <peksa@.interia.pl> napisa³ w wiadomo¶ci
news:uwelCobOFHA.3144@.tk2msftngp13.phx.gbl...
> A couple months ago we started a report server MS SQL Reporting Services.
> The MS SQL is of course licenced but the Microsoft dealer by mistake sent
us
> an evaluation version of RS. We've used it for a couple of months and
> yestarday it stopped working - its evaluation period passed. As it is
> already a production system we are worried how to install the Stadard
> Edition RS. How can we preserve all our reports and all their permissions?
> Would a RS database backup and after RS reinstallation DB restore work?
> Thanks for any help.
> Marcin
>|||Hi,
I'd like to know what solution you came up with. I want to be 100% sure
before installing standard edition on top of evaluation edition. I forgot to
backup the keys, so will this have any impact ?
Karthik
"pexiak" wrote:
> Too bad nobady answered :( Already came up with a solution.
> UÂ¿ytkownik "pexiak" <peksa@.interia.pl> napisaÂ³ w wiadomoÂ¶ci
> news:uwelCobOFHA.3144@.tk2msftngp13.phx.gbl...
> > A couple months ago we started a report server MS SQL Reporting Services.
> > The MS SQL is of course licenced but the Microsoft dealer by mistake sent
> us
> > an evaluation version of RS. We've used it for a couple of months and
> > yestarday it stopped working - its evaluation period passed. As it is
> > already a production system we are worried how to install the Stadard
> > Edition RS. How can we preserve all our reports and all their permissions?
> > Would a RS database backup and after RS reinstallation DB restore work?
> > Thanks for any help.
> > Marcin
> >
> >
>
>|||You should be able to upgrade without any problem. Just in case, I would
back up your key as well as your ReportServer database.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
"Karthik Guruswamy" <Karthik Guruswamy@.discussions.microsoft.com> wrote in
message news:667C5DB7-FBC8-43A6-8900-FDD0C9A6992F@.microsoft.com...
> Hi,
> I'd like to know what solution you came up with. I want to be 100% sure
> before installing standard edition on top of evaluation edition. I forgot
> to
> backup the keys, so will this have any impact ?
> Karthik
> "pexiak" wrote:
>> Too bad nobady answered :( Already came up with a solution.
>> U¿ytkownik "pexiak" <peksa@.interia.pl> napisa³ w wiadomo¶ci
>> news:uwelCobOFHA.3144@.tk2msftngp13.phx.gbl...
>> > A couple months ago we started a report server MS SQL Reporting
>> > Services.
>> > The MS SQL is of course licenced but the Microsoft dealer by mistake
>> > sent
>> us
>> > an evaluation version of RS. We've used it for a couple of months and
>> > yestarday it stopped working - its evaluation period passed. As it is
>> > already a production system we are worried how to install the Stadard
>> > Edition RS. How can we preserve all our reports and all their
>> > permissions?
>> > Would a RS database backup and after RS reinstallation DB restore work?
>> > Thanks for any help.
>> > Marcin
>> >
>> >
>>

RS upgrade

RS SP2 Upgrade

Hi,
We use two IIS machine hosting each an instance of Report Server. The RS
database is located on a SQL2000 SP4 cluster where no component of RS is
installed except the RS and RSTempDB databases.
We upgraded each IIS machine and the setup completed without any errors or
warning. In the release notes for SP2, it is told that the database server
needs also to be upgraded. But there are no RS components installed on the
SQL cluster and by the way nothing to upgrade.
Is this a bug on the release notes ? Is the database upgraded by the update
process on a report server machine ?
Or do I need to do anything else to upgrade the database ? How can I check
if the database was upgraded or not ?
Thanks in advance.
SBIt sounds like you have a web farm. The process of upgrading RS will upgrade
the database.
Note that you will want to upgrade your development (report designer).
Especially if you skipped SP1.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BENHAMOU Stéphane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> Hi,
> We use two IIS machine hosting each an instance of Report Server. The RS
> database is located on a SQL2000 SP4 cluster where no component of RS is
> installed except the RS and RSTempDB databases.
> We upgraded each IIS machine and the setup completed without any errors or
> warning. In the release notes for SP2, it is told that the database server
> needs also to be upgraded. But there are no RS components installed on the
> SQL cluster and by the way nothing to upgrade.
> Is this a bug on the release notes ? Is the database upgraded by the
> update
> process on a report server machine ?
> Or do I need to do anything else to upgrade the database ? How can I check
> if the database was upgraded or not ?
> Thanks in advance.
> SB|||Thanks for your answer.
Is there a way to check the database structure upgrade ?
I run a "select * from information_schema.columns" on an SP1 and then on the
SP2 database used by my web farm, and the number of columns is exactly the
same (206) for both versions.
Do you know what are the database structure changes ?
"Bruce L-C [MVP]" a Ã©crit :
> It sounds like you have a web farm. The process of upgrading RS will upgrade
> the database.
> Note that you will want to upgrade your development (report designer).
> Especially if you skipped SP1.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "BENHAMOU StÃ©phane" <BENHAMOUStphane@.discussions.microsoft.com> wrote in
> message news:E26F48E0-155E-41B6-8BCF-69D4605F57BE@.microsoft.com...
> > Hi,
> >
> > We use two IIS machine hosting each an instance of Report Server. The RS
> > database is located on a SQL2000 SP4 cluster where no component of RS is
> > installed except the RS and RSTempDB databases.
> >
> > We upgraded each IIS machine and the setup completed without any errors or
> > warning. In the release notes for SP2, it is told that the database server
> > needs also to be upgraded. But there are no RS components installed on the
> > SQL cluster and by the way nothing to upgrade.
> >
> > Is this a bug on the release notes ? Is the database upgraded by the
> > update
> > process on a report server machine ?
> >
> > Or do I need to do anything else to upgrade the database ? How can I check
> > if the database was upgraded or not ?
> >
> > Thanks in advance.
> > SB
>
>

Friday, March 9, 2012

RS Service Pack 1 question

Does installing RS SP1 upgrade the version of sql server? We are
running SP3A as a standard. I want to verify that if I install RS sp1
sql server will not be upgraded to 8.00.859 (this version contains a
hotfix). We noticed our test sever contains the hotfix and are
trying to figure out how it got there. RS SP1 was installed about a
week back.Are you sure that someone didn't install it? If your test server is running
Windows 2003 the install instruction say to install that hotfix.
I don't think SP1 does anything to the SQL Server version but I am not at
work today to verify that. I know it does upgrade the database used by RS
but that is just normal data objects, not applying a hotfix.
Bruce L-C
"Dave" <davidbr93@.hotmail.com> wrote in message
news:4e5222b5.0408130700.52c993f2@.posting.google.com...
> Does installing RS SP1 upgrade the version of sql server? We are
> running SP3A as a standard. I want to verify that if I install RS sp1
> sql server will not be upgraded to 8.00.859 (this version contains a
> hotfix). We noticed our test sever contains the hotfix and are
> trying to figure out how it got there. RS SP1 was installed about a
> week back.|||SP1 does NOT upgrade the SQL server. It does upgrade the database that RS
uses.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce Loehle-Conger" <bruce_lc@.hotmail.com> wrote in message
news:OVE6tjUgEHA.592@.TK2MSFTNGP11.phx.gbl...
> Are you sure that someone didn't install it? If your test server is
running
> Windows 2003 the install instruction say to install that hotfix.
> I don't think SP1 does anything to the SQL Server version but I am not at
> work today to verify that. I know it does upgrade the database used by RS
> but that is just normal data objects, not applying a hotfix.
> Bruce L-C
>
> "Dave" <davidbr93@.hotmail.com> wrote in message
> news:4e5222b5.0408130700.52c993f2@.posting.google.com...
> > Does installing RS SP1 upgrade the version of sql server? We are
> > running SP3A as a standard. I want to verify that if I install RS sp1
> > sql server will not be upgraded to 8.00.859 (this version contains a
> > hotfix). We noticed our test sever contains the hotfix and are
> > trying to figure out how it got there. RS SP1 was installed about a
> > week back.
>

RS Restore Version Conflict

We are attempting to dry run a SQL 2000 to SQL 2005 upgrade. We build a
server in a test lab with reporting services 2000, SP1 successfully. Backed
up our production (reporting services 2000 SP1) ReportServer databases and
restored to the test lab server. Now we get the following error in report
manager:
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.6.54'. The expected
version is 'C.0.6.51'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase) Get Online
Help
How do I troubleshoot this? I'm not finding anything in online help. Thank
you,Hi Brent,
Welcome to use MSDN Managed Newsgroup!
The error message indicates the database you used to attach is backuped
from a Reporting Services SP2 but you are attaching it to a Report Services
SP1.
You should select the correct version database for Reporting Services.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I am having a similar problem moving a RS db from 32 bit sql to 64 bit sql.
Could you please extrapolate on "You should select the correct version
database for Reporting Services."
--
MCSD
"Michael Cheng [MSFT]" wrote:
> Hi Brent,
> Welcome to use MSDN Managed Newsgroup!
> The error message indicates the database you used to attach is backuped
> from a Reporting Services SP2 but you are attaching it to a Report Services
> SP1.
> You should select the correct version database for Reporting Services.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi,
Thanks for your question but it is not exactly the same as original one.
If you want to move the Report Server database, it would be recommended to
use 32bit SQL Server's database to restore the 32bit SQL Server's database.
Everything should be match.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||We are migrating from a 32 bit SQL server to a 64 bit. I cannot find any
papers on how to do this migration, therefore I detached the DB from 32bit
and reattached to 64 bit server. After reattaching is when I get the error.
Reattaching to 32 is pointless.
--
MCSD
"Michael Cheng [MSFT]" wrote:
> Hi,
> Thanks for your question but it is not exactly the same as original one.
> If you want to move the Report Server database, it would be recommended to
> use 32bit SQL Server's database to restore the 32bit SQL Server's database.
> Everything should be match.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||Just a guess, but try the SSIS wizards on the 64bit server to move the
databases from a 32bit server.
Cheers
Chris
Aco wrote:
> We are migrating from a 32 bit SQL server to a 64 bit. I cannot find
> any papers on how to do this migration, therefore I detached the DB
> from 32bit and reattached to 64 bit server. After reattaching is when
> I get the error. Reattaching to 32 is pointless.

RS Repository database version is dorked up, named instance has higher number than base in

I installed a named instance but can't upgrade the database. The found
version is higher than the expected version. I read some blogs and it's
probably related to sp1. The config tool for the named instance gives me
all green but when I try to access the reports I get the following error.
The version of the report server database is either in a format
that is not valid, or it cannot be read. The found version is 'C.0.8.43'.
The expected version is 'C.0.8.40'. To continue, update the version of the
report server database and verify access rights.
(rsInvalidReportServerDatabase) Get Online Help
Steve MunLeeuwMy bad, not everything is green, Initialization is red and gives me the
following error when clicking on it. What did I do to get in this
situation?
--
Reporting Services Configuration Manager
--
There was an error while switching panels. The most likely cause is an error
retrieving WMI properties. The exception details are:
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.43'. The expected
version is 'C.0.8.40'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)
--
OK
--
Steve MunLeeuw
"Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
news:OmOq%23rs9GHA.1012@.TK2MSFTNGP05.phx.gbl...
>I installed a named instance but can't upgrade the database. The found
>version is higher than the expected version. I read some blogs and it's
>probably related to sp1. The config tool for the named instance gives me
>all green but when I try to access the reports I get the following error.
> The version of the report server database is either in a format
> that is not valid, or it cannot be read. The found version is 'C.0.8.43'.
> The expected version is 'C.0.8.40'. To continue, update the version of the
> report server database and verify access rights.
> (rsInvalidReportServerDatabase) Get Online Help
> Steve MunLeeuw
>
>|||Excerpt from http://blogs.msdn.com/lukaszp/
When you upgrade SQL Server 2005 to SP1 and you are running Reporting
Services, you may start to get the following error message:
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.40'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)
First the solution:
Got to Start à All Programs à Microsoft SQL Server 2005 à Configuration
Tools à Reporting Services Configuration
Connection to your report server on the connection dialog. Navigate to the
Database Setup tab (left navigation pane, 6th from the top).
Click the Upgrade button on the Database Connection page.
Provide credentials that are members of the sysadmin SQL server group.
After you finish this, you should be good to go.
Now let's talk about what setup is doing under the covers and how to avoid
getting in this situation:
In SP1 we had to change the report server database format. This meant that
during service pack installation we have to connect to the report server
database and upgrade the report server database.
When you run SP1 setup, by default we use the credentials of the user
running setup to connect to upgrade the report server database. Sometimes
this does not work:
1) when the user running setup does not have sysadmin group membership
in SQL Server
2) when the report server database is hosted on a remote computer, if
you're running as a local user, your user cannot access the remote computer
to upgrade the report server database
3) when the report server database is inaccessible - the sql server is
stopped or you cannot connect to the database for whatever reason.
You can change the credentials we use in one of two ways:
A) In the UI you can select the report server database and click to
configure specific credentials
B) On the command line you can specify the /rsupgradedatabaseaccount and
/rsupgradepassword switches
There is one case in which you cannot supply credentials. If you run SP1
upgrade using Microsoft Update, the setup runs under a local account. This
account may not have permissions as described above. As such, it is more
likely to cause you to encounter the error above.
Michael Abair
Michael Abair
Programmer / Analyst
Chicos FAS Inc.
"Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
news:%23Bu3Dws9GHA.4408@.TK2MSFTNGP02.phx.gbl...
> My bad, not everything is green, Initialization is red and gives me the
> following error when clicking on it. What did I do to get in this
> situation?
> --
> Reporting Services Configuration Manager
> --
> There was an error while switching panels. The most likely cause is an
> error retrieving WMI properties. The exception details are:
>
> The version of the report server database is either in a format that is
> not valid, or it cannot be read. The found version is 'C.0.8.43'. The
> expected version is 'C.0.8.40'. To continue, update the version of the
> report server database and verify access rights.
> (rsInvalidReportServerDatabase)
> --
> OK
> --
> Steve MunLeeuw
> "Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
> news:OmOq%23rs9GHA.1012@.TK2MSFTNGP05.phx.gbl...
>>I installed a named instance but can't upgrade the database. The found
>>version is higher than the expected version. I read some blogs and it's
>>probably related to sp1. The config tool for the named instance gives me
>>all green but when I try to access the reports I get the following error.
>> The version of the report server database is either in a
>> format that is not valid, or it cannot be read. The found version is
>> 'C.0.8.43'. The expected version is 'C.0.8.40'. To continue, update the
>> version of the report server database and verify access rights.
>> (rsInvalidReportServerDatabase) Get Online Help
>> Steve MunLeeuw
>>
>|||Thanks Michael,
I didn't apply SQL SP1 agian after installing the named instance. The
scripts to create the new database were probably for version 'C.0.8.43', but
the newly installed components were for 'C.0.8.40' . The SPI updated the
components to 'C.0.8.43' and the error went away.
Steve MunLeeuw
"Michael Abair" <michael.abair@.chicos.com> wrote in message
news:uiKy9gt9GHA.3348@.TK2MSFTNGP03.phx.gbl...
> Excerpt from http://blogs.msdn.com/lukaszp/
>
> When you upgrade SQL Server 2005 to SP1 and you are running Reporting
> Services, you may start to get the following error message:
>
> The version of the report server database is either in a format that is
> not valid, or it cannot be read. The found version is 'C.0.8.40'. The
> expected version is 'C.0.8.43'. To continue, update the version of the
> report server database and verify access rights.
> (rsInvalidReportServerDatabase)
>
> First the solution:
> Got to Start à All Programs à Microsoft SQL Server 2005 à Configuration
> Tools à Reporting Services Configuration
>
> Connection to your report server on the connection dialog. Navigate to
> the Database Setup tab (left navigation pane, 6th from the top).
>
> Click the Upgrade button on the Database Connection page.
> Provide credentials that are members of the sysadmin SQL server group.
>
> After you finish this, you should be good to go.
>
> Now let's talk about what setup is doing under the covers and how to avoid
> getting in this situation:
>
> In SP1 we had to change the report server database format. This meant
> that during service pack installation we have to connect to the report
> server database and upgrade the report server database.
>
> When you run SP1 setup, by default we use the credentials of the user
> running setup to connect to upgrade the report server database. Sometimes
> this does not work:
> 1) when the user running setup does not have sysadmin group
> membership in SQL Server
> 2) when the report server database is hosted on a remote computer, if
> you're running as a local user, your user cannot access the remote
> computer to upgrade the report server database
> 3) when the report server database is inaccessible - the sql server
> is stopped or you cannot connect to the database for whatever reason.
>
> You can change the credentials we use in one of two ways:
> A) In the UI you can select the report server database and click to
> configure specific credentials
> B) On the command line you can specify the /rsupgradedatabaseaccount
> and /rsupgradepassword switches
>
> There is one case in which you cannot supply credentials. If you run SP1
> upgrade using Microsoft Update, the setup runs under a local account. This
> account may not have permissions as described above. As such, it is more
> likely to cause you to encounter the error above.
>
>
> --
> Michael Abair
> Michael Abair
> Programmer / Analyst
> Chicos FAS Inc.
> "Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
> news:%23Bu3Dws9GHA.4408@.TK2MSFTNGP02.phx.gbl...
>> My bad, not everything is green, Initialization is red and gives me the
>> following error when clicking on it. What did I do to get in this
>> situation?
>> --
>> Reporting Services Configuration Manager
>> --
>> There was an error while switching panels. The most likely cause is an
>> error retrieving WMI properties. The exception details are:
>>
>> The version of the report server database is either in a format that is
>> not valid, or it cannot be read. The found version is 'C.0.8.43'. The
>> expected version is 'C.0.8.40'. To continue, update the version of the
>> report server database and verify access rights.
>> (rsInvalidReportServerDatabase)
>> --
>> OK
>> --
>> Steve MunLeeuw
>> "Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
>> news:OmOq%23rs9GHA.1012@.TK2MSFTNGP05.phx.gbl...
>>I installed a named instance but can't upgrade the database. The found
>>version is higher than the expected version. I read some blogs and it's
>>probably related to sp1. The config tool for the named instance gives me
>>all green but when I try to access the reports I get the following error.
>> The version of the report server database is either in a
>> format that is not valid, or it cannot be read. The found version is
>> 'C.0.8.43'. The expected version is 'C.0.8.40'. To continue, update the
>> version of the report server database and verify access rights.
>> (rsInvalidReportServerDatabase) Get Online Help
>> Steve MunLeeuw
>>
>>
>|||SQL Server 2005 SP1 Reporting Services database expected version is 'C.0.8.43' problem
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.8.40'. The expected version is 'C.0.8.43'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)
From http://www.google.co.in/search?hl=en&q=The+version+of+the+report+server+database+is+either+in+a+format+that+is+not+valid,+or+it+cannot+be+read.+The+found+version+is+'C.0.8.40'.+The+expected+version+is+'C.0.8.43'.+&btnG=Google+Search&meta
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||Open the SRS config tool and go to the Database Setup section. Then connect
to the database in question.
After you connect click the "Upgrade" button and follow the instructions.
--
SQL Server Developer Support Engineer
"Senthil" wrote:
> SQL Server 2005 SP1 Reporting Services database expected version is 'C.0.8.43' problem
> The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.8.40'. The expected version is 'C.0.8.43'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)
>
> From http://www.google.co.in/search?hl=en&q=The+version+of+the+report+server+database+is+either+in+a+format+that+is+not+valid,+or+it+cannot+be+read.+The+found+version+is+'C.0.8.40'.+The+expected+version+is+'C.0.8.43'.+&btnG=Google+Search&meta=
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>

RS problems after upgrade from SQLExpress to Standard

Hello

I've uninstalled SQLExpress(with adv. features, RS worked fine) and then installed Standard edition.

After reinstallation and deploying reports I failed in viewing report through web browser.

Here are errors:

- when I try to view report

Reporting Services Error

An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help Error executing child request for /ReportServer/Pages/ReportViewer.aspx. Exception of type 'System.Web.HttpUnhandledException' was thrown. Value does not fall within the expected range.

- when I try to navigate to Get Online Help Error executing child request for /ReportServer/Pages/ReportViewer.aspx. Exception of type 'System.Web.HttpUnhandledException' was thrown. Value does not fall within the expected range.

- when I try to navigate to http://localhost/reports

The website cannot display the page

Thank you for any help!

Here is log:

aspnet_wp!library!1!05/09/2007-17:05:01:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. > System.InvalidOperationException: Computer name could not be obtained.
at System.Environment.get_MachineName()
at Microsoft.ReportingServices.Diagnostics.RunningJobContext..ctor(String jobId, String requestPath, JobActionEnum action, JobType type, RunningJobList parentList, UserContext userContext, HttpContext optionalWebCtx)
at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase..ctor(String jobId, String requestPath, JobActionEnum action, JobType jobType, UserContext userContext)

.....

aspnet_wp!library!1!05/09/2007-17:05:01:: e ERROR: Error rending control: System.ArgumentException: Value does not fall within the expected range.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Web.Configuration.MachineKeySection.GetHMACSHA1Hash(Byte[] buf, Byte[] modifier, Int32 start, Int32 length)
at System.Web.Configuration.MachineKeySection.HashData(Byte[] buf, Byte[] modifier, Int32 start, Int32 length)
at System.Web.Configuration.MachineKeySection.GetEncodedData(Byte[] buf, Byte[] modifier, Int32 start, Int32& length)
at System.Web.UI.ObjectStateFormatter.Serialize(Object stateGraph)
at System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Serialize(Object state)
at System.Web.UI.Util.SerializeWithAssert(IStateFormatter formatter, Object stateGraph)
at System.Web.UI.HiddenFieldPageStatePersister.Save()
at System.Web.UI.Page.SavePageStateToPersistenceMedium(Object state)
at System.Web.UI.Page.SaveAllState()

.....

Wednesday, March 7, 2012

rs Enterprise Edition

I wanted to upgrade to rs Enterprise edition so i could take advantage of
data drive subscriptions and found that the price tag is $24,000. I was
surprised at the jump from $0 to $24K for such a small difference in
features, so I am assuming that I am missing something. Can anyone tell me
what would account for the sharp difference in price?Hmmm, yes. It was never 0 in the first place. You have to pay a license for
SQL Server on any server that RS is installed on. So if you have a web farm
you have to have a license for each server, regardless of whether a SQL
Server database is installed on the machine (think of it like buying an
office license, I buy an office license doesn't mean I can put Word on one
machine, Excel on another, Powerpoint on a 3rd). Anyway, if you have SQL
Server standard already purchased and you install RS on the same server
(important point) then it is free. Same thing is true if you already had
Enterprise and installed RS on the same server.
Based on the amount you mention I assume you are doing a per processor
license, not a per user license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"denny" <denny@.microsoft.com> wrote in message
news:uPPOU85SFHA.2916@.TK2MSFTNGP15.phx.gbl...
>I wanted to upgrade to rs Enterprise edition so i could take advantage of
>data drive subscriptions and found that the price tag is $24,000. I was
>surprised at the jump from $0 to $24K for such a small difference in
>features, so I am assuming that I am missing something. Can anyone tell
>me what would account for the sharp difference in price?
>|||We were in the same situation and thought that SQL Enterprise Edition was
required to for RS Enterprise Edition, but this is not true (just a bit
confusing). We installed RS Enterprise on our SQL Standard Edition server
just fine at no additional cost.
Neil
"Bruce L-C [MVP]" wrote:
> Hmmm, yes. It was never 0 in the first place. You have to pay a license for
> SQL Server on any server that RS is installed on. So if you have a web farm
> you have to have a license for each server, regardless of whether a SQL
> Server database is installed on the machine (think of it like buying an
> office license, I buy an office license doesn't mean I can put Word on one
> machine, Excel on another, Powerpoint on a 3rd). Anyway, if you have SQL
> Server standard already purchased and you install RS on the same server
> (important point) then it is free. Same thing is true if you already had
> Enterprise and installed RS on the same server.
> Based on the amount you mention I assume you are doing a per processor
> license, not a per user license.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "denny" <denny@.microsoft.com> wrote in message
> news:uPPOU85SFHA.2916@.TK2MSFTNGP15.phx.gbl...
> >I wanted to upgrade to rs Enterprise edition so i could take advantage of
> >data drive subscriptions and found that the price tag is $24,000. I was
> >surprised at the jump from $0 to $24K for such a small difference in
> >features, so I am assuming that I am missing something. Can anyone tell
> >me what would account for the sharp difference in price?
> >
>
>|||From a licensing perspective it very much is true. Also, whether it requires
for install or not is besides the point, an Enterprise SQL Server license is
required for RS Enterprise. They are one and the same as far as licensing is
concerned. RS is not a separate product it is part of SQL Server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Neil Gould" <NeilGould@.discussions.microsoft.com> wrote in message
news:456D0FBF-4FBA-412B-B2F6-39306036EE0E@.microsoft.com...
> We were in the same situation and thought that SQL Enterprise Edition was
> required to for RS Enterprise Edition, but this is not true (just a bit
> confusing). We installed RS Enterprise on our SQL Standard Edition server
> just fine at no additional cost.
> Neil
> "Bruce L-C [MVP]" wrote:
> > Hmmm, yes. It was never 0 in the first place. You have to pay a license
for
> > SQL Server on any server that RS is installed on. So if you have a web
farm
> > you have to have a license for each server, regardless of whether a SQL
> > Server database is installed on the machine (think of it like buying an
> > office license, I buy an office license doesn't mean I can put Word on
one
> > machine, Excel on another, Powerpoint on a 3rd). Anyway, if you have SQL
> > Server standard already purchased and you install RS on the same server
> > (important point) then it is free. Same thing is true if you already had
> > Enterprise and installed RS on the same server.
> >
> > Based on the amount you mention I assume you are doing a per processor
> > license, not a per user license.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "denny" <denny@.microsoft.com> wrote in message
> > news:uPPOU85SFHA.2916@.TK2MSFTNGP15.phx.gbl...
> > >I wanted to upgrade to rs Enterprise edition so i could take advantage
of
> > >data drive subscriptions and found that the price tag is $24,000. I
was
> > >surprised at the jump from $0 to $24K for such a small difference in
> > >features, so I am assuming that I am missing something. Can anyone
tell
> > >me what would account for the sharp difference in price?
> > >
> >
> >
> >

Saturday, February 25, 2012

RS deactivated after upgrade from Win 2000 to W2k3

Hi,
After I have upgraded my server, RS stop working .
a.. The report server cannot decrypt the symmetric key used to access
sensitive or encrypted data in a report server database. You must either
restore a backup key or delete all encrypted content and then restart the
service. Check the documentation for more information.
(rsReportServerDisabled) Get Online Help
a.. Bad Data.
I have the Key (exported using the rskeymgmt utility)
But I can't reapply the key:
an "Unable to connect to the database" error appear when I try to reapply
the key.
I have lost a document on the Microsoft web site which explain the entire
process to reactivate RS.
Anyone has the link?
or can explain the procedure?
thanks
Jerome.You may need to use rsconfig to reset that database connection if it is
having issues:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref/htm/cpu_rsconfig_v1_5f1e.asp
Here is an activation doc for the rsactivate utility:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref/htm/cpu_rsconfig_v1_6yqq.asp
--
Douglas McDowell douglas@.nospam.solidqualitylearning.com
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OSWdzrDJFHA.1360@.TK2MSFTNGP10.phx.gbl...
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>|||I think this is the key management article you are referring to...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/arp_dbadmin_v1_98xh.asp?frame=true
"JÃ©jÃ©" wrote:
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>
>|||its ok
I'have found (or re-found ) the solution.
I have replaced the oledb32.dll file on the server by the 2.8 version
(instead-of the 2.7 version which is not upgraded during the Win2003
upgrade)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OSWdzrDJFHA.1360@.TK2MSFTNGP10.phx.gbl...
> Hi,
> After I have upgraded my server, RS stop working .
> a.. The report server cannot decrypt the symmetric key used to access
> sensitive or encrypted data in a report server database. You must either
> restore a backup key or delete all encrypted content and then restart the
> service. Check the documentation for more information.
> (rsReportServerDisabled) Get Online Help
> a.. Bad Data.
> I have the Key (exported using the rskeymgmt utility)
> But I can't reapply the key:
> an "Unable to connect to the database" error appear when I try to reapply
> the key.
> I have lost a document on the Microsoft web site which explain the entire
> process to reactivate RS.
> Anyone has the link?
> or can explain the procedure?
> thanks
> Jerome.
>

Tuesday, February 21, 2012

RS 2005 Upgrade Database Problem

I have installed Reporting Services 2005 on SQL Server 2005 SP2. Then when I try to connect to the Reporting Services i get the error "Invalid Database Version". Any suggest?

Try applying Service Pack 2 to the Reporting Services installation as well.

Larry

|||

Thanks,

i get some problems if i'll install for the second time SP2 on SQL Server 2005 with SP2.

|||

I just read the release notes for SP2 (http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm#_reporting_services) and found the following:

5.4.6 SP1-to-SP2 Upgrade Does Not Update the Report Server Database in Some Cases

The type of credentials that are specified on the report server database connection will determine whether Setup can upgrade a report server database from an SP1 or CTP version of SP2 to the final release of SP2.

If the report server connects to the report server database using database credentials or a Windows user account that differs from the one used to run the Report Server Windows service, the database will not be upgraded when the rest of the software is upgraded. If this occurs, you must use the Reporting Services Configuration tool to upgrade the report server database manually. On the Database Setup page, click Upgrade to apply the SP2 format to the report server database.

Does this match your problem? Did you install SQL Engine, SP2, and then SSRS on the same machine in that order? Please give a bit more detail about what you have done and what has happened.

Also, I believe there is a command line parameter that you can provide the service pack to force it to install. I will provide it when I find it.

Larry

Friday, March 23, 2012

RS2008 with SQL 2005 (different question)

Monday, March 12, 2012

RS upgrade Eval to Stnd?

RS upgrade

RS upgrade

RS SP2 Upgrade

Friday, March 9, 2012

RS Service Pack 1 question

RS Restore Version Conflict

RS Repository database version is dorked up, named instance has higher number than base in

RS problems after upgrade from SQLExpress to Standard

Reporting Services Error

The website cannot display the page

Wednesday, March 7, 2012

rs Enterprise Edition

Saturday, February 25, 2012

RS deactivated after upgrade from Win 2000 to W2k3

Tuesday, February 21, 2012

RS 2005 Upgrade Database Problem

5.4.6 SP1-to-SP2 Upgrade Does Not Update the Report Server Database in Some Cases

RS and HTTPS

Blog Archive

About Me