Report connect to AS cube

I cannot get my report to connect to my datacube. I've got RS running on a
web server and Analysis Services running on another server. The two servers
have an established relationship as i am currently able to run RS reports
against the SQL Server relational db's that exist on the server that is
running AS.
When i try to execute a report against a cube i get "cannot connect to the
server {myserver}. the server is either too busy or not started".
The connection string i am using is:
Provider=MSOLAP.2;Client Cache Size=25;Data Source={myserver};Auto Synch
Period=10000;Initial Catalog={mycatalog}
This all works fine in my dev environment where AS and RS run on the same
server.
What extra step am i missing to get my RS Web server to talk to my AS DB
server?
Thanks for any info.Sorry i do not know the answer for your question. But i am facing one
problem.I am unable to get the query designer, to type the MDX query to get
reports from my analysis server. I am using the Analysis server and web
server on the same machine.
When i am trying to create the report using SQL server relational db, i
am able to get the query designer. Please help me..
Dhar.
"JeffW" wrote:
> I cannot get my report to connect to my datacube. I've got RS running on a
> web server and Analysis Services running on another server. The two servers
> have an established relationship as i am currently able to run RS reports
> against the SQL Server relational db's that exist on the server that is
> running AS.
> When i try to execute a report against a cube i get "cannot connect to the
> server {myserver}. the server is either too busy or not started".
> The connection string i am using is:
> Provider=MSOLAP.2;Client Cache Size=25;Data Source={myserver};Auto Synch
> Period=10000;Initial Catalog={mycatalog}
> This all works fine in my dev environment where AS and RS run on the same
> server.
> What extra step am i missing to get my RS Web server to talk to my AS DB
> server?
> Thanks for any info.
>|||Dahr:
I was able to solve my problem. Turns out, port 2725 was not open between
my web and db servers. once i opened up that port everything runs fine.
As for your issue, if you are running version 1 of RS with sp1, it does not
support an mdx query designer. i believe that capability is scheduled for
the next release of Reporting services. For now, you just have to type the
mdx in, or use another mdx builder to get the query you need, and then
copy/paste it into rs.
Hope that helps.
JeffW
"Dhar" wrote:
> Sorry i do not know the answer for your question. But i am facing one
> problem.I am unable to get the query designer, to type the MDX query to get
> reports from my analysis server. I am using the Analysis server and web
> server on the same machine.
> When i am trying to create the report using SQL server relational db, i
> am able to get the query designer. Please help me..
>
> Dhar.
>
> "JeffW" wrote:
> > I cannot get my report to connect to my datacube. I've got RS running on a
> > web server and Analysis Services running on another server. The two servers
> > have an established relationship as i am currently able to run RS reports
> > against the SQL Server relational db's that exist on the server that is
> > running AS.
> >
> > When i try to execute a report against a cube i get "cannot connect to the
> > server {myserver}. the server is either too busy or not started".
> >
> > The connection string i am using is:
> > Provider=MSOLAP.2;Client Cache Size=25;Data Source={myserver};Auto Synch
> > Period=10000;Initial Catalog={mycatalog}
> >
> > This all works fine in my dev environment where AS and RS run on the same
> > server.
> >
> > What extra step am i missing to get my RS Web server to talk to my AS DB
> > server?
> >
> > Thanks for any info.
> >
> >

Report Builder, SSAS, and Many-to-Many Relationships

Does Report Builder handle many-to-many relationships within an SSAS cube correctly? I can't seem to get it to. Using Adventure Works, here's an example of the problem I'm seeing.

- Create a new report in RB, opening the Adventure Works DW model

- Select one of the perspectives that includes the Sales Reason dimension (like Direct Sales)

- Select the Sales Reason entity in the Entities list and put the Sales Reason Type attribute into the report (making Sales Reason the primary entity)

- The Entities list will be reduced to show the Adventure Works Sales Reasons relationship (which maps to that underlying measure group)

- If you select the Adventure Works Sales Reasons relationship, you’ll see the Internet Sales Order Details entity below it

- If you select the Sales Order Details entity, however, you’ll only see the attributes that are in that dimension; you won’t see any of the measures that exist in the measure groups that are related to it

- Based on that fact, you can’t get to any of the measures in the cube (since the Sales Reason dimension is related to the other measure groups only through M-to-M relationships)

