|
|
You're in the
sql server reporting services
group:Reposting: Database Version Issue
sql server reporting services:
error when trying to use report server: "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.54'. The expected version is 'C.0.8.43'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)" When I go into Reporting service configuration tool, the update button returns the following: "The database version matches your Reporting services installation" and the database version is reported as 'C.0.8.54'. this is critical and I need to get this up and running again. Any ideas? -- John Cleveland Network Manager Urban systems Ltd
Have you installed any SQL service packs BEFORE adding other parts
like 'reporting services' Also, there was a critical patch sent through windows update that updates SQL server. Not sure if that is causing you problems. On Apr 13, 1:16 am, John Cleveland [quoted text, click to view] <JohnClevel...@discussions.microsoft.com> wrote: > I just installed SP2 for 2005 standard edition and am getting the following > error when trying to use report server: > > "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.54'. The expected > version is 'C.0.8.43'. To continue, update the version of the report server > database and verify access rights. (rsInvalidReportServerDatabase)" > > When I go into Reporting service configuration tool, the update button > returns the following: > > "The database version matches your Reporting services installation" > > and the database version is reported as 'C.0.8.54'. > > this is critical and I need to get this up and running again. Any ideas? > > -- > John Cleveland > Network Manager > Urban systems Ltd
SP1 was already installed. reporting services was installed pre sp1.
I've narrowed down the sequence of events that lead to this issue. It seems there was a reporting services update that was installed without my knowledge that was intended for sp2 installs. SP2 wasn't installed yet. even though sp2 is now installed, i still get the error message listed previously. -- John Cleveland Network Manager Urban systems Ltd [quoted text, click to view] "gommo" wrote:
> Have you installed any SQL service packs BEFORE adding other parts > like 'reporting services' > > Also, there was a critical patch sent through windows update that > updates SQL server. Not sure if that is causing you problems. > > On Apr 13, 1:16 am, John Cleveland > <JohnClevel...@discussions.microsoft.com> wrote: > > I just installed SP2 for 2005 standard edition and am getting the following > > error when trying to use report server: > > > > "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.54'. The expected > > version is 'C.0.8.43'. To continue, update the version of the report server > > database and verify access rights. (rsInvalidReportServerDatabase)" > > > > When I go into Reporting service configuration tool, the update button > > returns the following: > > > > "The database version matches your Reporting services installation" > > > > and the database version is reported as 'C.0.8.54'. > > > > this is critical and I need to get this up and running again. Any ideas? > > > > -- > > John Cleveland > > Network Manager > > Urban systems Ltd > >
Is there a possibility that you actually have two different db's and your
reportserver instance is pointed at the "wrong" one frm the POV of the one that your web application thinks it should connect to? This might have happened if the person applying the update is not the administrator of the box. See http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213 It can also happen if you apply the update in the wrong identity, even if you are an administrator (I know that from personal experience <sigh> FWIW the ReportServer database has a sprocwhere this is hard coded. I kid you not. I think it gets adjusted during upgrades with a file called catalog.sql. ) Short version of the fix described in that thread: you have to stop IIS and RS and copy the files that were truly upgraded to the correct location -- but you should probably read the thread. HTH, [quoted text, click to view] >L< [quoted text, click to view] "John Cleveland" <JohnCleveland@discussions.microsoft.com> wrote in message
news:C797E3E5-38CA-4547-AD46-2215A50529A4@microsoft.com... >I just installed SP2 for 2005 standard edition and am getting the following > error when trying to use report server: > > "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.54'. The expected > version is 'C.0.8.43'. To continue, update the version of the report > server > database and verify access rights. (rsInvalidReportServerDatabase)" > > When I go into Reporting service configuration tool, the update button > returns the following: > > "The database version matches your Reporting services installation" > > and the database version is reported as 'C.0.8.54'. > > this is critical and I need to get this up and running again. Any ideas? > > > -- > John Cleveland > Network Manager > Urban systems Ltd >
I actually have this fixed now, it was caused by the sp2 upgrade. I
uninstalled rs, reinstalled and applied sp2 once again and all is fine. Reports cam back properly, but the data sources had to be reconfigured. No biggie. Thanks for your suggestions though. -- John Cleveland Network Manager Urban systems Ltd [quoted text, click to view] "Lisa Slater Nicholls" wrote:
> Is there a possibility that you actually have two different db's and your > reportserver instance is pointed at the "wrong" one frm the POV of the one > that your web application thinks it should connect to? > > This might have happened if the person applying the update is not the > administrator of the box. See > http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213 > > It can also happen if you apply the update in the wrong identity, even if > you are an administrator (I know that from personal experience <sigh> FWIW > the ReportServer database has a sprocwhere this is hard coded. I kid you > not. I think it gets adjusted during upgrades with a file called > catalog.sql. ) > > Short version of the fix described in that thread: you have to stop IIS and > RS and copy the files that were truly upgraded to the correct location -- > but you should probably read the thread. > > HTH, > > >L< > > > "John Cleveland" <JohnCleveland@discussions.microsoft.com> wrote in message > news:C797E3E5-38CA-4547-AD46-2215A50529A4@microsoft.com... > >I just installed SP2 for 2005 standard edition and am getting the following > > error when trying to use report server: > > > > "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.54'. The expected > > version is 'C.0.8.43'. To continue, update the version of the report > > server > > database and verify access rights. (rsInvalidReportServerDatabase)" > > > > When I go into Reporting service configuration tool, the update button > > returns the following: > > > > "The database version matches your Reporting services installation" > > > > and the database version is reported as 'C.0.8.54'. > > > > this is critical and I need to get this up and running again. Any ideas? > > > > > > -- > > John Cleveland > > Network Manager > > Urban systems Ltd > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |