RSExecutionLog_Update.dts fails for named SQL Instance

Hi:
I am running SRS on a named instance of SQL. When I attempt to run this DTS
package, it fails on the five update steps with the error message "Cannot
open database requested in login 'ReportServer'. Login fails."
How can I point it to the non-default instance of SQL.
Thanks in advance.
Bruce.Have you tried changing the server name in the RSExecutionLog_Update.ini
file? I have never used the package with a non-default instance of SQL
server, but I assume it should work when you make the appropriate edits in
the above ini file.
Charles Kangai, MCT, MCDBA
"bwschiek@.hotmail.com" wrote:
> Hi:
> I am running SRS on a named instance of SQL. When I attempt to run this DTS
> package, it fails on the five update steps with the error message "Cannot
> open database requested in login 'ReportServer'. Login fails."
> How can I point it to the non-default instance of SQL.
> Thanks in advance.
> Bruce.|||Hi Charles:
It worked! I changed the server setting for both the source and destination
from (local) to ServerName\SQLInstanceName and the DTS package executed as
intented!
Thanks for the quick and accurate reply!
Bruce.
"Charles Kangai" wrote:
> Have you tried changing the server name in the RSExecutionLog_Update.ini
> file? I have never used the package with a non-default instance of SQL
> server, but I assume it should work when you make the appropriate edits in
> the above ini file.
> Charles Kangai, MCT, MCDBA
> "bwschiek@.hotmail.com" wrote:
> > Hi:
> >
> > I am running SRS on a named instance of SQL. When I attempt to run this DTS
> > package, it fails on the five update steps with the error message "Cannot
> > open database requested in login 'ReportServer'. Login fails."
> >
> > How can I point it to the non-default instance of SQL.
> >
> > Thanks in advance.
> >
> > Bruce.

RS2005 Standard install error..