Of course, it may be that I just don't understand how the auto-generated report model for the SSAS cube is exposing the relationships and the entities that correspond to the Sales Reason dimension, the Sales Reasons measure group (the intermediate measure group for the M-to-M relationships to the other measure groups), etc.

Anyone seen this before or know that this is defined behavior? Seems that for any SSAS cube that includes M-to-M relationships, Report Builder just won't work...

Thanks!

Dave Fackler

Unfortunately, the SMDL model in the Report Builder sometimes gets in the way when SSAS is used as a data source. To get around similar limitations, I added calculated members in the cube which mapped to the original measures and I assigned them to the first measure group. The net result is that all measures were mapped to only one measure group. Then, I had to manually change the SMDL model to hide the measure groups/measures I don't need.|||

Hi Teo,

I understand most of the limitations with RB against an SSAS-based SMDL model. However, I've never tested trying to build a report that includes dimensions/measure groups that are related via a many-to-many relationship. The fact that this doesn't seem to work is troubling, so I'm trying to confirm that it is indeed an issue (or bug?) with RB and not just me doing something silly... Have you ever tried to create a report using RB that hits the Sales Reason dimension in the AW cube? If not, give it a try and let me know what your experience is...

Thanks!

Dave F.

|||

The fact that this doesn't seem to work is troubling, so I'm trying to confirm that it is indeed an issue (or bug?) with RB and not just me doing something silly.

