sql server reporting services: RS Repository database version is dorked up, named instance has higher number than base instance, now can't access it. -- sql server reporting services

You're in the

sql server reporting services

group:

RS Repository database version is dorked up, named instance has higher number than base instance, now can't access it.

Steve MunLeeuw
10/23/2006 11:45:12 AM

sql server reporting services: 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

Re: RS Repository database version is dorked up, named instance has higher number than base instance, now can't access it.

Steve MunLeeuw
10/23/2006 11:52:30 AM

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

[quoted text, click to view]

Re: RS Repository database version is dorked up, named instance has higher number than base instance, now can't access it.

Steve MunLeeuw
10/23/2006 1:27:53 PM

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

[quoted text, click to view]

Re: RS Repository database version is dorked up, named instance has higher number than base instance, now can't access it.

Michael Abair
10/23/2006 3:20:00 PM

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.

[quoted text, click to view]

RE: RS Repository database version is dorked up, named instance has higher number than base instance, now can't access it.

Senthil
9/12/2007 6:04:30 AM

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

RE: RS Repository database version is dorked up, named instance ha

Chris Alton [MS]
9/28/2007 11:26:00 AM

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

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server reporting services group.

home · blog · groups

Questions? Comments? Contact the dn