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 Install killing me w/ 'NT AUTHORITY\ANONYMOUS LOGON' error

Hi - my config is as follows:
- RS Standard on Windows Server 2003 (server1)
- SQL Server 2000 for repository on a different server server2 (same domain)
- I am logged onto server1 as domain admin (full SQL perms to server2)
- I have successfully installed other RS repositories to server2 (different
db names of course)
Installation fails at the "Configuring Microsoft SQL Server" part with error
message: "SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT Authority\Anonymous
Logon'. "
It appears to be losing my interactively logged on credentials.
Here is info from the log:
SQL_ERROR (-1) in SQLDriverConnectW
sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
user 'NT AUTHORITY\ANONYMOUS LOGON'.
Error 29545. SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'.
Refer to the Server error logs and setup logs for more detailed information.
MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
Standard Edition -- Error 29545. SQL Setup failed to connect to the database
service for server configuration. The error was: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
Refe
r to the Server error logs and setup logs for more detailed information.
--
Thoughts?
thanksHow are permissions configured for server2? I've had some problems in the
past connecting from a local machine account to a domain sql server
(configured with mixed security). I was attempting SQL authentication. It
started working when I changed the service to run with a domain user
identity rather than a local machine user; then it connected with SQL
authentication just fine. That was odd, because I expected SQL
authentication to work regardless of the windows login identity.
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same
> domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2
> (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with
> error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT
> Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for
> server
> configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed
> information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the
> database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||Hi Jeff - Just to clarify my understanding of the installation process as a
baseline assumption so we're on the same page - it's the ID of the
interactively logged on user performing the install who the repository
database is created under.
Regarding permissions for server2, the user I am logged onto server1 as is
domainA\userA. This user is a domain admin and has full admin to server1 and
server2, as well as SQL Server on server2.
regards
"Jeff A. Stucker" wrote:
> How are permissions configured for server2? I've had some problems in the
> past connecting from a local machine account to a domain sql server
> (configured with mixed security). I was attempting SQL authentication. It
> started working when I changed the service to run with a domain user
> identity rather than a local machine user; then it connected with SQL
> authentication just fine. That was odd, because I expected SQL
> authentication to work regardless of the windows login identity.
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
> news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> > Hi - my config is as follows:
> >
> > - RS Standard on Windows Server 2003 (server1)
> > - SQL Server 2000 for repository on a different server server2 (same
> > domain)
> > - I am logged onto server1 as domain admin (full SQL perms to server2)
> > - I have successfully installed other RS repositories to server2
> > (different
> > db names of course)
> >
> > Installation fails at the "Configuring Microsoft SQL Server" part with
> > error
> > message: "SQL Setup failed to connect to the database service for server
> > configuration. The error was: Login failed for user 'NT
> > Authority\Anonymous
> > Logon'. "
> >
> > It appears to be losing my interactively logged on credentials.
> >
> > Here is info from the log:
> >
> > SQL_ERROR (-1) in SQLDriverConnectW
> > sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> > user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > Error 29545. SQL Setup failed to connect to the database service for
> > server
> > configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS
> > LOGON'.
> > Refer to the Server error logs and setup logs for more detailed
> > information.
> > MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> > Standard Edition -- Error 29545. SQL Setup failed to connect to the
> > database
> > service for server configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS LOGON'.
> > Refe
> > r to the Server error logs and setup logs for more detailed information.
> >
> > --
> >
> > Thoughts?
> > thanks
>
>|||I had the same problem when I installed RS yesterday. For some reason the
credentials are not passed correctly and I had to run the setup program from
the command line and explicitly pass it credentials with which to run the
setup program. The command to run setup ends up looking something like this:
setup /i "setup\rsrun.msi" RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
I've been told you can use any credentials you want (domain administrator,
etc.), but I just used the sql sa account, and that worked correctly.
I had the same problem when installing sp1. I had to manually extract the
.cab file and run setup from the command line once again:
sp1setup RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
Hope this helps.
David
"ISGADMIN" wrote:
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2 (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||> Installation fails at the "Configuring Microsoft SQL Server" part
with error
> message: "SQL Setup failed to connect to the database service for
server
> configuration. The error was: Login failed for user 'NT
Authority\Anonymous
> Logon'. "
>
Another fix for this - add the 'NT Authority\Anonymous Logon' account
as Local Admin on the SQL Server box and then be sure
Builtin\Administrators has SA access on the SQL Server.
Run the install and then change the dbowner to "sa" and remove the
account.
That's how I finally got it installed on a Win2003 box...
-Annette

RS 2005 using SQL Server 2000 as a repository?

Hi - If I want a Reporting Services 2005 installation in which the repository
is on a *different* box than the RS services, can the repository database be
SQL Server 2000 rather than SQL Server 2005?
Thanks and regards,Yes. As a matter of fact it can be on the same box (mine is). You do need a
2005 license for the box that has RS 2005 installed. In your case a 2005
license for the box with RS services and the metadata box can stay at 2000
without a license for 2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:1D8C637A-2E76-487F-B006-0F6012B08EDE@.microsoft.com...
> Hi - If I want a Reporting Services 2005 installation in which the
> repository
> is on a *different* box than the RS services, can the repository database
> be
> SQL Server 2000 rather than SQL Server 2005?
> Thanks and regards,|||Hi Bruce, thanks a lot for the quick response.
Regards
"Bruce L-C [MVP]" wrote:
> Yes. As a matter of fact it can be on the same box (mine is). You do need a
> 2005 license for the box that has RS 2005 installed. In your case a 2005
> license for the box with RS services and the metadata box can stay at 2000
> without a license for 2005.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
> news:1D8C637A-2E76-487F-B006-0F6012B08EDE@.microsoft.com...
> > Hi - If I want a Reporting Services 2005 installation in which the
> > repository
> > is on a *different* box than the RS services, can the repository database
> > be
> > SQL Server 2000 rather than SQL Server 2005?
> >
> > Thanks and regards,
>
>