rsItemNotFound for Report Models

I have a Sharepoint integrated Reporting Services server. I have created Report models based on Data Sources. I then created Report Builder Reports to make some BI Charts and Graphs. They look great and work fine for a few days then all of a sudden I get a rsItemNotFound error saying it cannot find the Report Model which is clearly there.

An error has occurred during report processing. (rsProcessingAborted)

The item 'IT Reports/PWPDB_Prod_Model.smdl' cannot be found. (rsItemNotFound)

If I open the Report Model from Report Builder it loads the data fields, but also fails to run reports with the same error

If I try to regenerate the model from the library I get an error stating that the model needs to be a generated model.

The model specified must be a generated model.

(rsModelNotGenerated)

Even after rebooting all of the servers in the farm I get the same messages. I can regenerate a model from the data source and it doesn't work. I am seeing no errors in the logs of my app server at all regarding reporting services.

It looks as though I will have to de-integrate Reporting Services as it is not viable for a business critical application.

Please for th elove of Zeus tell me you were able to solve this?

I am getting the exact same error. I have tried everything under the sun to make this work. Any advice?

rsItemNotFound for Report Models

I have a Sharepoint integrated Reporting Services server. I have created Report models based on Data Sources. I then created Report Builder Reports to make some BI Charts and Graphs. They look great and work fine for a few days then all of a sudden I get a rsItemNotFound error saying it cannot find the Report Model which is clearly there.

An error has occurred during report processing. (rsProcessingAborted)

The item 'IT Reports/PWPDB_Prod_Model.smdl' cannot be found. (rsItemNotFound)

If I open the Report Model from Report Builder it loads the data fields, but also fails to run reports with the same error

If I try to regenerate the model from the library I get an error stating that the model needs to be a generated model.

The model specified must be a generated model.

(rsModelNotGenerated)

Even after rebooting all of the servers in the farm I get the same messages. I can regenerate a model from the data source and it doesn't work. I am seeing no errors in the logs of my app server at all regarding reporting services.

It looks as though I will have to de-integrate Reporting Services as it is not viable for a business critical application.

Please for th elove of Zeus tell me you were able to solve this?

I am getting the exact same error. I have tried everything under the sun to make this work. Any advice?

rsInvalidReportServerDatabase-Error after installing SP2

Hello all,
I have a W2003 Server machine running Sql Server 2000 SP4 and Reporting
Services with *now* installed SP2 (before SP1). After installing the service
pack, I get the following error (sry, its german):
"Die Version der Berichtsserver-Datenbank liegt in einem Format vor, das
nicht gültig ist oder nicht gelesen werden kann. Die gefundene Version ist
'C.0.6.51'; die erwartete Version ist 'C.0.6.54'. Aktualisieren Sie die
Version der Berichtsserver-Datenbank, und überprüfen Sie die Zugriffsrechte,
um den Vorgang fortzusetzen. (rsInvalidReportServerDatabase)"
Can you give me please some advice, what I can do, to get the current
version of the database? I made backups from the report databases, but did
not manage to extract the key for encoding.
Thank you in advance.
Sandra GeislerI found a solution (well, I hope so). I just opened the stored
procedure GetDBVersion in the ReportServer database and exchanged the
last digit of the version number. I then restarted the ReportServer
service and it worked!! I tried to execute a report and it was
produced. If I am noticing some side effects, I will post them here.

rsInvalidReportServerDatabase

We are getting the following error when we try to deploy SQL report on to the reporting server
the 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 'Unknown'. The expected version is 'C.0.8.20'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)

We are using SQL server 2005 CTP and .Net 2005 beta 2.
the OS is Win xp and the reporting server is the local host.

Thanks a lot in advance.

Thanks & Regards

Jayan

You can use the Reporting Services Configuration tool (available from Start -> SQL Ctp -> Configuration Tools) to look at the configuraiton properties for the report server.

Navigate to the database page. If there is a database configured, and you get this error, chances are you somehow chose to use an existing database. If you tried to upgrade from a previous RS deployment, this might occur. The May CTP will support upgrade from SQL 2000 RS to the May CTP version.

I would recommend creating a new report server database and confguring the report servet use it. The config tool lets you do that.

-Lukasz

|||we used the reporting service config tool to configure the service also we created new database to be used by the reporting service(both reportingservice & reportingservicetemp) ew had also configured the reporting service to use SA account, tried with windows security and also with the service crediantials. still we are getting the same error, when we try to deploy reporting project. we get the same error when we try to create a new data source from the report manager web application.

