Reporting Services 2005 using Analysis Services 2000 as a datasource

Has anyone tried this and if so what degree of success have you had.
I've tried with both April and June CTP and cannot get anything of any
use to return. This begs the question, is the only way to get data from
SSAS 2000 into reporting services is to use a flattened dataset through
OLEDB.
In fact any information regarding registering, querying or browsing
2000 servers with the 2005 tools would be useful.
Thanks
SteveI've answered my own question, the answer is a big fat dissapointing
"no".

Reporting Service's 2005 upgrade issue

We have completed the Reporting Service's 2005 upgrade (sept ctp) and have
been testing some of the reports. We are finding reports that work just find
on 2000 (our prod. box) are not working properly in 2005. Is anyone else
having any issues? I will try to explain one of the scenarios in which we
have encountered issues:
Ok. The report has two date dropdowns and three other string dropdowns. The
dates are defaulted but the others are not. One of the three other dropdowns
are greyed out until the other two are selected first. The problem is when we
select either of the first two dropdowns, it displays an error page stating
"Value cannot be null. Parameter name: value ". The 2000 version works
correctly.
Any help is appreciated!It sounds like you run into a known issue with datatime parameters in
combination with multi-value parameters when running them in report manager.
The error happens with CTP September. It is fixed in the final RTM release
of SQL Server 2005.
You should basically just take again a backup of your RS 2000 production
server, and then run the upgrade with the SQL Server 2005 RTM release once
it is available.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"clutch" <clutch@.discussions.microsoft.com> wrote in message
news:0A495BC3-1FAE-403B-BF93-156B89C8913F@.microsoft.com...
> We have completed the Reporting Service's 2005 upgrade (sept ctp) and
> have
> been testing some of the reports. We are finding reports that work just
> find
> on 2000 (our prod. box) are not working properly in 2005. Is anyone else
> having any issues? I will try to explain one of the scenarios in which we
> have encountered issues:
> Ok. The report has two date dropdowns and three other string dropdowns.
> The
> dates are defaulted but the others are not. One of the three other
> dropdowns
> are greyed out until the other two are selected first. The problem is when
> we
> select either of the first two dropdowns, it displays an error page
> stating
> "Value cannot be null. Parameter name: value ". The 2000 version works
> correctly.
> Any help is appreciated!|||Thank you Robert!
"Robert Bruckner [MSFT]" wrote:
> It sounds like you run into a known issue with datatime parameters in
> combination with multi-value parameters when running them in report manager.
> The error happens with CTP September. It is fixed in the final RTM release
> of SQL Server 2005.
> You should basically just take again a backup of your RS 2000 production
> server, and then run the upgrade with the SQL Server 2005 RTM release once
> it is available.
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> news:0A495BC3-1FAE-403B-BF93-156B89C8913F@.microsoft.com...
> > We have completed the Reporting Service's 2005 upgrade (sept ctp) and
> > have
> > been testing some of the reports. We are finding reports that work just
> > find
> > on 2000 (our prod. box) are not working properly in 2005. Is anyone else
> > having any issues? I will try to explain one of the scenarios in which we
> > have encountered issues:
> >
> > Ok. The report has two date dropdowns and three other string dropdowns.
> > The
> > dates are defaulted but the others are not. One of the three other
> > dropdowns
> > are greyed out until the other two are selected first. The problem is when
> > we
> > select either of the first two dropdowns, it displays an error page
> > stating
> > "Value cannot be null. Parameter name: value ". The 2000 version works
> > correctly.
> >
> > Any help is appreciated!
>
>

reporting services 2005 (CTP) and Oracle

I can't create a connection for Oracle (any version). Is this a CTP issue ?Since SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us
--
--Brian
(Please reply to the newsgroups only.)
"pn2kt" <pn2kt@.discussions.microsoft.com> wrote in message
news:67DE088B-35C9-4983-992D-19CEA9FBF6EB@.microsoft.com...
>I can't create a connection for Oracle (any version). Is this a CTP issue ?

Reporting Server 2005 Login issues

Have SQL Server 2005 September CTP
I am Local admin on box
Sysadmin in SQL Server
Installed reporting server. I used the BI Development Suite (VS) to build
reports. I ran the build with no issues than deployed the reports to the
server successfully. I can log in and view the reports from IE on the server
itself. They show up fine. The security is set to windows in reporting
server. When I attempt to view the report from my workstation I get the
following error:
An error has occurred during report processing.
Cannot impersonate user for data source 'RemoteConnection'.
Logon failed.
For more information about this error navigate to the report server on the
local server machine, or enable remote errors
Again SQL Server 2005 Sept CTP. Any help would really be appreciated.In Report Manager, select the data source you are using in your
report. In the General tab you should see information about
credentials and other connection informaton relevant to the data
source. Have a careful look at all aspects of that, as a first step.
Andrew Watt
MVP - InfoPath
On Fri, 7 Oct 2005 10:07:04 -0700, "T Man"
<TMan@.discussions.microsoft.com> wrote:
>Have SQL Server 2005 September CTP
>I am Local admin on box
>Sysadmin in SQL Server
>Installed reporting server. I used the BI Development Suite (VS) to build
>reports. I ran the build with no issues than deployed the reports to the
>server successfully. I can log in and view the reports from IE on the server
>itself. They show up fine. The security is set to windows in reporting
>server. When I attempt to view the report from my workstation I get the
>following error:
>An error has occurred during report processing.
>Cannot impersonate user for data source 'RemoteConnection'.
>Logon failed.
>For more information about this error navigate to the report server on the
>local server machine, or enable remote errors
>
>Again SQL Server 2005 Sept CTP. Any help would really be appreciated.