Not the latter for sure . M-M relationships is not the only case. The same thing happens if you have a multi-grain relationship, e.g. Sales Target in the Adventure Works. Then the model drops the Date relationship so you can't slice by date. I'd recommend you file a bug report with product services for all Report Builder issues that you encounter (I've done my fair share doing so). The more people complain about the SSAS integration scenario the more likely is to get fixed/improved. Meanwhile, consider opening the SMDL model and adding the dropped relationships manually. This isn't a supported scenario but it will probably get you going.

Report Builder, limiting the Dimensions

Hi,

I created a report model based over the cube. The problme is, it retrieves all dimensions from the cube regardless those are checked or not even in the prespective.

It does work with Measure but not with Dimensions.

Appreciate if some one can drop a line here and help me out.

Thank you

Imran

You need to make manual changes to the model for this to happen.

1. Create a new Report Builder project.

2. Save the auto-generated SMDL file from Report Manager.

3. Add it to the Report Builder project.

4. Open the model in the Model Designer and select the root Model node.

5. On the right pane, right-click on the perspective desired and choose Edit.

6. In the Edit Perspective dialog box, unselect all dimensions that you don't need.

7. When you are done, go back to the Report Manager and update the model (click the Update button).

HTH

|||

The model is generated from the cube... It is not over the relational database where I can create and edit prepectives.

Imran

|||

I understand your scenario. You can still make manual changes to a model generated from UDM by following the steps in my previous post.

|||

Ok...

I limit the Dimension as you mentioned but now I cann't generate the report... The reason is, somehow all the Dimensions need to be selected in the Model...else it is not going to work.... Updating the Model back to original state rectify the problem.

Any help?

Thank You

Imran

|||

Can you provide repro steps with the AdventureWorks cube and include a report definition of a Report Builder report that cannot be generated?

|||Report Builder models generated against an Analysis Services cube cannot be edited using Model Designer. Also, modifying the report-model (.smdl) file directly is not supported.

Source: http://msdn2.microsoft.com/en-us/library/aa964121.aspx

Even if try to modify the report builder model using other way, we canot get the achieved results.

--Imran

|||

I am well aware of the Report Builder-SSAS limitations and the fact that the modifying the report-model is not supported. However, when nothing else helps you don't have much choice unless you take the unsupported road, do you? You should be able to open the smdl file in a Report Builder project, make the changes I mentioned, and update the model back successfully. If something doesn't work, please let us know what it is and provide repro steps if possible.

Report Builder, limiting the Dimensions

Hi,

I created a report model based over the cube. The problme is, it retrieves all dimensions from the cube regardless those are checked or not even in the prespective.

It does work with Measure but not with Dimensions.

Appreciate if some one can drop a line here and help me out.

Thank you

Imran

You need to make manual changes to the model for this to happen.

1. Create a new Report Builder project.

2. Save the auto-generated SMDL file from Report Manager.

3. Add it to the Report Builder project.

4. Open the model in the Model Designer and select the root Model node.

5. On the right pane, right-click on the perspective desired and choose Edit.

6. In the Edit Perspective dialog box, unselect all dimensions that you don't need.

7. When you are done, go back to the Report Manager and update the model (click the Update button).

HTH

|||

The model is generated from the cube... It is not over the relational database where I can create and edit prepectives.

Imran

|||

I understand your scenario. You can still make manual changes to a model generated from UDM by following the steps in my previous post.

|||

Ok...

I limit the Dimension as you mentioned but now I cann't generate the report... The reason is, somehow all the Dimensions need to be selected in the Model...else it is not going to work.... Updating the Model back to original state rectify the problem.

Any help?

Thank You

Imran

|||

Can you provide repro steps with the AdventureWorks cube and include a report definition of a Report Builder report that cannot be generated?

|||Report Builder models generated against an Analysis Services cube cannot be edited using Model Designer. Also, modifying the report-model (.smdl) file directly is not supported.

Source: http://msdn2.microsoft.com/en-us/library/aa964121.aspx

Even if try to modify the report builder model using other way, we canot get the achieved results.

--Imran

|||

I am well aware of the Report Builder-SSAS limitations and the fact that the modifying the report-model is not supported. However, when nothing else helps you don't have much choice unless you take the unsupported road, do you? You should be able to open the smdl file in a Report Builder project, make the changes I mentioned, and update the model back successfully. If something doesn't work, please let us know what it is and provide repro steps if possible.

Report Builder, limiting the Dimensions

Hi,

I created a report model based over the cube. The problme is, it retrieves all dimensions from the cube regardless those are checked or not even in the prespective.

It does work with Measure but not with Dimensions.

Appreciate if some one can drop a line here and help me out.

Thank you

Imran

You need to make manual changes to the model for this to happen.

1. Create a new Report Builder project.

2. Save the auto-generated SMDL file from Report Manager.

3. Add it to the Report Builder project.

4. Open the model in the Model Designer and select the root Model node.

5. On the right pane, right-click on the perspective desired and choose Edit.

6. In the Edit Perspective dialog box, unselect all dimensions that you don't need.

7. When you are done, go back to the Report Manager and update the model (click the Update button).

HTH

|||

The model is generated from the cube... It is not over the relational database where I can create and edit prepectives.

Imran

|||

I understand your scenario. You can still make manual changes to a model generated from UDM by following the steps in my previous post.

|||

Ok...

I limit the Dimension as you mentioned but now I cann't generate the report... The reason is, somehow all the Dimensions need to be selected in the Model...else it is not going to work.... Updating the Model back to original state rectify the problem.

Any help?

Thank You

Imran

|||

Can you provide repro steps with the AdventureWorks cube and include a report definition of a Report Builder report that cannot be generated?

|||Report Builder models generated against an Analysis Services cube cannot be edited using Model Designer. Also, modifying the report-model (.smdl) file directly is not supported.

Source: http://msdn2.microsoft.com/en-us/library/aa964121.aspx

Even if try to modify the report builder model using other way, we canot get the achieved results.

--Imran

|||

I am well aware of the Report Builder-SSAS limitations and the fact that the modifying the report-model is not supported. However, when nothing else helps you don't have much choice unless you take the unsupported road, do you? You should be able to open the smdl file in a Report Builder project, make the changes I mentioned, and update the model back successfully. If something doesn't work, please let us know what it is and provide repro steps if possible.

sql

Report Builder, limiting the Dimensions

Hi,

I created a report model based over the cube. The problme is, it retrieves all dimensions from the cube regardless those are checked or not even in the prespective.

It does work with Measure but not with Dimensions.

Appreciate if some one can drop a line here and help me out.

Thank you

Imran

You need to make manual changes to the model for this to happen.

1. Create a new Report Builder project.

2. Save the auto-generated SMDL file from Report Manager.

3. Add it to the Report Builder project.

4. Open the model in the Model Designer and select the root Model node.

5. On the right pane, right-click on the perspective desired and choose Edit.

6. In the Edit Perspective dialog box, unselect all dimensions that you don't need.

7. When you are done, go back to the Report Manager and update the model (click the Update button).

HTH

|||

The model is generated from the cube... It is not over the relational database where I can create and edit prepectives.

Imran

|||

I understand your scenario. You can still make manual changes to a model generated from UDM by following the steps in my previous post.

|||

Ok...

I limit the Dimension as you mentioned but now I cann't generate the report... The reason is, somehow all the Dimensions need to be selected in the Model...else it is not going to work.... Updating the Model back to original state rectify the problem.

Any help?

Thank You

Imran

|||

Can you provide repro steps with the AdventureWorks cube and include a report definition of a Report Builder report that cannot be generated?

|||Report Builder models generated against an Analysis Services cube cannot be edited using Model Designer. Also, modifying the report-model (.smdl) file directly is not supported.

Source: http://msdn2.microsoft.com/en-us/library/aa964121.aspx

Even if try to modify the report builder model using other way, we canot get the achieved results.

--Imran

|||

I am well aware of the Report Builder-SSAS limitations and the fact that the modifying the report-model is not supported. However, when nothing else helps you don't have much choice unless you take the unsupported road, do you? You should be able to open the smdl file in a Report Builder project, make the changes I mentioned, and update the model back successfully. If something doesn't work, please let us know what it is and provide repro steps if possible.

Report Builder Query

Hi Experts,

I have a report model on top of a cube. I have a calculated metrics called Policy Count and different amounts in cube.

When i try to create report in report builder with Policy count, amounts and different dimensional attributes it doesnt work.

The problem is report builder allows me to select either Policy count in the report or the amount field.

Have anyone faced this problem.

The same report works in cube browser.

Regards'

Neeraj

Make sure your calculated and non-calculated measures are housed in the same measure group folder. To move the calcualted measure to a measure group's folder, go to the Calculations tab in the Cube Designer. There is a Properties button in the toolbar which will allow you to choose the calculated member and which measure group to associate it with. (Don't set the display folder.) Deploy your cube and rebuild your Report Model off the DSV.

