ReportViewer fails when called direct from production server / works when called indirect

Hi Folks ...

Here is my setup and then I'll detail what is working, not working with the ReportViewer control:

1) Server (Everything is contained on one server right now) sits in the DMZ (Web application available to Internet)

- Win2003 Server

- IIS

Web Site A -www.site1.comWeb Site B -www.site2.comWeb Site C -www.site3.com

- SQL Server 2005

- SQL Server Reporting Services

Each web site has its own SRSS Virtual Reports and ReportServer directories setup for reporting.

2) Development Workstation - inside the firewall.

- Windows XP Professional

- Visual Studio 2005

Ok, you have the setup. Now for the problem. I've created a web application that uses form authentication with user ids and passwords stored in the database that I check to allow authorization in to the web program. I have created reports and deployed them via Visual Studio to the Report Server.

Run Verification:

Successfully runs when I run by keying the web address in to the web browser - am prompted for user id and password, I manually key in the user id and password that I have coded in to the application:http://www.site1.com/ReportServer?/ApplicationName/ReportName

Run from within Visual Studio on Development Machine - note this authenticates properly - note that when run within VS, it still calls report on server:

Successfully runs the report when I have the following code on a form - the ReportViewer control is located within the web page and is named rptMOCLog (I created the MOCReportServerCredentials authentication mechanism to support my Form based authentication based on articles in this Forum and MSDN to create the authentication mechanism that can be passed to ReportServer)

ProtectedSub rptMOCLog_Init(ByVal senderAsObject,ByVal eAs System.EventArgs)Handles rptMOCLog.Init

Dim loParameters(3)As ReportParameter

Me.rptMOCLog.ServerReport.ReportServerCredentials =New ReportServerCredentials("ApplicationReportUser","ApplicationReportUserPassword","")

Me.rptMOCLog.ServerReport.ReportServerUrl =New Uri("http://www.site1.com/ReportServer")

Me.rptMOCLog.ServerReport.ReportPath ="/ApplicationName/ReportName"

loParameters(0) =

New Microsoft.Reporting.WebForms.ReportParameter("corpID", Session("svCorpId").ToString,False)

loParameters(1) =

New Microsoft.Reporting.WebForms.ReportParameter("plantID", Session("svPlantId").ToString,False)

loParameters(2) =

New Microsoft.Reporting.WebForms.ReportParameter("dateBegin", Format(DateAdd(DateInterval.Year, -1, Date.Now()),"d").ToString,True)

loParameters(3) =

New Microsoft.Reporting.WebForms.ReportParameter("dateEnd", Format(DateAdd(DateInterval.Day, 1,Date.Now()),"d").ToString,True) Me.rptMOCLog.ServerReport.SetParameters(loParameters)EndSub

Next I move the entire application up to the IIS Server and attempt to run from there - moved to thewww.site1.com web site on the server.

Application fails to run the report with the following message

The request failed with HTTP status 401: Unauthorized.

I have verified that the ApplicationReportUser is a part of the following groups:

SQLServer2005ReportingServicesWebServiceUser$ENTERPRISE$MSSQLSERVERSQLServer2005ReportServerUser$ENTERPRISE$MSSQLSERVER

Ok, I'm banging my head against the wall and it's starting to hurt. Anyone have any clue on how to make the report run from the production server?

I ended up having to blow away and reinstall the entire SQL Server environment to get rid of my error and have the reports display properly. Don't know what other solutions may exist, but this is the only way I could solve the problem.

Hoping this doesn't happen after I role this in to production ... fingers crossed.

David

ReportViewer 2005