I am installing SQL 2005 and RS 2005 on a new W2k3 server. I have tried to
install to a default instance and to a named instance and continue to get the
following error when I try to retrieve the reports page or connect to the
reporting services thru Microsoft SQL server Management Studio.
The attempt to connect to the report server failed. Check your connection
information and that the report server is a compatible version.
In the Log file ReportServerWebApp__01_03_2006_13_51_00.log I see:
w3wp!ui!7!1/3/2006-12:01:32:: e ERROR: The attempt to connect to the report
server failed. Check your connection information and that the report server
is a compatible version.
w3wp!ui!7!1/3/2006-12:01:33:: e ERROR: HTTP status code --> 500
--Details--
Microsoft.SqlServer.ReportingServices2005.RSConnection+MissingEndpointException:
The attempt to connect to the report server failed. Check your connection
information and that the report server is a compatible version. -->
System.Net.WebException: The request failed with HTTP status 404: Not Found.
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at
Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
methodname)
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
-- End of inner exception stack trace --
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!7!1/3/2006-12:01:34:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)Did anyone find a solutions to this issue, i have encountered the same
problem, and cannot seem to get it to work.
Thanks
Jim wrote:
> I am installing SQL 2005 and RS 2005 on a new W2k3 server. I have tried to
> install to a default instance and to a named instance and continue to get the
> following error when I try to retrieve the reports page or connect to the
> reporting services thru Microsoft SQL server Management Studio.
> The attempt to connect to the report server failed. Check your connection
> information and that the report server is a compatible version.
>
> In the Log file ReportServerWebApp__01_03_2006_13_51_00.log I see:
>
> w3wp!ui!7!1/3/2006-12:01:32:: e ERROR: The attempt to connect to the report
> server failed. Check your connection information and that the report server
> is a compatible version.
> w3wp!ui!7!1/3/2006-12:01:33:: e ERROR: HTTP status code --> 500
> --Details--
> Microsoft.SqlServer.ReportingServices2005.RSConnection+MissingEndpointException:
> The attempt to connect to the report server failed. Check your connection
> information and that the report server is a compatible version. -->
> System.Net.WebException: The request failed with HTTP status 404: Not Found.
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
> at
> Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
> methodname)
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
> -- End of inner exception stack trace --
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Page.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> w3wp!ui!7!1/3/2006-12:01:34:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)|||I'm experiencing the same problems, you might think it has something to do
with SSL, but it is not necessary to use it, is it?
I would be very pleased with some help regarding this subject!|||Why are no microsoft people responding to these posts? Thought that was the
deal with this support option via msdn?
I'm having the same issue and have yet to get report manager to work via
http://servername/reports.
--
Thanks,
Chris.
"Ruud0011" wrote:
> I'm experiencing the same problems, you might think it has something to do
> with SSL, but it is not necessary to use it, is it?
> I would be very pleased with some help regarding this subject!|||I've had this same issue. I installed RS2005 and VS2005 on a new Windows
2003 server. This was not an upgrade. I am using an SSL certificate and
edited the C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\ReportManager\RSWebApplication.config file by removing the entry for
<ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>.
The ReportURL entry looks like this
ReportServerUrl>https://localhost/reportserver</ReportServerUrl> -- Note that
it says "reportserver" and not reports which is why I kept getting the same
error. The C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\ReportServer\RSReportServer.config file was edited to reflect the
SecureConnectionLevel Value 3 and the URLRoot was
https://localhost/reportserver
All is well. No more error messages.
WMH
"whoopdaddy" wrote:
> Why are no microsoft people responding to these posts? Thought that was the
> deal with this support option via msdn?
> I'm having the same issue and have yet to get report manager to work via
> http://servername/reports.
> --
> Thanks,
> Chris.
>
> "Ruud0011" wrote:
> > I'm experiencing the same problems, you might think it has something to do
> > with SSL, but it is not necessary to use it, is it?
> >
> > I would be very pleased with some help regarding this subject!|||Thanks WMH - I had same problem - just spent a few very frustrating days
trying to fix this until I spotted your advice.
Paddy
"WMH" wrote:
> I've had this same issue. I installed RS2005 and VS2005 on a new Windows
> 2003 server. This was not an upgrade. I am using an SSL certificate and
> edited the C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportManager\RSWebApplication.config file by removing the entry for
> <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>.
> The ReportURL entry looks like this
> ReportServerUrl>https://localhost/reportserver</ReportServerUrl> -- Note that
> it says "reportserver" and not reports which is why I kept getting the same
> error. The C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportServer\RSReportServer.config file was edited to reflect the
> SecureConnectionLevel Value 3 and the URLRoot was
> https://localhost/reportserver
> All is well. No more error messages.
> WMH
>
> "whoopdaddy" wrote:
> > Why are no microsoft people responding to these posts? Thought that was the
> > deal with this support option via msdn?
> >
> > I'm having the same issue and have yet to get report manager to work via
> > http://servername/reports.
> > --
> > Thanks,
> > Chris.
> >
> >
> > "Ruud0011" wrote:
> >
> > > I'm experiencing the same problems, you might think it has something to do
> > > with SSL, but it is not necessary to use it, is it?
> > >
> > > I would be very pleased with some help regarding this subject!|||I feel certain that I missed some important documentation that Microsoft
provided us on this issue, but your "removing the entry for
<ReportServerVirtualDirectory>" is the best information on this error
message. I don't have SSL and the Configuration Tool doesn't fix this problem
when you move the virtual directories to another website. I have wasted
entirely too many hours on this and have actually reloaded our 2003 server
twice. Simply remove the <ReportServerVirtualDirectory> tag and all is well.
Thank you very much for your post!!!
Thanks,
Chris
"WMH" wrote:
> I've had this same issue. I installed RS2005 and VS2005 on a new Windows
> 2003 server. This was not an upgrade. I am using an SSL certificate and
> edited the C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportManager\RSWebApplication.config file by removing the entry for
> <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>.
> The ReportURL entry looks like this
> ReportServerUrl>https://localhost/reportserver</ReportServerUrl> -- Note that
> it says "reportserver" and not reports which is why I kept getting the same
> error. The C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportServer\RSReportServer.config file was edited to reflect the
> SecureConnectionLevel Value 3 and the URLRoot was
> https://localhost/reportserver
> All is well. No more error messages.
> WMH
>
> "whoopdaddy" wrote:
> > Why are no microsoft people responding to these posts? Thought that was the
> > deal with this support option via msdn?
> >
> > I'm having the same issue and have yet to get report manager to work via
> > http://servername/reports.
> > --
> > Thanks,
> > Chris.
> >
> >
> > "Ruud0011" wrote:
> >
> > > I'm experiencing the same problems, you might think it has something to do
> > > with SSL, but it is not necessary to use it, is it?
> > >
> > > I would be very pleased with some help regarding this subject!