B.

Report Builder Query

Hi Experts,

I have a report model on top of a cube. I have a calculated metrics called Policy Count and different amounts in cube.

When i try to create report in report builder with Policy count, amounts and different dimensional attributes it doesnt work.

The problem is report builder allows me to select either Policy count in the report or the amount field.

Have anyone faced this problem.

The same report works in cube browser.

Regards'

Neeraj

Make sure your calculated and non-calculated measures are housed in the same measure group folder. To move the calcualted measure to a measure group's folder, go to the Calculations tab in the Cube Designer. There is a Properties button in the toolbar which will allow you to choose the calculated member and which measure group to associate it with. (Don't set the display folder.) Deploy your cube and rebuild your Report Model off the DSV.

B.

Report Builder problem with no All level on Scenario?

At first glance, this appears to be a bug in Reporting Services...
I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
set IsAggregatable to False (since it doesn't make sense to add Actuals and
Budgets). This effectively removes the All level, as I understand it. I've
set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
datasource in SSRS and generate a model off it. When I build a Report Builder
report off the model, I have a problem. If the report does not specify
scenario as a row, column, or filter, then the MDX that gets generated
(captured this via Profiler) starts...
WITH
MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
And since [Agg_0] is used in the body of the query inside an Exists()
function, it results in the query returning no cells (so the report says that
no data was returned). This may be a problem with the engine that translates
a model query into MDX. For some reason it's not paying attention to the
DefaultMember. (That's why I posted to this newsgroup, not the SSAS
newsgroup.)
When I flip IsAggregatable back to True such that there's an All level,
everything works fine. It gives me the correct numbers. But I don't want to
show an All level for the Scenario dimension.
Please let me know if you have any suggestions or if you can confirm this is
a bug. And please let me know if the SSRS guys feel this is an SSAS issue
that should be posted in that newsgroup.
(As a side note, though I get the right numbers by turning IsAggregatable to
True, I think the MDX is still not quite right because it references
[Scenario].[Scenario].[All] in the Exists function when it really should be
referencing [Scenario].CurrentMember. But that's another topic and not nearly
as crucial. The worst that could happen there is that you show some unneeded
rows. And I may be wrong on whether it should use CurrentMember.)"FurmanGG" wrote:
> At first glance, this appears to be a bug in Reporting Services...
> I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
> set IsAggregatable to False (since it doesn't make sense to add Actuals and
> Budgets). This effectively removes the All level, as I understand it. I've
> set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
> datasource in SSRS and generate a model off it. When I build a Report Builder
> report off the model, I have a problem. If the report does not specify
> scenario as a row, column, or filter, then the MDX that gets generated
> (captured this via Profiler) starts...
> WITH
> MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
> SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
> And since [Agg_0] is used in the body of the query inside an Exists()
> function, it results in the query returning no cells (so the report says that
> no data was returned). This may be a problem with the engine that translates
> a model query into MDX. For some reason it's not paying attention to the
> DefaultMember. (That's why I posted to this newsgroup, not the SSAS
> newsgroup.)
> When I flip IsAggregatable back to True such that there's an All level,
> everything works fine. It gives me the correct numbers. But I don't want to
> show an All level for the Scenario dimension.
> Please let me know if you have any suggestions or if you can confirm this is
> a bug. And please let me know if the SSRS guys feel this is an SSAS issue
> that should be posted in that newsgroup.
> (As a side note, though I get the right numbers by turning IsAggregatable to
> True, I think the MDX is still not quite right because it references
> [Scenario].[Scenario].[All] in the Exists function when it really should be
> referencing [Scenario].CurrentMember. But that's another topic and not nearly
> as crucial. The worst that could happen there is that you show some unneeded
> rows. And I may be wrong on whether it should use CurrentMember.)|||Hello,
Did you get any response to this problem or find any solution? I have about
the same problem; I am building an OLAP cube with a time dimension and stock
number. Those stock figures cannot be aggregated over time, so I set the
IsAggregatable option on the time dimension to False. When I do that, Report
Builder does not work as I would expect...
Thanks, Hans.
"FurmanGG" wrote:
> At first glance, this appears to be a bug in Reporting Services...
> I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
> set IsAggregatable to False (since it doesn't make sense to add Actuals and
> Budgets). This effectively removes the All level, as I understand it. I've
> set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
> datasource in SSRS and generate a model off it. When I build a Report Builder
> report off the model, I have a problem. If the report does not specify
> scenario as a row, column, or filter, then the MDX that gets generated
> (captured this via Profiler) starts...
> WITH
> MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
> SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
> And since [Agg_0] is used in the body of the query inside an Exists()
> function, it results in the query returning no cells (so the report says that
> no data was returned). This may be a problem with the engine that translates
> a model query into MDX. For some reason it's not paying attention to the
> DefaultMember. (That's why I posted to this newsgroup, not the SSAS
> newsgroup.)
> When I flip IsAggregatable back to True such that there's an All level,
> everything works fine. It gives me the correct numbers. But I don't want to
> show an All level for the Scenario dimension.
> Please let me know if you have any suggestions or if you can confirm this is
> a bug. And please let me know if the SSRS guys feel this is an SSAS issue
> that should be posted in that newsgroup.
> (As a side note, though I get the right numbers by turning IsAggregatable to
> True, I think the MDX is still not quite right because it references
> [Scenario].[Scenario].[All] in the Exists function when it really should be
> referencing [Scenario].CurrentMember. But that's another topic and not nearly
> as crucial. The worst that could happen there is that you show some unneeded
> rows. And I may be wrong on whether it should use CurrentMember.)|||Should be fixed in SP1...
http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=77da7b11-f20a-41ee-a18a-a74fd5ac4650
"Hans Geurtsen" wrote:
> Hello,
> Did you get any response to this problem or find any solution? I have about
> the same problem; I am building an OLAP cube with a time dimension and stock
> number. Those stock figures cannot be aggregated over time, so I set the
> IsAggregatable option on the time dimension to False. When I do that, Report
> Builder does not work as I would expect...
> Thanks, Hans.
> "FurmanGG" wrote:
> > At first glance, this appears to be a bug in Reporting Services...
> >
> > I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
> > set IsAggregatable to False (since it doesn't make sense to add Actuals and
> > Budgets). This effectively removes the All level, as I understand it. I've
> > set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
> > datasource in SSRS and generate a model off it. When I build a Report Builder
> > report off the model, I have a problem. If the report does not specify
> > scenario as a row, column, or filter, then the MDX that gets generated
> > (captured this via Profiler) starts...
> >
> > WITH
> > MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
> > SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
> >
> > And since [Agg_0] is used in the body of the query inside an Exists()
> > function, it results in the query returning no cells (so the report says that
> > no data was returned). This may be a problem with the engine that translates
> > a model query into MDX. For some reason it's not paying attention to the
> > DefaultMember. (That's why I posted to this newsgroup, not the SSAS
> > newsgroup.)
> >
> > When I flip IsAggregatable back to True such that there's an All level,
> > everything works fine. It gives me the correct numbers. But I don't want to
> > show an All level for the Scenario dimension.
> >
> > Please let me know if you have any suggestions or if you can confirm this is
> > a bug. And please let me know if the SSRS guys feel this is an SSAS issue
> > that should be posted in that newsgroup.
> >
> > (As a side note, though I get the right numbers by turning IsAggregatable to
> > True, I think the MDX is still not quite right because it references
> > [Scenario].[Scenario].[All] in the Exists function when it really should be
> > referencing [Scenario].CurrentMember. But that's another topic and not nearly
> > as crucial. The worst that could happen there is that you show some unneeded
> > rows. And I may be wrong on whether it should use CurrentMember.)

