rsExecutionNotFound !

I have been frequetly visiting your blogs with a solution for rsExecutionNotFound. I used johngaallard's script to extend the accesstimeout(to 6000 ) eventhough that was not the base of the problem.

My Reports run in less than 15 sec (max). I have enabled caching for about 12 hours ( there are nightly updates) using [Cache a temporary copy of the report. Expire copy of report after a number of minutes option])

The reports are rendered using a ReportViewerControl in an ASP.Net2.0 web application.(The report is rendered as PDF and then shown in another IFrame using Adobe plugin).The ASP application session timeout is 100mts.

The problem i am facing is that after sometime, the rsExecutionNotfound starts occuring for some report with a specific set of parameters. No amount of rerunning the report will stop. The same report with different parameters renders fine. The only way to stop this is to set the cache option 'Do not cache temporary copies of this report'.

If i set ''Do not cache temporary copies of this report'' there are no errors. I am doing caching mainly to bring down report rendering from 15 sec to 2-3 secs. I am using PDF format .

I am now thinking of working around by trying to catch the Exception that occurs and trying to re-render the report. If this is the only way, how can i do it.

I had fought fiercely to use SSRS and now I am in a fix
Any help is appreciated.
Thanks,
Saj

You probably want to post this in the reporting services forum. There are many more experts in that area there.

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 on sql server 2000 and 2005 on same machine

Hi Samuel,

I'd like to draw on your expertise on this topic. I've been browsing at many blogs/forums about installing SQL Server 2000 and 2005 on the same machine.

What I'd like to know is how does that work with Reporting Services? Your machine's IIS will need to work with Reporting Services 2000 and Reporting Services 2005. The RS 2005 requires .NET Framework 2.0 and RS 2000 requires .NET Framework 1.1. IIS can only support 1 version of the .NET Framework at a time.

Thanks kindly.

I ran the question by the RS folks and here is the reply:

RS 2005 will run in a separate ASP.Net app pool from RS 2000. In this way, the .Net Frameworks are segregated. To this extent, IIS does support multiple .Net Frameworks versions, just not in the same app pool.

RS 2000
Default app pool
.Net Framework 1.1
Default virtual directories

RS 2005
“ReportServer” or some other user-specified app pool
.Net Framework 2.0
Non-default virtual directories (nominally they will be “ReportServer” and “Reports” appended with “$” plus the instance name, but they can be user-specified also)

Thanks,
Sam Lester (MSFT)

|||Here is another question regarding the problem, i ve installed Reporting Services 2005 on 64-bit machine and when i configure it, it is configured properly but when i tried to access Report Server it asks me for credentials i provide appropriate credentials then it IIS message appears You are not authorized to access this page, secondly when i try to access the Reports it say Page not found. Then i switched the IIS mode from 64-bit to 32-bit and installed .NET Framework 1.1 and 2.0 for 32-bit but same thing is happening again with message when i try to access reports "Internal Server Error". Is there any seperate version for 32-bit and 64-bit of Reporting Services? Please help me in this regard, i am stuck in this matter for too much time now....