RS2005 Multi-Value Problem, urgent!

Dose RS 2005 Multi-Value parameter function can work?
Trying to use multi-value function of RS2005,
dataset named as "AdventureWorks and syntax as following:
SELECT Name, ProductCategoryID
FROM Production.ProductCategory
WHERE (ProductCategoryID = @.ID)
Properties: multi-value
Available values: From query
Dataset: dataset1
Value field: ProductCategoryID
Label field: Name
Dataset1's syntax:
SELECT Name, ProductCategoryID
FROM Production.ProductCategory
Preview report and choice Bikes, Clothing has error msg:
An error occurred during local report processing.
An error has occurred during report processing.
Query execution failed for data set 'AdventureWorks'.
Incorrect syntax near ','.
Dose anyone has the same problem?
In Beta the Multi-Value function is ok,
but in released enterprise version I have this problem?
What's happened?
Thanks for any advice!
AngiYou have to write
... WHERE ProductCategoryID IN (@.ID)
"Angi" <enchiw@.msn.com> schrieb im Newsbeitrag
news:uIw261SAGHA.3968@.TK2MSFTNGP10.phx.gbl...
> Dose RS 2005 Multi-Value parameter function can work?
> Trying to use multi-value function of RS2005,
> dataset named as "AdventureWorks and syntax as following:
> SELECT Name, ProductCategoryID
> FROM Production.ProductCategory
> WHERE (ProductCategoryID = @.ID)
> Properties: multi-value
> Available values: From query
> Dataset: dataset1
> Value field: ProductCategoryID
> Label field: Name
> Dataset1's syntax:
> SELECT Name, ProductCategoryID
> FROM Production.ProductCategory
> Preview report and choice Bikes, Clothing has error msg:
> An error occurred during local report processing.
> An error has occurred during report processing.
> Query execution failed for data set 'AdventureWorks'.
> Incorrect syntax near ','.
> Dose anyone has the same problem?
> In Beta the Multi-Value function is ok,
> but in released enterprise version I have this problem?
> What's happened?
> Thanks for any advice!
> Angi
>|||uh... Thanks Ralph...
Don't know what I think... ><
Make the funny mistake..
"Ralph Watermann" <We.Want@.NoSpam.de> ¼¶¼g©ó¶l¥ó·s»D:uizY49VAGHA.3928@.tk2msftngp13.phx.gbl...
> You have to write
> ... WHERE ProductCategoryID IN (@.ID)
>
> "Angi" <enchiw@.msn.com> schrieb im Newsbeitrag
> news:uIw261SAGHA.3968@.TK2MSFTNGP10.phx.gbl...
>> Dose RS 2005 Multi-Value parameter function can work?
>> Trying to use multi-value function of RS2005,
>> dataset named as "AdventureWorks and syntax as following:
>> SELECT Name, ProductCategoryID
>> FROM Production.ProductCategory
>> WHERE (ProductCategoryID = @.ID)
>> Properties: multi-value
>> Available values: From query
>> Dataset: dataset1
>> Value field: ProductCategoryID
>> Label field: Name
>> Dataset1's syntax:
>> SELECT Name, ProductCategoryID
>> FROM Production.ProductCategory
>> Preview report and choice Bikes, Clothing has error msg:
>> An error occurred during local report processing.
>> An error has occurred during report processing.
>> Query execution failed for data set 'AdventureWorks'.
>> Incorrect syntax near ','.
>> Dose anyone has the same problem?
>> In Beta the Multi-Value function is ok,
>> but in released enterprise version I have this problem?
>> What's happened?
>> Thanks for any advice!
>> Angi
>

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
>