I'm working with vs.net 2005 and SRS 2005. I setup a custom security
extension and I connect using a proxy class via "LogonUser" to a custom
asp.net web application. When I set some parameters and pass them to the
reportviewer I get the following error:
{"The parameter '{0}' cannot be an empty string. Parameter name:
cookie.Domain"}
I tryed a few different things but nothing works... Has anyone else ran into
this problem?
Nuno PereiraI was passing an incomplete cookie to ReportServerCredentials. I change how i
retrieve the cookie to use the Utilities class provided by the extension
sample. Now, I'm stuck on something else. Everything seems to get accepted
except i get an
"Object moved" page.
This is how i retrieve my cookie:
Dim netCookie As System.Net.Cookie =Utilities.TranslateCookie(HttpContext.Current.Request.Cookies(Utilities.CustomAuthCookieName))
ReportViewer1.ProcessingMode = ProcessingMode.Remote
ReportViewer1.ServerReport.ReportServerCredentials = New
CustomCredentials(netCookie, "admin", "password", "domainName")
ReportViewer1.ServerReport.ReportServerUrl = New
Uri(ConfigurationManager.AppSettings("ReportServerUrl"))
ReportViewer1.ServerReport.ReportPath = Session("ReportPath")
SetReportParams() 'Custom method that sets params
__________________________________________________________
When I use this code I the reportserver spits out the following:
The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a
href='/ReportServer/logon.aspx?ReturnUrl=%2fReportServer%2fReportExecution2005.asmx'>here</a>.</h2>
</body></html>
--.
Nuno Pereira
"Nuno" wrote:
> I'm working with vs.net 2005 and SRS 2005. I setup a custom security
> extension and I connect using a proxy class via "LogonUser" to a custom
> asp.net web application. When I set some parameters and pass them to the
> reportviewer I get the following error:
> {"The parameter '{0}' cannot be an empty string. Parameter name:
> cookie.Domain"}
> I tryed a few different things but nothing works... Has anyone else ran into
> this problem?
> Nuno Pereirasql

ReportServer component is not showing during installaion

when i try to install Sql Server 2000 reporting services setup on XP then it shows me client components only.Report Server and report manager component is not showing.Due to this i am unable to run the report project using report server.It gives a messege "No Reprot Server was found at http://localhost/ReprotServer".How can i installed report server.

Can you check if IIS is installed? The below link might give you some more info.

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Thanks,
Sharmila

|||Thanks Sharmila....

Reports Manager does not list or manage reports...

I recently installed RS and have deployed several reports but none show up under the reports manager. Only the top toolbar folder shows home.
Setup:
ReportServer: local administrator
ReportServer Database: SQL User auth.
Windows 2003
SQL 2000
Any Ideas?Sounds like you are accessing the server with an account that does not have
permissions. Did you assign any security roles?
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"jhines" <jhines@.discussions.microsoft.com> wrote in message
news:991D3C55-3022-4F3C-B7A8-2395D243ADDC@.microsoft.com...
>I recently installed RS and have deployed several reports but none show up
>under the reports manager. Only the top toolbar folder shows home.
> Setup:
> ReportServer: local administrator
> ReportServer Database: SQL User auth.
> Windows 2003
> SQL 2000
> Any Ideas?|||Permissions?
"jhines" <jhines@.discussions.microsoft.com> wrote in message
news:991D3C55-3022-4F3C-B7A8-2395D243ADDC@.microsoft.com...
> I recently installed RS and have deployed several reports but none show up
under the reports manager. Only the top toolbar folder shows home.
> Setup:
> ReportServer: local administrator
> ReportServer Database: SQL User auth.
> Windows 2003
> SQL 2000
> Any Ideas?

Reports Manager 400 Bad Request

Here is the problem I am having. I have 2 instances of SQL Server setup on
one machine. Both with Reporting Services installed. I am running SQL
Server 2005 build 2153 for both, on Windows Server 2003 Enterprise. I have
IIS setup correctly. I went through and configured each so that everything
has a green checkmark next to it, with the exception of encryption. Now
everytime I try to bring up the reports either locally or remotely. It
brings up the page and with a 400 error. I have tried the following
server2/reports(instancename), server2.mastro.local/reports(instancename),
and 192.168.0.2/reports(instancename). Does anyone know how to get rid of
this 400 error?
Michael R. Mastro IIGot it fixed.
"Michael Mastro" <MikeRM2XXX@.worldnet.att.net> wrote in message
news:e9YR1RRUHHA.1364@.TK2MSFTNGP06.phx.gbl...
> Here is the problem I am having. I have 2 instances of SQL Server setup
> on one machine. Both with Reporting Services installed. I am running SQL
> Server 2005 build 2153 for both, on Windows Server 2003 Enterprise. I
> have IIS setup correctly. I went through and configured each so that
> everything has a green checkmark next to it, with the exception of
> encryption. Now everytime I try to bring up the reports either locally or
> remotely. It brings up the page and with a 400 error. I have tried the
> following server2/reports(instancename),
> server2.mastro.local/reports(instancename), and
> 192.168.0.2/reports(instancename). Does anyone know how to get rid of
> this 400 error?
> Michael R. Mastro II
>

Reports for Multiple SQL Databases

I would like to setup a Report server... so it can be used as the primary
reporting server for the SQL databases in our environment.
I've installed Windows 2003 Standard Edition, all necessary IIS components,
SQL 2000 (with SP3), Reporting Services (with SP1).
I used a domain account instead of the local service account (perhaps this
was a mistake?).
I can run reports from the AdventureWorks database without incident (since
it is on the same server).
When I try to run a report that references a database on another server... I
either get permission errors or Null SQL user errors.
I suppose this is the standard double-hop authentication issue...
Is there any documentation somebody can point me to that discussing setting
up a reporting server in an environment like this?It seems to me that you are seeing an issue with credentials for the data
source. IYour reports can either have the data source embedded in the report
or the report can reference a shared data source. I recommend using shared
record sources. Look at the credentials of the recordsource. I would not use
integrated but instead use the credentials stored securely in the report
server. I prefer to use a read only account. The advange of this is two
fold. One, you can make sure that only readonly access is allowed via your
reports and two that connection pooling can be fully taken advantage of.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rob Edwards" <RobEdwards@.Landam.com> wrote in message
news:O5GVWqE7EHA.2540@.TK2MSFTNGP09.phx.gbl...
> I would like to setup a Report server... so it can be used as the primary
> reporting server for the SQL databases in our environment.
> I've installed Windows 2003 Standard Edition, all necessary IIS
components,
> SQL 2000 (with SP3), Reporting Services (with SP1).
> I used a domain account instead of the local service account (perhaps this
> was a mistake?).
> I can run reports from the AdventureWorks database without incident (since
> it is on the same server).
> When I try to run a report that references a database on another server...
I
> either get permission errors or Null SQL user errors.
> I suppose this is the standard double-hop authentication issue...
> Is there any documentation somebody can point me to that discussing
setting
> up a reporting server in an environment like this?
>

Reports + Setup

Hi,

I need to create a setup project that will create a new folder in the Reports Server.

The folder should contain all the reports I have developed.

The folder should have a browse permission for a user that I will choose (from the Active Dir.).

Everything must be programaticlly. In other words, I need to create a folder and set the permissions for it using code.

Is there a way? Do you have something in mind?

10x,

Solved it using the followings:

for the folder creation part:

_service = new ReportingService2005();

_service.Credentials = System.Net.CredentialCache.DefaultCredentials;

_service.CreateFolder(directoryName, "/", null);

for the security part:

Role role = new Role();

role.Name = "Browser";

Policy policy = new Policy();

policy.Roles = new Role[] { role };

policy.GroupUserName = domain + @."\user";

_service.SetPolicies("/" + directoryName, new Policy[] { policy });

I hope this will help you guys..

reporting..

Great,
So basically, in a small networked office setup I described,I will:
1> Install myapp on all 4 machines
2> Install MSDE on the centralserver A
3> Connection string will point to the machine A for datasource
But what about:
1> If I need to start the sqlserver service on clients machine, for e.g. to backup/restore database. How will I do it. Currently I use the following code to create the service controller and then start it if needed:
svc = New ServiceController("MSSQL$MyInstanceName)
What will I do when the service is on the central machine. How to start the service using the above code.
(See my clients will not have a dba and are assumed to not know that there is anything related to sql server on their machines, so we are providing the UI for backup/restore etc and the db functionality is kept as hidden as possible from them, this UI wil
l be in the tools on my vb.net app)
2> Will I need to run any network config utilities on the client machine. I know I will have to set disablenetworkprotocols to false on the server, but is there anything related to network access to be done on the client.
3> Andrea sometime back you mentioned something like, the location to backup should be from the MSDE machine's point of view.. so if PC1 wants to backup the db on it's D:\Backup drive, then what change will I have to do to this code below(which works fine
for a machine which has msde installed)
'--
cn = New SqlConnection(mMasterConnString)
cn.Open()
Dim cm As New SqlCommand
With cm
.Connection = cn
.CommandType = CommandType.Text
.CommandText = "BACKUP DATABASE " & mDBName & " TO DISK = '" & bkpFileWithPath & "' WITH NAME = My Backup', INIT"
.ExecuteNonQuery()
End With
'Note: bkpFileWithPath argument is: "D:\Backup\MyDB.bak"
'---
4> I guess I will take DMO slowly..
Thanks a lot guys.
dev
hi dev_kh,
"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:FB209BF1-68B3-489C-A9E3-FD4CDDB6E87A@.microsoft.com...
> Great,
> So basically, in a small networked office setup I described,I will:
> 1> Install myapp on all 4 machines
> 2> Install MSDE on the centralserver A
> 3> Connection string will point to the machine A for datasource
yep =;-D

> But what about:
> 1> If I need to start the sqlserver service on clients machine, for e.g.
to
>backup/restore database. How will I do it. Currently I use the following
code to
>create the service controller and then start it if needed:
> svc = New ServiceController("MSSQL$MyInstanceName)
> What will I do when the service is on the central machine. How to start
the service
>using the above code.
usually the MSDE instance running on the remote server shoul'd be up and
running...
if you do have SQL-DMO [again =;-D ] you can try starting it, but the best
solution is making sure the MSDE instance starts at server startup...

> (See my clients will not have a dba and are assumed to not know that there
is
>anything related to sql server on their machines, so we are providing the
UI for
>backup/restore etc and the db functionality is kept as hidden as possible
from them,
>this UI will be in the tools on my vb.net app)
add a job script to make sure a dayly (?) backup operation is performed at
least..

> 2> Will I need to run any network config utilities on the client machine.
I know I will have
>to set disablenetworkprotocols to false on the server, but is there
anything related to network
>access to be done on the client.
usually not... but wait for WinXP sp2 and then he all will have a lot to do,
related to personal firewall settings =;-D ... and this is good, related to
secuirty concerns...

> 3> Andrea sometime back you mentioned something like, the location to
backup
>should be from the MSDE machine's point of view.. so if PC1 wants to backup
the
> db on it's D:\Backup drive, then what change will I have to do to this
code below(which
> works fine for a machine which has msde installed)
> '--
> cn = New SqlConnection(mMasterConnString)
> cn.Open()
> Dim cm As New SqlCommand
> With cm
> .Connection = cn
> .CommandType = CommandType.Text
> .CommandText = "BACKUP DATABASE " & mDBName & " TO DISK =
'" & bkpFileWithPath & "' WITH NAME = My Backup', INIT"
> .ExecuteNonQuery()
> End With
> 'Note: bkpFileWithPath argument is: "D:\Backup\MyDB.bak"
> '---
nothing...
>bkpFileWithPath argument is: "D:\Backup\MyDB.bak"
will actually point to server's file system... so the db wil be backed up on
server's d:\....

> 4> I guess I will take DMO slowly..
ROTFL
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
you mentioned:
"usually the MSDE instance running on the remote server shoul'd be up and
running...
if you do have SQL-DMO [again =;-D ] you can try starting it, but the best
solution is making sure the MSDE instance starts at server startup"
Do you mean making sure that the MSDE is set to startup automatically.. but I want to use the Start Service if needed. So when my app starts I want to see if the service is running, if not I want to start it.
So, on my machine I was using the following line:
svc = New ServiceController("MSSQL$MyInstanceName)
but now when the service is on the central machine then will anything change in the above line of code? I mean will I have to add the server's name/path somewhere in the above line.. after all the service is on the server...
Hope my question is clear now..
Thanks a lot
dev
|||hi dev
"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:CAF7632E-4D3E-4EF9-9B75-ADE8414C3632@.microsoft.com...[vbcol=seagreen]
> you mentioned:
best
> Do you mean making sure that the MSDE is set to startup automatically..
>but I want to use the Start Service if needed. So when my app starts I
want
> to see if the service is running, if not I want to start it.
> So, on my machine I was using the following line:
> svc = New ServiceController("MSSQL$MyInstanceName)
> but now when the service is on the central machine then will anything
change
>in the above line of code? I mean will I have to add the server's
name/path
>somewhere in the above line.. after all the service is on the server...
> Hope my question is clear now..
if you are using WMI, you will actually invoke SQL-DMO behind the scenes, so
just directly rely on DMO...
so you have to try a connection, possiblyy with low timeout in order not to
wait to much, and eventaully start the server if needed...
but, again, you shoul'd rely on autostart service method whenever
possible...
make it simple =;-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You said "if you are using WMI, you will actually invoke SQL-DMO behind the scenes, so just directly rely on DMO... so you have to try a connection, possiblyy with low timeout in order not to wait to much, and eventaully start the server if needed... but,
again, you shoul'd rely on autostart service method whenever
possible... make it simple =;-D"
But this code works fine without wmi or dmo on my machine which has msde.. and if I don't want to use dmo, just simply start the service on the server from the client's machine.. then will I need to add some server name etc on this line of code...
thanks
dev

Reporting Sevices Setup/server question

I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
comleted the set up and when I go to http://Localhost\Report server I get the
attached error message. I also tried to upgrade the SQL DB on the SQL
reporting Database Serup and I received a warning message there that said
"Verifying Database Version . The current connection string is not valid
and can't be user to connect to SQL server."
Does anyone have any ideas ?
Reporting Services 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.43'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase) Get Online
HelpI guess you typed Report or Reports, it really matters, because it creates a
vitual directory with name as "Reports" so be specific.
Amarnath
"armela" wrote:
> I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
> comleted the set up and when I go to http://Localhost\Report server I get the
> attached error message. I also tried to upgrade the SQL DB on the SQL
> reporting Database Serup and I received a warning message there that said
> "Verifying Database Version . The current connection string is not valid
> and can't be user to connect to SQL server."
> Does anyone have any ideas ?
>
> Reporting Services 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.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase) Get Online
> Help
>|||I'm having the same experience and I cannot read Amarnath's reply to armela.
--
jl
"armela" wrote:
> I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
> comleted the set up and when I go to http://Localhost\Report server I get the
> attached error message. I also tried to upgrade the SQL DB on the SQL
> reporting Database Serup and I received a warning message there that said
> "Verifying Database Version . The current connection string is not valid
> and can't be user to connect to SQL server."
> Does anyone have any ideas ?
>
> Reporting Services 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.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase) Get Online
> Help
>|||BTW, my server is an IA-64 Windows 2003 EE SP1, SQL 2005 EE SP1. SQL 2005 is
a new install. RS was installed after IIS had been installed but not before
ASP.NET was installed. At this point the RS Configuration Manager shows all
green (except for the encryption key which has not been set).
--
jl
"armela" wrote:
> I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
> comleted the set up and when I go to http://Localhost\Report server I get the
> attached error message. I also tried to upgrade the SQL DB on the SQL
> reporting Database Serup and I received a warning message there that said
> "Verifying Database Version . The current connection string is not valid
> and can't be user to connect to SQL server."
> Does anyone have any ideas ?
>
> Reporting Services 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.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase) Get Online
> Help
>|||You should check with "http://localhost/reports" and not just "report", it
has different meaning. This is the way you need to check whether your RS is
installed properly.
Amarnath
"John L" wrote:
> BTW, my server is an IA-64 Windows 2003 EE SP1, SQL 2005 EE SP1. SQL 2005 is
> a new install. RS was installed after IIS had been installed but not before
> ASP.NET was installed. At this point the RS Configuration Manager shows all
> green (except for the encryption key which has not been set).
> --
> jl
>
> "armela" wrote:
> > I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
> > comleted the set up and when I go to http://Localhost\Report server I get the
> > attached error message. I also tried to upgrade the SQL DB on the SQL
> > reporting Database Serup and I received a warning message there that said
> > "Verifying Database Version . The current connection string is not valid
> > and can't be user to connect to SQL server."
> >
> > Does anyone have any ideas ?
> >
> >
> > Reporting Services 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.43'. To continue, update the version of the report server
> > database and verify access rights. (rsInvalidReportServerDatabase) Get Online
> > Help
> >
> >|||I specified reports and cannot get RS working.
--
jl
"Amarnath" wrote:
> You should check with "http://localhost/reports" and not just "report", it
> has different meaning. This is the way you need to check whether your RS is
> installed properly.
> Amarnath
> "John L" wrote:
> > BTW, my server is an IA-64 Windows 2003 EE SP1, SQL 2005 EE SP1. SQL 2005 is
> > a new install. RS was installed after IIS had been installed but not before
> > ASP.NET was installed. At this point the RS Configuration Manager shows all
> > green (except for the encryption key which has not been set).
> >
> > --
> > jl
> >
> >
> > "armela" wrote:
> >
> > > I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
> > > comleted the set up and when I go to http://Localhost\Report server I get the
> > > attached error message. I also tried to upgrade the SQL DB on the SQL
> > > reporting Database Serup and I received a warning message there that said
> > > "Verifying Database Version . The current connection string is not valid
> > > and can't be user to connect to SQL server."
> > >
> > > Does anyone have any ideas ?
> > >
> > >
> > > Reporting Services 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.43'. To continue, update the version of the report server
> > > database and verify access rights. (rsInvalidReportServerDatabase) Get Online
> > > Help
> > >
> > >|||Sorry you need to reinstall because it is not installed properly. This is
what MS recommends to check the correctness of installation.
Amarnath
"John L" wrote:
> I specified reports and cannot get RS working.
> --
> jl
>
> "Amarnath" wrote:
> > You should check with "http://localhost/reports" and not just "report", it
> > has different meaning. This is the way you need to check whether your RS is
> > installed properly.
> >
> > Amarnath
> >
> > "John L" wrote:
> >
> > > BTW, my server is an IA-64 Windows 2003 EE SP1, SQL 2005 EE SP1. SQL 2005 is
> > > a new install. RS was installed after IIS had been installed but not before
> > > ASP.NET was installed. At this point the RS Configuration Manager shows all
> > > green (except for the encryption key which has not been set).
> > >
> > > --
> > > jl
> > >
> > >
> > > "armela" wrote:
> > >
> > > > I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
> > > > comleted the set up and when I go to http://Localhost\Report server I get the
> > > > attached error message. I also tried to upgrade the SQL DB on the SQL
> > > > reporting Database Serup and I received a warning message there that said
> > > > "Verifying Database Version . The current connection string is not valid
> > > > and can't be user to connect to SQL server."
> > > >
> > > > Does anyone have any ideas ?
> > > >
> > > >
> > > > Reporting Services 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.43'. To continue, update the version of the report server
> > > > database and verify access rights. (rsInvalidReportServerDatabase) Get Online
> > > > Help
> > > >
> > > >|||I finally uninstalled SQL 2005 and .NetFramework 2.0 and reinstalled.
Configuration worked and RS is running. Did have an issue with the account
running ASP.Net and had to change that (using inetmgr!).
--
jl
"Amarnath" wrote:
> Sorry you need to reinstall because it is not installed properly. This is
> what MS recommends to check the correctness of installation.
> Amarnath
> "John L" wrote:
> > I specified reports and cannot get RS working.
> >
> > --
> > jl
> >
> >
> > "Amarnath" wrote:
> >
> > > You should check with "http://localhost/reports" and not just "report", it
> > > has different meaning. This is the way you need to check whether your RS is
> > > installed properly.
> > >
> > > Amarnath
> > >
> > > "John L" wrote:
> > >
> > > > BTW, my server is an IA-64 Windows 2003 EE SP1, SQL 2005 EE SP1. SQL 2005 is
> > > > a new install. RS was installed after IIS had been installed but not before
> > > > ASP.NET was installed. At this point the RS Configuration Manager shows all
> > > > green (except for the encryption key which has not been set).
> > > >
> > > > --
> > > > jl
> > > >
> > > >
> > > > "armela" wrote:
> > > >
> > > > > I installed SQL Reporting Services 2005 SP1 and eveything looks fine. I
> > > > > comleted the set up and when I go to http://Localhost\Report server I get the
> > > > > attached error message. I also tried to upgrade the SQL DB on the SQL
> > > > > reporting Database Serup and I received a warning message there that said
> > > > > "Verifying Database Version . The current connection string is not valid
> > > > > and can't be user to connect to SQL server."
> > > > >
> > > > > Does anyone have any ideas ?
> > > > >
> > > > >
> > > > > Reporting Services 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.43'. To continue, update the version of the report server
> > > > > database and verify access rights. (rsInvalidReportServerDatabase) Get Online
> > > > > Help
> > > > >
> > > > >