Report Builder MDX on filter

Please interpret this MDX statement generated by Report Builder for me. I am not sure why it is returning all years in cube when I just want 2005:

SELECT

{ ( Extract( filter( { [Accounting Date].[MDY Date].Levels(1).Members * { [Accounting Date].[Date].[Calendar] } }, ( ( [Accounting Date].[MDY Date].CurrentMember.membervalue >= "09/01/2005" ) AND ( [Accounting Date].[MDY Date].CurrentMember.membervalue <= "09/30/2005" ) ) ), [Accounting Date].[MDY Date] ) , * ) } on 0

FROM

[Cube]

It is filtering the data on the month and day portion of the date range just fine, just not filtering on the year. Same report in Reporting Services generates different MDX and returns 2005 only, so this rules out cube problem.

Could you please add CDate() around the begin and end dates, so as comparisons are made using the proper time ordering?

For instance:

... >= CDate("09/01/2005") ...

Report Builder Filter drop down list - when the list is more than 500 values

Hi All,

I build a model (either from Cube or from tables) and open it in report builder. When I select a FIELTER on field which has few distinct values like state code, I get a drop down list. But when I select a filter on 'Dept Name', the drop down list on filter disapears. I have to manually key the filter value.

Can any one help me in getting a drop down list on filter, when distinct values in that column are more than few hundred.