Thanks a lot for your help.
Thanks & regards

Jayan|||Hi Lukasz,
Thanks for your help, we deleted the earlier databases, then created new using the tool. still when we tried it gave the same error. then we restarted the service and everything worked fine.

Thanks a lot for your help.

Thanks & Regards

Jayan.|||I actually think we fixed that bug for the June CTP. It was a problem where we were not picking up configuration file changes that affect the windows service DSN.

This led to problems with backing up the symmetric key. It could also, now that I think about it, cause problems publishing reports due to the need to encrypt information in the report datasources.

Good to hear you're up and running.
-Lukasz|||i got the same err while deploying with sql 2005 reporting services:

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)

the fix is:
1. In reporiting services configuration manager-> database setup, make sure you have the correct reporting database selected. In this case it will throw the same err when you try to initialize the reporting services.|||Hi,

I had the same problem you reported, and fixed it by creating a new database.

now when I navigate to http://localhost/reports

I get the following error:

XML Parsing Error: not well-formed
Location: http://moor-6ftylksqxm/reports/
Line Number 1, Column 2:<%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false" Inherits="Microsoft.ReportingServices.UI.HomePage" %>
-^

any idea what that's about?

regards

Helen|||I'm experiencing the same problem. Is this more of an IIS issue? Any help would be appreciated.

Thanks!sql

rsInvalidReportServerDatabase

We are getting the following error when we try to deploy SQL report on to the reporting server
the 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 'Unknown'. The expected version is 'C.0.8.20'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)

We are using SQL server 2005 CTP and .Net 2005 beta 2.
the OS is Win xp and the reporting server is the local host.

Thanks a lot in advance.

Thanks & Regards

Jayan

You can use the Reporting Services Configuration tool (available from Start -> SQL Ctp -> Configuration Tools) to look at the configuraiton properties for the report server.

Navigate to the database page. If there is a database configured, and you get this error, chances are you somehow chose to use an existing database. If you tried to upgrade from a previous RS deployment, this might occur. The May CTP will support upgrade from SQL 2000 RS to the May CTP version.

I would recommend creating a new report server database and confguring the report servet use it. The config tool lets you do that.

-Lukasz

|||we used the reporting service config tool to configure the service also we created new database to be used by the reporting service(both reportingservice & reportingservicetemp) ew had also configured the reporting service to use SA account, tried with windows security and also with the service crediantials. still we are getting the same error, when we try to deploy reporting project. we get the same error when we try to create a new data source from the report manager web application.

Thanks a lot for your help.
Thanks & regards

Jayan|||Hi Lukasz,
Thanks for your help, we deleted the earlier databases, then created new using the tool. still when we tried it gave the same error. then we restarted the service and everything worked fine.

Thanks a lot for your help.

Thanks & Regards

Jayan.|||I actually think we fixed that bug for the June CTP. It was a problem where we were not picking up configuration file changes that affect the windows service DSN.

This led to problems with backing up the symmetric key. It could also, now that I think about it, cause problems publishing reports due to the need to encrypt information in the report datasources.

Good to hear you're up and running.
-Lukasz|||i got the same err while deploying with sql 2005 reporting services:

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)

the fix is:
1. In reporiting services configuration manager-> database setup, make sure you have the correct reporting database selected. In this case it will throw the same err when you try to initialize the reporting services.|||Hi,

I had the same problem you reported, and fixed it by creating a new database.

now when I navigate to http://localhost/reports

I get the following error:

XML Parsing Error: not well-formed
Location: http://moor-6ftylksqxm/reports/
Line Number 1, Column 2:<%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false" Inherits="Microsoft.ReportingServices.UI.HomePage" %>
-^

any idea what that's about?

regards

Helen|||I'm experiencing the same problem. Is this more of an IIS issue? Any help would be appreciated.

Thanks!

rsInvalidReportServerDatabase

We are getting the following error when we try to deploy SQL report on to the reporting server
the 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 'Unknown'. The expected version is 'C.0.8.20'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)

We are using SQL server 2005 CTP and .Net 2005 beta 2.
the OS is Win xp and the reporting server is the local host.

Thanks a lot in advance.

Thanks & Regards

Jayan

You can use the Reporting Services Configuration tool (available from Start -> SQL Ctp -> Configuration Tools) to look at the configuraiton properties for the report server.

