Ads

15 February 2012

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 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)

Error 1 :-
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 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase) 

In SSRS 2005

WorkAround :-

1. Check ReportServer and ReportServerTempDB is created
2. If DB is missing, Take a Backup from server and restore, or need to uninstall SSRS and reinstall
3. Connect to report config Manager
4. Database Settings click update.
5. Make sure all goes Green in Report Configuration
6. Now we will be able to browse .


Error 2 :- "Create New Database Script for report server"


In SQL Server Reporting Services 2005, we can generate the scripts using Reporting Service Configuration Manager tool.

In SQL Server Reporting Services 2008, we can create the RSExecRole using the following script:



And then execute the scripts in Catalog.sql and CatalogTempDB.sql to create table, view, stored produce and so on.

USE [ReportServer]
GO
 
if not exists (select * from sysusers where issqlrole = 1 and name = 'RSExecRole')
BEGIN
 EXEC sp_addrole 'RSExecRole'
END
GO
 
USE msdb
GO
 
if not exists (select * from sysusers where issqlrole = 1 and name = 'RSExecRole')
BEGIN
 EXEC sp_addrole 'RSExecRole'
END
GO
 
USE master
GO
 
if not exists (select * from sysusers where issqlrole = 1 and name = 'RSExecRole')
BEGIN
 EXEC sp_addrole 'RSExecRole'
END
GO
 
USE [ReportServerTempDB]
GO
 
if not exists (select * from sysusers where issqlrole = 1 and name = 'RSExecRole')
BEGIN
 EXEC sp_addrole 'RSExecRole'
END
GO




No comments:

Post a Comment