Regards

Bobba

This is controlled by a property InstanceSelection, that can be set on each attribute of a dimension (within the dimension Editor).

The cube/dimension wizard initially sets this property, but then it can be changed as required.

Report Builder Cube deploys to the wrong location!!

I have built a cube successfully however, it deploys succcessfully but to the wrong location. I have MSSQL.1, MSSQL.2 and MSSQL.3 and I Reporting Services in is MSSQL.3 but the cube is deploying to MSSQL.2/OLAP and I can't access it from there. I have tried changing the server name and specifiying the server/instance but it fails. I'm at my wits end! HELP!

Debra

The directories you've outlined are all correct and the cube has deployed to the correct location. With all components installed the locations should be as follows:

MSSQL - SQL 2000 Database Engine|||I am trying to access it by clicking on "report builder" from the reports webpage http://localhost/reports. Instead of seeing the cube in the selection box, there is a message saying therre are no cubes available and that in order to use report builder at least one cube must be published to the report server. Again, I am able to "successfully" deploy (using either localhost or my server name) but for some reason report builder can't "see" it. Are there some setting I need to modify for report builder?|||

Report builder does not connect directly to a cube. It connects to a Report Model which is different.

Once you've created a cube you first need to create a data source to point to that cube. you can do this by clicking the "New Data Source" button on the toolbar in report manager. Give it a name, select "Microsoft Analysis Services" as the connection type and put something like

Initial Catalog=Adventure Works DW;Data Source=<server>[\<instance>];

in the connection string box. Once you click ok to create the data source go to the properties page of the data source and click the "Generate Model" button. Once you've created the default model you'll be able to launch report builder and access the cube using the model.

Report models can also be created an modified using the BI development studio.

Report Builder Connection Error