Navigate to the database page. If there is a database configured, and you get this error, chances are you somehow chose to use an existing database. If you tried to upgrade from a previous RS deployment, this might occur. The May CTP will support upgrade from SQL 2000 RS to the May CTP version.

I would recommend creating a new report server database and confguring the report servet use it. The config tool lets you do that.

-Lukasz

|||we used the reporting service config tool to configure the service also we created new database to be used by the reporting service(both reportingservice & reportingservicetemp) ew had also configured the reporting service to use SA account, tried with windows security and also with the service crediantials. still we are getting the same error, when we try to deploy reporting project. we get the same error when we try to create a new data source from the report manager web application.

Thanks a lot for your help.
Thanks & regards

Jayan|||Hi Lukasz,
Thanks for your help, we deleted the earlier databases, then created new using the tool. still when we tried it gave the same error. then we restarted the service and everything worked fine.

Thanks a lot for your help.

Thanks & Regards

Jayan.|||I actually think we fixed that bug for the June CTP. It was a problem where we were not picking up configuration file changes that affect the windows service DSN.

This led to problems with backing up the symmetric key. It could also, now that I think about it, cause problems publishing reports due to the need to encrypt information in the report datasources.

Good to hear you're up and running.
-Lukasz|||i got the same err while deploying with sql 2005 reporting services:

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)

the fix is:
1. In reporiting services configuration manager-> database setup, make sure you have the correct reporting database selected. In this case it will throw the same err when you try to initialize the reporting services.|||Hi,

I had the same problem you reported, and fixed it by creating a new database.

now when I navigate to http://localhost/reports

I get the following error:

XML Parsing Error: not well-formed
Location: http://moor-6ftylksqxm/reports/
Line Number 1, Column 2:<%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false" Inherits="Microsoft.ReportingServices.UI.HomePage" %>
-^

any idea what that's about?

regards

Helen|||I'm experiencing the same problem. Is this more of an IIS issue? Any help would be appreciated.

Thanks!

rsInvalidReportServerDatabase

We are getting the following error when we try to deploy SQL report on to the reporting server
the 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 'Unknown'. The expected version is 'C.0.8.20'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)

We are using SQL server 2005 CTP and .Net 2005 beta 2.
the OS is Win xp and the reporting server is the local host.

Thanks a lot in advance.

Thanks & Regards

Jayan

You can use the Reporting Services Configuration tool (available from Start -> SQL Ctp -> Configuration Tools) to look at the configuraiton properties for the report server.

Navigate to the database page. If there is a database configured, and you get this error, chances are you somehow chose to use an existing database. If you tried to upgrade from a previous RS deployment, this might occur. The May CTP will support upgrade from SQL 2000 RS to the May CTP version.

I would recommend creating a new report server database and confguring the report servet use it. The config tool lets you do that.

-Lukasz

|||we used the reporting service config tool to configure the service also we created new database to be used by the reporting service(both reportingservice & reportingservicetemp) ew had also configured the reporting service to use SA account, tried with windows security and also with the service crediantials. still we are getting the same error, when we try to deploy reporting project. we get the same error when we try to create a new data source from the report manager web application.

Thanks a lot for your help.
Thanks & regards

Jayan|||Hi Lukasz,
Thanks for your help, we deleted the earlier databases, then created new using the tool. still when we tried it gave the same error. then we restarted the service and everything worked fine.

Thanks a lot for your help.

Thanks & Regards

Jayan.|||I actually think we fixed that bug for the June CTP. It was a problem where we were not picking up configuration file changes that affect the windows service DSN.

This led to problems with backing up the symmetric key. It could also, now that I think about it, cause problems publishing reports due to the need to encrypt information in the report datasources.

Good to hear you're up and running.
-Lukasz|||i got the same err while deploying with sql 2005 reporting services:

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)

the fix is:
1. In reporiting services configuration manager-> database setup, make sure you have the correct reporting database selected. In this case it will throw the same err when you try to initialize the reporting services.|||Hi,

I had the same problem you reported, and fixed it by creating a new database.

now when I navigate to http://localhost/reports

I get the following error:

XML Parsing Error: not well-formed
Location: http://moor-6ftylksqxm/reports/
Line Number 1, Column 2:<%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false" Inherits="Microsoft.ReportingServices.UI.HomePage" %>
-^

any idea what that's about?

regards

Helen|||I'm experiencing the same problem. Is this more of an IIS issue? Any help would be appreciated.

Thanks!