Okay, here is the scenario. I have an analysis services cube and a report
model generated from a OLAP datasource in reporting services. My first
problem is that when I try to create a report using the report builder from
my local pc I get data source connection errors, but if I remote desktop into
the dev server where reporting services is installed an complete the same
procedure everything works great. My second problem is that I cannot create
a report model from an OLAP datasource unless I am remoted into the report
server.
Thanks, Andrewwhen you create report model, you need to use default in your data source
properties, so that it takes the same and connects.
second problem is: have you deployed your report model, only then you can
see the entities and then you can create the reports.
Amarnath
"chabotwvu" wrote:
> Okay, here is the scenario. I have an analysis services cube and a report
> model generated from a OLAP datasource in reporting services. My first
> problem is that when I try to create a report using the report builder from
> my local pc I get data source connection errors, but if I remote desktop into
> the dev server where reporting services is installed an complete the same
> procedure everything works great. My second problem is that I cannot create
> a report model from an OLAP datasource unless I am remoted into the report
> server.
> Thanks, Andrew|||When I navigate to my OLAP datasource using SQL Server Management Studio and
generate the model my datasource security is set to windows integrated
security. The OLAP datasource impersonation information is set to use the
service account; when I do this from SSMS on my local laptop I get connection
errors, but if I remote desktop into the reporting services server and
connect to reporting services using the SSMS it will create the model and you
can create and run a report from the report builder no problem.
"Amarnath" wrote:
> when you create report model, you need to use default in your data source
> properties, so that it takes the same and connects.
> second problem is: have you deployed your report model, only then you can
> see the entities and then you can create the reports.
> Amarnath
>
> "chabotwvu" wrote:
> > Okay, here is the scenario. I have an analysis services cube and a report
> > model generated from a OLAP datasource in reporting services. My first
> > problem is that when I try to create a report using the report builder from
> > my local pc I get data source connection errors, but if I remote desktop into
> > the dev server where reporting services is installed an complete the same
> > procedure everything works great. My second problem is that I cannot create
> > a report model from an OLAP datasource unless I am remoted into the report
> > server.
> >
> > Thanks, Andrew|||Here is the error message from the Report Server Log Files:
e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'dataSource1'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'dataSource1'.
--> Microsoft.AnalysisServices.AdomdClient.AdomdConnectionException:
The connection either timed out or was lost. --> System.IO.IOException:
Unable to read data from the transport connection:
An existing connection was forcibly closed by the remote host. -->
System.Net.Sockets.SocketException: An existing connection was forcibly
closed by the remote host
"chabotwvu" wrote:
> When I navigate to my OLAP datasource using SQL Server Management Studio and
> generate the model my datasource security is set to windows integrated
> security. The OLAP datasource impersonation information is set to use the
> service account; when I do this from SSMS on my local laptop I get connection
> errors, but if I remote desktop into the reporting services server and
> connect to reporting services using the SSMS it will create the model and you
> can create and run a report from the report builder no problem.
> "Amarnath" wrote:
> > when you create report model, you need to use default in your data source
> > properties, so that it takes the same and connects.
> >
> > second problem is: have you deployed your report model, only then you can
> > see the entities and then you can create the reports.
> >
> > Amarnath
> >
> >
> > "chabotwvu" wrote:
> >
> > > Okay, here is the scenario. I have an analysis services cube and a report
> > > model generated from a OLAP datasource in reporting services. My first
> > > problem is that when I try to create a report using the report builder from
> > > my local pc I get data source connection errors, but if I remote desktop into
> > > the dev server where reporting services is installed an complete the same
> > > procedure everything works great. My second problem is that I cannot create
> > > a report model from an OLAP datasource unless I am remoted into the report
> > > server.
> > >
> > > Thanks, Andrew

Report Builder and confirmed dimension

Hi Experts,

I have build a cube and placed report builder on it. I have a Dimensional model with two fact table. When i try to create a report it allows me to select measures from only one fact. It doesnt allow me to create report from two different fact and two different dimensions.

Please help

Regards

Neeraj

Hi, you can't never do that in report builder, because [Report Builder] model does not work with more them one fact table.|||

I believe Loobo is correct in stating that Report Builder doesn't accept more than one measure group/fact table. Report Builder seems to be focused on more of a relational database model which does not always work well with Analysis Services.

Thanks,
Bryan Smith

|||Thank You Guys for that Insight.

Report Builder and confirmed dimension

Hi Experts,

I have build a cube and placed report builder on it. I have a Dimensional model with two fact table. When i try to create a report it allows me to select measures from only one fact. It doesnt allow me to create report from two different fact and two different dimensions.

Please help

Regards

Neeraj

Hi, you can't never do that in report builder, because [Report Builder] model does not work with more them one fact table.|||

I believe Loobo is correct in stating that Report Builder doesn't accept more than one measure group/fact table. Report Builder seems to be focused on more of a relational database model which does not always work well with Analysis Services.

Thanks,
Bryan Smith

|||Thank You Guys for that Insight.