Problems displaying default value of first cascading parameters.

I have 5 cascading parameters. They all have default values. I would like the default value of each of these to be selected when the report opens.

It currently works correctly when I preview the report, however when I deploy the report to the server it does not. In the deployed report, the default value of the first parameter is not selected. However, when I select a value for this one, on postback the rest of these parameters get set to their default value. They're all configured the same. I'm confused as to why the first one doesn't default to its default value while the others do.

Got any ideas?

Here's how I have it configured:

Allow null value CHECKED

Allow blank value CHECKED

The rest are unchecked.

Available values: From query

Default Values: Non-queried with a value supplied that exists in the dataset.

This issue got resolved when I deleted all of my reports from the server and then redeployed them. Funny how that works...sql

Problems displaying default value of first cascading parameters.

I have 5 cascading parameters. They all have default values. I would like the default value of each of these to be selected when the report opens.

It currently works correctly when I preview the report, however when I deploy the report to the server it does not. In the deployed report, the default value of the first parameter is not selected. However, when I select a value for this one, on postback the rest of these parameters get set to their default value. They're all configured the same. I'm confused as to why the first one doesn't default to its default value while the others do.

Got any ideas?

Here's how I have it configured:

Allow null value CHECKED

Allow blank value CHECKED

The rest are unchecked.

Available values: From query

Default Values: Non-queried with a value supplied that exists in the dataset.

This issue got resolved when I deleted all of my reports from the server and then redeployed them. Funny how that works...

Problems Connecting to Server Due to Deliting of Default DB

Hlp!
I have made a stoopid mistake of deleting the DB that was sat to default with Enterprise Manager. Now I can't use Enterprise Manager to work with any of my DB's.

Don't get me wrong, the server is still running, and I am able to view all the old folders in IIS, I can log into and add content to different sites I am working with.
But Ican not add new DB's, make backups or modify excisting tables and so on.

There must be a way to make another Db my new defalut? Pls say it is, so I don't need to reinstall, cause then I will loose data the way it is now.

Pls tell me there is a someway easy way around this issue.

slopee
Sad n' bitterEXEC sp_defaultdb 'User', 'DB'|||I will try this in commandline, and put my username, and the DB i want for default

If this does not work I hope someone can give mestep by step guiding, that way I know what I am doing:)) I am not even sure this is to be run from cmd, or where i should run it:))

Will try this, and let you know how it went.

slopee|||Ok, sure what you wrote is totally correct, but I am afraid I am going to need more then that. I will need a step by step guide on howto do this, cause i didn't work from cmd line.

If someone knows what to do here, pls guide me.

slopee|||Clearly I need help. I can barely spell, ("Deliting" lol) how should I possible manage to apply the line you submitted?;-)

Come on y'all, surely there is someone how can give me basic details? I need it explained in details, and step-by-step pls.

s|||From MS Support (http://support.microsoft.com/default.aspx?scid=kb;en-us;307864&Product=sql):

f the user's default database no longer exists, or has been marked suspect, use the ISQL command line utility to change the user's default database to a database that is currently available for a connection.

1. At a command line prompt, type the following and then press ENTER: C:\>isql -E

2. At the isql prompt, type the following and then press ENTER: 1>sp_defaultdb 'user's_login', 'master'

3. At the second prompt, type the following and then press ENTER:2>go|||Great.

Thx y'all.

s

Problems after the install of the Hotfix

After installing SP1 and then the hotfix: http://support.microsoft.com/Default.aspx?id=918222

We now get the following error when trying to work with date parameters in Report Builder:

Query (6, 117) The '[VBA].[DateSerial]' function does not exist.
-
Semantic query execution failed.
-
Query execution failed for data set 'dataSet'.
-
An error has occurred during report processing.

Is this a known problem or is there some sort of something that I can reinstall?

Thanks!

Hi Louis, can you paste in RDL that fails?

thanks!

|||

Sure thing. The problem comes with the prompted Transaction Date MDY. Without this parameter, it runs fine.

Thanks for the help :)

<?xml version="1.0" encoding="utf-8"?>
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<Language>en-US</Language>
<BottomMargin>1.27cm</BottomMargin>
<RightMargin>1.27cm</RightMargin>
<rd:GridSpacing>0.318cm</rd:GridSpacing>
<DataSets>
<DataSet Name="dataSet">
<Query>
<DataSourceName>dataSource1</DataSourceName>
<CommandText>&lt;SemanticQuery xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:rb="http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder" xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"&gt;
&lt;Hierarchies&gt;
&lt;Hierarchy&gt;
&lt;BaseEntity&gt;
&lt;!--Donations--&gt;
&lt;EntityID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Entity_MeasureGroup_All_Petra_Donations&lt;/EntityID&gt;
&lt;/BaseEntity&gt;
&lt;Groupings&gt;
&lt;Grouping Name="Donation Payment Method"&gt;
&lt;Expression Name="Donation Payment Method"&gt;
&lt;Path&gt;
&lt;RolePathItem&gt;
&lt;!--Donation Payment Method--&gt;
&lt;RoleID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Role_MeasureGroupDimension_Entity_MeasureGroup_All_Petra_Donations_Entity_Dimension_Donation_Payment_Method_Entity_Dimension_All_Petra_Donation_Payment_Method&lt;/RoleID&gt;
&lt;/RolePathItem&gt;
&lt;/Path&gt;
&lt;EntityRef&gt;
&lt;!--Donation Payment Method--&gt;
&lt;EntityID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Entity_Dimension_Donation_Payment_Method&lt;/EntityID&gt;
&lt;/EntityRef&gt;
&lt;/Expression&gt;
&lt;Details&gt;
&lt;Expression Name="Donation Payment Method1"&gt;
&lt;AttributeRef&gt;
&lt;!--Donation Payment Method--&gt;
&lt;AttributeID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Attribute_Hierarchy_Donation_Payment_Method.Donation_Payment_Method&lt;/AttributeID&gt;
&lt;/AttributeRef&gt;
&lt;/Expression&gt;
&lt;/Details&gt;
&lt;/Grouping&gt;
&lt;Grouping Name="Core Cause Entity"&gt;
&lt;Expression Name="Core Cause Entity"&gt;
&lt;Path&gt;
&lt;RolePathItem&gt;
&lt;!--Partner Account--&gt;
&lt;RoleID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Role_MeasureGroupDimension_Entity_MeasureGroup_All_Petra_Donations_Entity_Dimension_Partner_Account_Entity_Dimension_All_Petra_Partner_Account&lt;/RoleID&gt;
&lt;/RolePathItem&gt;
&lt;/Path&gt;
&lt;AttributeRef&gt;
&lt;!--Core Cause Entity--&gt;
&lt;AttributeID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Attribute_Hierarchy_Partner_Account.Core_Cause_Entity&lt;/AttributeID&gt;
&lt;/AttributeRef&gt;
&lt;/Expression&gt;
&lt;/Grouping&gt;
&lt;Grouping Name="Distribution Name"&gt;
&lt;Expression Name="Distribution Name"&gt;
&lt;Path&gt;
&lt;RolePathItem&gt;
&lt;!--Fund Distribution--&gt;
&lt;RoleID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Role_MeasureGroupDimension_Entity_MeasureGroup_All_Petra_Donations_Entity_Dimension_Fund_Distribution_Entity_Dimension_All_Petra_Fund_Distribution&lt;/RoleID&gt;
&lt;/RolePathItem&gt;
&lt;/Path&gt;
&lt;AttributeRef&gt;
&lt;!--Distribution Name--&gt;
&lt;AttributeID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Attribute_Hierarchy_Fund_Distribution.Distribution_Name&lt;/AttributeID&gt;
&lt;/AttributeRef&gt;
&lt;/Expression&gt;
&lt;/Grouping&gt;
&lt;/Groupings&gt;
&lt;Filter&gt;
&lt;Expression Name="expr2"&gt;
&lt;Function&gt;
&lt;FunctionName&gt;GreaterThan&lt;/FunctionName&gt;
&lt;Arguments&gt;
&lt;Expression&gt;
&lt;Path&gt;
&lt;RolePathItem&gt;
&lt;!--Transaction Date--&gt;
&lt;RoleID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Role_MeasureGroupDimension_Entity_MeasureGroup_All_Petra_Donations_Entity_Dimension_Date_Entity_Dimension_All_Petra_Transaction_Date&lt;/RoleID&gt;
&lt;/RolePathItem&gt;
&lt;/Path&gt;
&lt;AttributeRef&gt;
&lt;!--MDY Date (Date)--&gt;
&lt;AttributeID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Attribute_Time_Attribute_Hierarchy_Date.`_Date&lt;/AttributeID&gt;
&lt;/AttributeRef&gt;
&lt;/Expression&gt;
&lt;Expression&gt;
&lt;ParameterRef&gt;
&lt;ParameterName&gt;Transaction Date MDY Date (Date)&lt;/ParameterName&gt;
&lt;/ParameterRef&gt;
&lt;/Expression&gt;
&lt;/Arguments&gt;
&lt;/Function&gt;
&lt;CustomProperties&gt;
&lt;CustomProperty Name="qd:FilterCondition" /&gt;
&lt;CustomProperty Name="qd:Filter" /&gt;
&lt;CustomProperty Name="qd:ContextEntityID"&gt;
&lt;Value xsi:type="xsd:string"&gt;http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations&lt;/Value&gt;
&lt;/CustomProperty&gt;
&lt;CustomProperty Name="qd:AutoChangeBaseEntity" /&gt;
&lt;CustomProperty Name="qd:Design"&gt;
&lt;Value xsi:type="xsd:string"&gt;expr3&lt;/Value&gt;
&lt;/CustomProperty&gt;
&lt;/CustomProperties&gt;
&lt;/Expression&gt;
&lt;/Filter&gt;
&lt;/Hierarchy&gt;
&lt;/Hierarchies&gt;
&lt;MeasureGroups&gt;
&lt;MeasureGroup&gt;
&lt;BaseEntity&gt;
&lt;!--Donations--&gt;
&lt;EntityID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Entity_MeasureGroup_All_Petra_Donations&lt;/EntityID&gt;
&lt;/BaseEntity&gt;
&lt;Measures&gt;
&lt;Expression Name="Transaction Amount"&gt;
&lt;AttributeRef&gt;
&lt;!--Transaction Amount--&gt;
&lt;AttributeID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Attribute_Measure_All_Petra_Transaction_Amount&lt;/AttributeID&gt;
&lt;/AttributeRef&gt;
&lt;/Expression&gt;
&lt;Expression Name="Transaction Count"&gt;
&lt;AttributeRef&gt;
&lt;!--Transaction Count--&gt;
&lt;AttributeID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Attribute_Measure_All_Petra_Transaction_Count&lt;/AttributeID&gt;
&lt;/AttributeRef&gt;
&lt;/Expression&gt;
&lt;/Measures&gt;
&lt;SubtotalSets&gt;
&lt;SubtotalSet&gt;
&lt;SubtotalMeasures&gt;
&lt;MeasureName&gt;Transaction Amount&lt;/MeasureName&gt;
&lt;MeasureName&gt;Transaction Count&lt;/MeasureName&gt;
&lt;/SubtotalMeasures&gt;
&lt;/SubtotalSet&gt;
&lt;SubtotalSet&gt;
&lt;SubtotalGroupings&gt;
&lt;GroupingName&gt;Donation Payment Method&lt;/GroupingName&gt;
&lt;/SubtotalGroupings&gt;
&lt;SubtotalMeasures&gt;
&lt;MeasureName&gt;Transaction Amount&lt;/MeasureName&gt;
&lt;MeasureName&gt;Transaction Count&lt;/MeasureName&gt;
&lt;/SubtotalMeasures&gt;
&lt;/SubtotalSet&gt;
&lt;SubtotalSet&gt;
&lt;SubtotalGroupings&gt;
&lt;GroupingName&gt;Donation Payment Method&lt;/GroupingName&gt;
&lt;GroupingName&gt;Core Cause Entity&lt;/GroupingName&gt;
&lt;/SubtotalGroupings&gt;
&lt;SubtotalMeasures&gt;
&lt;MeasureName&gt;Transaction Amount&lt;/MeasureName&gt;
&lt;MeasureName&gt;Transaction Count&lt;/MeasureName&gt;
&lt;/SubtotalMeasures&gt;
&lt;/SubtotalSet&gt;
&lt;/SubtotalSets&gt;
&lt;/MeasureGroup&gt;
&lt;/MeasureGroups&gt;
&lt;CalculatedAttributes&gt;
&lt;Expression Name="expr3"&gt;
&lt;Function&gt;
&lt;FunctionName&gt;And&lt;/FunctionName&gt;
&lt;Arguments&gt;
&lt;Expression&gt;
&lt;Function&gt;
&lt;FunctionName&gt;GreaterThan&lt;/FunctionName&gt;
&lt;Arguments&gt;
&lt;Expression&gt;
&lt;Path&gt;
&lt;RolePathItem&gt;
&lt;!--Transaction Date--&gt;
&lt;RoleID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Role_MeasureGroupDimension_Entity_MeasureGroup_All_Petra_Donations_Entity_Dimension_Date_Entity_Dimension_All_Petra_Transaction_Date&lt;/RoleID&gt;
&lt;/RolePathItem&gt;
&lt;/Path&gt;
&lt;AttributeRef&gt;
&lt;!--MDY Date (Date)--&gt;
&lt;AttributeID xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling"&gt;np:Attribute_Time_Attribute_Hierarchy_Date.MDY_Date&lt;/AttributeID&gt;
&lt;/AttributeRef&gt;
&lt;/Expression&gt;
&lt;Expression&gt;
&lt;ParameterRef&gt;
&lt;ParameterName&gt;Transaction Date MDY Date (Date)&lt;/ParameterName&gt;
&lt;/ParameterRef&gt;
&lt;/Expression&gt;
&lt;/Arguments&gt;
&lt;/Function&gt;
&lt;CustomProperties&gt;
&lt;CustomProperty Name="qd:FilterCondition" /&gt;
&lt;/CustomProperties&gt;
&lt;/Expression&gt;
&lt;Expression&gt;
&lt;Null /&gt;
&lt;CustomProperties&gt;
&lt;CustomProperty Name="qd:Unspecified" /&gt;
&lt;/CustomProperties&gt;
&lt;/Expression&gt;
&lt;/Arguments&gt;
&lt;/Function&gt;
&lt;CustomProperties&gt;
&lt;CustomProperty Name="qd:Filter" /&gt;
&lt;CustomProperty Name="qd:ContextEntityID"&gt;
&lt;Value xsi:type="xsd:string"&gt;http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations&lt;/Value&gt;
&lt;/CustomProperty&gt;
&lt;CustomProperty Name="qd:AutoChangeBaseEntity" /&gt;
&lt;/CustomProperties&gt;
&lt;/Expression&gt;
&lt;/CalculatedAttributes&gt;
&lt;Parameters&gt;
&lt;Parameter Name="Transaction Date MDY Date (Date)"&gt;
&lt;DataType&gt;DateTime&lt;/DataType&gt;
&lt;/Parameter&gt;
&lt;/Parameters&gt;
&lt;CustomProperties&gt;
&lt;CustomProperty Name="qd:PerspectiveID"&gt;
&lt;Value xsi:type="xsd:string"&gt;http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Perspective_Cube_Donations&lt;/Value&gt;
&lt;/CustomProperty&gt;
&lt;/CustomProperties&gt;
&lt;/SemanticQuery&gt;</CommandText>
<QueryParameters>
<QueryParameter Name="Transaction Date MDY Date (Date)">
<Value>=Parameters!TransactionDateMDYDateDate.Value</Value>
</QueryParameter>
</QueryParameters>
</Query>
<Fields>
<Field Name="DonationPaymentMethod">
<DataField>Donation Payment Method</DataField>
</Field>
<Field Name="DonationPaymentMethod1">
<DataField>Donation Payment Method1</DataField>
</Field>
<Field Name="CoreCauseEntity">
<DataField>Core Cause Entity</DataField>
</Field>
<Field Name="DistributionName">
<DataField>Distribution Name</DataField>
</Field>
<Field Name="TransactionAmount">
<DataField>Transaction Amount</DataField>
</Field>
<Field Name="TransactionCount">
<DataField>Transaction Count</DataField>
</Field>
</Fields>
</DataSet>
</DataSets>
<DataSources>
<DataSource Name="dataSource1">
<DataSourceReference>/Models/UDM Model</DataSourceReference>
<rd:DataSourceID>8c35ebf2-199b-4a18-8ead-c64e8b722e47</rd:DataSourceID>
</DataSource>
</DataSources>
<PageHeight>21.59cm</PageHeight>
<LeftMargin>1.27cm</LeftMargin>
<ReportParameters>
<ReportParameter Name="TransactionDateMDYDateDate">
<DataType>DateTime</DataType>
<Prompt>Transaction Date MDY Date (Date)</Prompt>
</ReportParameter>
</ReportParameters>
<TopMargin>1.27cm</TopMargin>
<Width>25.4cm</Width>
<Body>
<Height>0cm</Height>
<ReportItems>
<Textbox Name="Title">
<Left>1.27cm</Left>
<Top>1.27cm</Top>
<CanGrow>true</CanGrow>
<Width>18.446cm</Width>
<Value>Giving by Date Range</Value>
<Style>
<FontFamily>Tahoma</FontFamily>
<TextAlign>Center</TextAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>18pt</FontSize>
<VerticalAlign>Middle</VerticalAlign>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CustomProperties>
<CustomProperty>
<Name>rb:Watermark</Name>
<Value>Click to add title</Value>
</CustomProperty>
</CustomProperties>
<Height>0.9525cm</Height>
</Textbox>
<Table Name="table">
<Footer>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ColSpan>3</ColSpan>
<ReportItems>
<Textbox Name="DonationPaymentMethod_SubtotalHeader">
<CanGrow>true</CanGrow>
<Value>Total</Value>
<Style>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>#c7d9f9</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionAmount_Total_3_3_3_3_3">
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=AGGREGATE(Fields!TransactionAmount.Value)</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>C</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionCount_Total_3_3_3_3_3">
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=AGGREGATE(Fields!TransactionCount.Value)</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>#,#</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.635cm</Height>
</TableRow>
</TableRows>
</Footer>
<Top>3.18cm</Top>
<TableGroups>
<TableGroup>
<Footer>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="blank">
<CanGrow>true</CanGrow>
<Value />
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Left>Solid</Left>
<Right>Solid</Right>
<Bottom>Solid</Bottom>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>White</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ColSpan>2</ColSpan>
<ReportItems>
<Textbox Name="textbox2">
<CanGrow>true</CanGrow>
<Value>Total</Value>
<Style>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>#c7d9f9</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionAmount_Total_3_3_3_3_1">
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=AGGREGATE(Fields!TransactionAmount.Value)</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>C</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionCount_Total_3_3_3_3_1">
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=AGGREGATE(Fields!TransactionCount.Value)</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>#,#</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.635cm</Height>
</TableRow>
</TableRows>
</Footer>
<Sorting>
<SortBy>
<SortExpression>=AGGREGATE(Fields!TransactionAmount.Value)</SortExpression>
<Direction>Descending</Direction>
</SortBy>
</Sorting>
<Grouping Name="table_DonationPaymentMethod">
<PageBreakAtEnd>true</PageBreakAtEnd>
<GroupExpressions>
<GroupExpression>=Fields!DonationPaymentMethod.Value</GroupExpression>
</GroupExpressions>
</Grouping>
</TableGroup>
<TableGroup>
<Footer>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="blank2">
<CanGrow>true</CanGrow>
<Value />
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Left>Solid</Left>
<Right>Solid</Right>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>White</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="blank3">
<CanGrow>true</CanGrow>
<Value />
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Left>Solid</Left>
<Right>Solid</Right>
<Bottom>Solid</Bottom>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>White</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="DistributionName_SubtotalHeader">
<CanGrow>true</CanGrow>
<Value>Total</Value>
<Style>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>#c7d9f9</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionAmount_Total_3_3_3_3_2">
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=AGGREGATE(Fields!TransactionAmount.Value)</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>C</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionCount_Total_3_3_3_3_2">
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=AGGREGATE(Fields!TransactionCount.Value)</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>#,#</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.635cm</Height>
</TableRow>
</TableRows>
</Footer>
<Grouping Name="table_CoreCauseEntity">
<GroupExpressions>
<GroupExpression>=Fields!CoreCauseEntity.Value</GroupExpression>
</GroupExpressions>
</Grouping>
</TableGroup>
</TableGroups>
<Details>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="DonationPaymentMethod_Value">
<DataElementOutput>Output</DataElementOutput>
<CanGrow>true</CanGrow>
<HideDuplicates>table_DonationPaymentMethod</HideDuplicates>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_Dimension_Donation_Payment_Method</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>Detail</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=Fields!DonationPaymentMethod1.Value</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Left>Solid</Left>
<Right>Solid</Right>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>White</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="CoreCauseEntity_Value">
<DataElementOutput>Output</DataElementOutput>
<CanGrow>true</CanGrow>
<HideDuplicates>table_CoreCauseEntity</HideDuplicates>
<Value>=Fields!CoreCauseEntity.Value</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Left>Solid</Left>
<Right>Solid</Right>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>White</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="DistributionName_Value">
<DataElementOutput>Output</DataElementOutput>
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_Dimension_Fund_Distribution</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>Detail</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=Fields!DistributionName.Value</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<BackgroundColor>White</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionAmount_Value">
<DataElementOutput>Output</DataElementOutput>
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=Fields!TransactionAmount.Value</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>C</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CustomProperties>
<CustomProperty>
<Name>rb:Group</Name>
<Value>table_DistributionName</Value>
</CustomProperty>
</CustomProperties>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionCount_Value">
<DataElementOutput>Output</DataElementOutput>
<CanGrow>true</CanGrow>
<Action>
<Drillthrough>
<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>
<Parameters>
<Parameter Name="rs:EntityID">
<Value>http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Entity_MeasureGroup_All_Petra_Donations</Value>
</Parameter>
<Parameter Name="rs:DrillType">
<Value>List</Value>
</Parameter>
<Parameter Name="rs:Command">
<Value>Drillthrough</Value>
</Parameter>
<Parameter Name="DrillthroughSourceQuery">
<Value>=DataSets!dataSet.RewrittenCommandText</Value>
</Parameter>
<Parameter Name="DrillthroughContext">
<Value>=CreateDrillthroughContext()</Value>
</Parameter>
</Parameters>
</Drillthrough>
</Action>
<Value>=Fields!TransactionCount.Value</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<Format>#,#</Format>
<BackgroundColor>#ffff99</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CustomProperties>
<CustomProperty>
<Name>rb:Group</Name>
<Value>table_DistributionName</Value>
</CustomProperty>
</CustomProperties>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.635cm</Height>
</TableRow>
</TableRows>
<Grouping Name="table_DistributionName">
<GroupExpressions>
<GroupExpression>=Fields!DistributionName.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<Sorting>
<SortBy>
<SortExpression>=Fields!TransactionAmount.Value</SortExpression>
<Direction>Descending</Direction>
</SortBy>
</Sorting>
</Details>
<Style />
<Width>0cm</Width>
<Height>0cm</Height>
<DataSetName>dataSet</DataSetName>
<TableColumns>
<TableColumn>
<Width>3.40026cm</Width>
<Visibility>
<Hidden>=Fields!DonationPaymentMethod1.IsMissing</Hidden>
</Visibility>
</TableColumn>
<TableColumn>
<Width>3.40026cm</Width>
<Visibility>
<Hidden>=Fields!CoreCauseEntity.IsMissing</Hidden>
</Visibility>
</TableColumn>
<TableColumn>
<Width>3.81447cm</Width>
<Visibility>
<Hidden>=Fields!DistributionName.IsMissing</Hidden>
</Visibility>
</TableColumn>
<TableColumn>
<Width>4.09435cm</Width>
<Visibility>
<Hidden>=Fields!TransactionAmount.IsMissing</Hidden>
</Visibility>
</TableColumn>
<TableColumn>
<Width>3.81213cm</Width>
<Visibility>
<Hidden>=Fields!TransactionCount.IsMissing</Hidden>
</Visibility>
</TableColumn>
</TableColumns>
<Header>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="DonationPaymentMethod_Header">
<CanGrow>true</CanGrow>
<UserSort>
<SortExpression>=Fields!DonationPaymentMethod1.Value</SortExpression>
<SortExpressionScope>table_DonationPaymentMethod</SortExpressionScope>
</UserSort>
<Value>Donation Payment Method</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Bold</FontWeight>
<BackgroundColor>#518ae5</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="CoreCauseEntity_Header">
<CanGrow>true</CanGrow>
<UserSort>
<SortExpression>=Fields!CoreCauseEntity.Value</SortExpression>
<SortExpressionScope>table_CoreCauseEntity</SortExpressionScope>
</UserSort>
<Value>Core Cause Entity</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Bold</FontWeight>
<BackgroundColor>#518ae5</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="DistributionName_Header">
<CanGrow>true</CanGrow>
<UserSort>
<SortExpression>=Fields!DistributionName.Value</SortExpression>
<SortExpressionScope>table_DistributionName</SortExpressionScope>
</UserSort>
<Value>Distribution Name</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Bold</FontWeight>
<BackgroundColor>#518ae5</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionAmount_Header">
<CanGrow>true</CanGrow>
<UserSort>
<SortExpression>=Fields!TransactionAmount.Value</SortExpression>
<SortExpressionScope>table_DistributionName</SortExpressionScope>
</UserSort>
<Value>Transaction Amount</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Bold</FontWeight>
<BackgroundColor>#518ae5</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="TransactionCount_Header">
<CanGrow>true</CanGrow>
<UserSort>
<SortExpression>=Fields!TransactionCount.Value</SortExpression>
<SortExpressionScope>table_DistributionName</SortExpressionScope>
</UserSort>
<Value>Transaction Count</Value>
<Style>
<Language>en-US</Language>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontFamily>Tahoma</FontFamily>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontWeight>Bold</FontWeight>
<BackgroundColor>#518ae5</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>1.19834cm</Height>
</TableRow>
</TableRows>
<RepeatOnNewPage>true</RepeatOnNewPage>
<FixedHeader>true</FixedHeader>
</Header>
<Left>1.272cm</Left>
</Table>
<Textbox Name="TotalRows">
<Left>1.27cm</Left>
<Top>7.62cm</Top>
<CanGrow>true</CanGrow>
<Width>16.51cm</Width>
<Value>=String.Format("Total rows" &amp; Chr(58) &amp; " {0}", COUNTROWS("dataSet"))</Value>
<Style>
<PaddingLeft>3pt</PaddingLeft>
<PaddingBottom>3pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<PaddingRight>3pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
</Style>
<CustomProperties>
<CustomProperty>
<Name>rb:SpecialContent</Name>
<Value>TotalRows</Value>
</CustomProperty>
</CustomProperties>
<Height>0.635cm</Height>
</Textbox>
<Textbox Name="FilterDescription">
<Left>1.27cm</Left>
<Top>8.89cm</Top>
<CanGrow>true</CanGrow>
<Width>16.51cm</Width>
<Value>Filter: Donations with: Transaction Date MDY Date (Date) after (prompted)</Value>
<Style>
<PaddingLeft>3pt</PaddingLeft>
<PaddingBottom>3pt</PaddingBottom>
<FontWeight>Normal</FontWeight>
<FontSize>8pt</FontSize>
<PaddingRight>3pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
</Style>
<CustomProperties>
<CustomProperty>
<Name>rb:SpecialContent</Name>
<Value>FilterDescription</Value>
</CustomProperty>
</CustomProperties>
<Height>1.27cm</Height>
</Textbox>
</ReportItems>
<Style />
</Body>
<PageWidth>27.94cm</PageWidth>
</Report>

|||

Any ideas? We are going to have to rebuild the server to avoid these issues really soon now (and I hate to be defeated :)

Louis

|||

Sorry for delay, I am looking into this.

We've never seen this error message before. Do you have any other servers where this report runs? Did it run on pre-SP1 bits?

<Edit>

Ok, I can't figure what exactly happens, and can't repro it.
Could you please modify ReportServer Web.Config:
<add name="Components" value="all,RunningJobs:3,SemanticQueryEngine:4,SemanticModelGenerator:2" />

and rerun the report (repro the problem). Then take the latest ReportServer__timestamp.log and see if there are any interesting stack traces at the end of the file?

Thanks! :)

|||

I am not rushing you because I didn't think you were checking into it. I thought you might not have any ideas and it was time to punt. If we do I will try adding the hotfix again after we reinstall sql server with SP1 just to see if it was the hotfix.

Yes, it did. They had a training class and there are quite a few of these reports from that class. So after I added the hotfix, we were testing things to see if they worked, and this was one of the few things that didn't. We are really pushing Report Builder to our clients to give them an ad hoc tool (for a great price :) but then we got this error.

I changed the setting, and it does show issues. I bolded what I thought were interesting. I should also note that our server is on the G: drive and not in C: (I didn't install it, and that person is gone now)

Basically we are taking a date dimension, then choosing the MDY Date format, choosing greater than, or something like that, right clicking the criteria and choosing Prompt. Then I run the report, click the date pick object, choose any date, and click run report. It starts to run then does this. To make sure it wasn't just upgraded reports, Tonight I took a dimension, chose two measures, and filtered like this on a date, same error.

Here is all of the trace stuff after it sets up the query, if you need more, feel free to ask. If you want to email me for quicker feedback, it is drsql@.hotmail.com, and I will be happy to talke by phone but I am not posting that here :)

Thanks for the help!

Query parameter: Transaction Date MDY Date (Date) = 6/5/2006 12:00:00 AM
Query has been compiled successfully.
w3wp!semanticqueryengine!5!6/14/2006-22:54:07:: i INFO: Semantic Query Command ID: 1. Target command type = ASSemanticQueryCommand
SELECT
{ [Measures].[Transaction Amount], [Measures].[Transaction Count] } on 0,
{ EXISTS( { { [Donation Payment Method].[Donation Payment Method].[All Donation Payment Method] } * { [Partner Account].[Core Cause Entity].[All Partner Account] } * { [Fund Distribution].[Distribution Name].[All Fund Distribution] } }, , "Donations" ), EXISTS( { [Donation Payment Method].[Donation Payment Method].Levels(1).Members * { [Partner Account].[Core Cause Entity].[All Partner Account] } * { [Fund Distribution].[Distribution Name].[All Fund Distribution] } }, , "Donations" ), EXISTS( { [Donation Payment Method].[Donation Payment Method].Levels(1).Members * [Partner Account].[Core Cause Entity].Levels(1).Members * { [Fund Distribution].[Distribution Name].[All Fund Distribution] } }, , "Donations" ), EXISTS( { [Donation Payment Method].[Donation Payment Method].Levels(1).Members * [Partner Account].[Core Cause Entity].Levels(1).Members * [Fund Distribution].[Distribution Name].Levels(1).Members }, , "Donations" ) } DIMENSION PROPERTIES MEMBER_TYPE, MEMBER_UNIQUE_NAME, MEMBER_NAME, MEMBER_VALUE on 1
FROM
(SELECT
{ ( Extract( filter( { [Transaction Date].[MDY Date].Levels(1).Members * { [Transaction Date].[Date].[All Periods] } }, ( [Transaction Date].[MDY Date].CurrentMember.membervalue > VBA!DateSerial( 2006, 6, 5 ) ) ), [Transaction Date].[MDY Date] ) , * ) } on 0
FROM
[Donations]
)

w3wp!semanticqueryengine!5!6/14/2006-22:54:07:: e ERROR: Throwing Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryEngineException: Semantic query execution failed. , ;
Info: Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryEngineException: Semantic query execution failed. > Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query (6, 181) The '[VBA].[DateSerial]' function does not exist.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
at Microsoft.AnalysisServices.Modeling.QueryExecution.ASSemanticQueryCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
End of inner exception stack trace
w3wp!processing!5!6/14/2006-22:54:10:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dataSet'., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dataSet'. > Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryEngineException: Semantic query execution failed. > Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query (6, 181) The '[VBA].[DateSerial]' function does not exist.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
at Microsoft.AnalysisServices.Modeling.QueryExecution.ASSemanticQueryCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
End of inner exception stack trace
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
End of inner exception stack trace
w3wp!processing!5!6/14/2006-22:54:10:: e ERROR: An exception has occurred in data source 'dataSet'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dataSet'. > Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryEngineException: Semantic query execution failed. > Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query (6, 181) The '[VBA].[DateSerial]' function does not exist.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
at Microsoft.AnalysisServices.Modeling.QueryExecution.ASSemanticQueryCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
End of inner exception stack trace
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
End of inner exception stack trace
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.FirstPassInit()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.Process()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet)
w3wp!processing!5!6/14/2006-22:54:10:: i INFO: Merge abort handler called for ID=-1. Aborting data sources ...
w3wp!processing!5!6/14/2006-22:54:10:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dataSet'. > Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryEngineException: Semantic query execution failed. > Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query (6, 181) The '[VBA].[DateSerial]' function does not exist.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
at Microsoft.AnalysisServices.Modeling.QueryExecution.ASSemanticQueryCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
End of inner exception stack trace
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
End of inner exception stack trace
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.FirstPassInit()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.Process()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet)
End of inner exception stack trace
w3wp!processing!5!6/14/2006-22:54:10:: w WARN: Data source 'dataSource1': Report processing has been aborted.
w3wp!processing!5!6/14/2006-22:54:10:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dataSet'. > Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryEngineException: Semantic query execution failed. > Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query (6, 181) The '[VBA].[DateSerial]' function does not exist.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
at Microsoft.AnalysisServices.Modeling.QueryExecution.ASSemanticQueryCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
End of inner exception stack trace
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
End of inner exception stack trace
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.FirstPassInit()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.Process()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet)
End of inner exception stack trace
w3wp!webserver!5!06/14/2006-22:54:10:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'dataSet'. > Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryEngineException: Semantic query execution failed. > Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query (6, 181) The '[VBA].[DateSerial]' function does not exist.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
at Microsoft.AnalysisServices.Modeling.QueryExecution.ASSemanticQueryCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
End of inner exception stack trace
at Microsoft.ReportingServices.SemanticQueryEngine.SemanticQueryCommandWrapper.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
End of inner exception stack trace
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.RunDataSetQuery()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.FirstPassInit()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.FirstPassProcess(Boolean& closeConnWhenFinish)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeReportDataSetNode.Process()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSetNode.ProcessConcurrent(Object threadSet)
End of inner exception stack trace
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.AbortHelper.ThrowAbortException(Int32 reportUniqueName)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.CheckAndThrowIfAborted()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.Merge.Process(ParameterInfoCollection parameters, Boolean mergeTran)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, ProcessingContext context)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, Boolean snapshotProcessing, Boolean processWithCachedData, GetReportChunk getChunkCallback, ErrorContext errorContext, DateTime executionTime, CreateReportChunk cacheDataCallback, ProcessingContext& context)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension renderer, DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc, CreateReportChunk cacheDataCallback, Boolean& dataCached)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc)
at Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext reportContext, ItemProperties properties, ParameterInfoCollection effectiveParameters, Guid reportId, ClientRequest session, String description, ReportSnapshot intermediateSnapshot, DataSourceInfoCollection thisReportDataSources, Boolean cachingRequested, Boolean isLinkedReport, Warning[]& warnings, ReportSnapshot& resultSnapshotData, DateTime& executionDateTime, RuntimeDataSourceInfoCollection& alldataSources, UserProfileState& usedUserProfile)
at Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters)
at Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
End of inner exception stack trace
at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService rs, CatalogItemContext reportContext, ClientRequest session, JobType type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport(HttpResponseStreamFactory streamFactory)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.DoStreamedOperation(StreamedOperation operation)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(ItemType itemType)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent()
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()

|||

This looks like a problem in AS server which is being called by semantic query engine to execute the final (MDX) query. I will forward this to AS ppl for further analysis.
Thanks!

|||

Totally thanks for your help. I figured this was something wierd.

Do you think it will take long to get something started on correcting it? I can probably only leave the server in this state another day or two before the hounds attack and we reinstall :)

Louis

|||We looked at it and it seems like an installation glitch...|||

So is it repairable, or will we need to to a reinstall? And do I reinstall the hotfix? Or SP1? Or start over with RTM?

|||

If you insalled SQL server on disk C then there should be a folder like: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin, which contains the binaries for the AS server. That folder should contain msmdvbanet.dll.

The data folder (like C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data) should contain folders like VBAMDX.0.asm and VBAMDXINTERNAL.0.asm. It should also contan files like VBAMDX.0.asm.xml and VBAMDXINTERNAL.0.asm.xml.

If something of the above is missing please let us know.

|||

I should mention that we are running on an instance named BI.

We didn't install it on C: (even though our norm is to install program files on c: and data on other drives ).

In c:\program files\microsoft sql server we only have: 80, 90

on G:\MSSQL\MSSQL.1\OLAP\bin

there is an msmdvbanet.dll

on H:\MSSQL$BI\AnalysisData\MSSQL.2\OLAP\Data

there is a VBAMDX.0.asm.xml file, and in it is a listing for:

G:\MSSQL$BI\MSSQL.2\OLAP\bin\msmdvbanet.dll

There is a G:\MSSQL$BI\MSSQL.3\Reporting Services, but no MSSQL.2, or any other number (I understand the numbering well enough)

It appears that we had a quite non-standard setup and the hotfix didn't take that into consideration. Let me know if you want me to send you the contents of any files. I think we are going to rebuild soon.

|||

So you have 2 instances, which you can run - default and BI, right? Or just one (BI)?

When you run the named BI instance, is it configured to run from G:\MSSQL$BI\MSSQL.2\OLAP\bin ?

|||

Just one instance. And it was the only one installed (I am trying to force everyone to get used to working with instances).

Actually the service (Named MSOLAP$BI, SQL Server Analysis Services (BI)) is running:

G:\MSSQL\MSSQL.1\OLAP\bin\msmdsrv.exe -s "G:\MSSQL\MSSQL.1\OLAP\Config"

Or did you want something else?

|||

Please open msmdsrv.ini from G:\MSSQL\MSSQL.1\OLAP\Config

Does it contain the following line?

<UseVBANet>1</UseVBANet>

Problem: Using Custom Code to provide default values for parameter

Hi, I have reports with parameters that use custom code, and when you hide
the parameters in the report manager the reports no longer work.
I thought it was a parameter dependancy problem, but have done the following
test to prove its not:
I have just created a report, with one parameter called prmUserID that gets
its value from my dll. The default non-queried value for this parameter is
set as follows:
=libIntranetReporting.clsGeneral.GetCurrentUser( User!UserID, True , False,
False )
The report displays a table, and the table references a dataset that uses
the parameter value. This is the string for the dataset:
="Select * from mhgroup.docusers where userid='" &
Parameters!prmUserID.Value & "'"
The report works fine when I deploy it to the report
manager. The parameter shows the value returned from my
dll correctly.
However, I changed the parameter properties of my report in report manager
and took the tick out of the prompt user checkbox. The report no longer
works - I'm pretty sure that my prmUserID is just parsing an empty string now
to the dataset. Maybe once you've hidden a parameter the code from my dll is
no longer called?
I also know its not a problem with my dll as I did the same test above but
used custom code directly in the report (ie added to the code tab of the
report properties dialog). This produced the same result - deployed it,
worked fine, hide the parameter and the code no longer seems to run.
I would be grateful if someone at MS could try and replicate this and let me
know if I'm doing something wrong or if its a bug.
My Firm is VERY keen to move forward with Reporting Services, the printing
issue (which I know is being addressed in SP2) and this parameter problem is
the only thing holding us back at the moment.
Thanks
JeanineHave you installed SP1?... I think that hidden parameters are NOT settable
unless you have SP1 installed...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
news:E953EF89-AD1F-408D-9729-AC99C109D784@.microsoft.com...
> Hi, I have reports with parameters that use custom code, and when you hide
> the parameters in the report manager the reports no longer work.
> I thought it was a parameter dependancy problem, but have done the
> following
> test to prove its not:
> I have just created a report, with one parameter called prmUserID that
> gets
> its value from my dll. The default non-queried value for this parameter
> is
> set as follows:
> =libIntranetReporting.clsGeneral.GetCurrentUser( User!UserID, True ,
> False,
> False )
> The report displays a table, and the table references a dataset that uses
> the parameter value. This is the string for the dataset:
> ="Select * from mhgroup.docusers where userid='" &
> Parameters!prmUserID.Value & "'"
> The report works fine when I deploy it to the report
> manager. The parameter shows the value returned from my
> dll correctly.
> However, I changed the parameter properties of my report in report manager
> and took the tick out of the prompt user checkbox. The report no longer
> works - I'm pretty sure that my prmUserID is just parsing an empty string
> now
> to the dataset. Maybe once you've hidden a parameter the code from my dll
> is
> no longer called?
> I also know its not a problem with my dll as I did the same test above but
> used custom code directly in the report (ie added to the code tab of the
> report properties dialog). This produced the same result - deployed it,
> worked fine, hide the parameter and the code no longer seems to run.
> I would be grateful if someone at MS could try and replicate this and let
> me
> know if I'm doing something wrong or if its a bug.
> My Firm is VERY keen to move forward with Reporting Services, the printing
> issue (which I know is being addressed in SP2) and this parameter problem
> is
> the only thing holding us back at the moment.
> Thanks
> Jeanine|||Thanks for you reply, yes I do have SP1 installed.
"Wayne Snyder" wrote:
> Have you installed SP1?... I think that hidden parameters are NOT settable
> unless you have SP1 installed...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
> news:E953EF89-AD1F-408D-9729-AC99C109D784@.microsoft.com...
> > Hi, I have reports with parameters that use custom code, and when you hide
> > the parameters in the report manager the reports no longer work.
> >
> > I thought it was a parameter dependancy problem, but have done the
> > following
> > test to prove its not:
> >
> > I have just created a report, with one parameter called prmUserID that
> > gets
> > its value from my dll. The default non-queried value for this parameter
> > is
> > set as follows:
> >
> > =libIntranetReporting.clsGeneral.GetCurrentUser( User!UserID, True ,
> > False,
> > False )
> >
> > The report displays a table, and the table references a dataset that uses
> > the parameter value. This is the string for the dataset:
> >
> > ="Select * from mhgroup.docusers where userid='" &
> > Parameters!prmUserID.Value & "'"
> >
> > The report works fine when I deploy it to the report
> > manager. The parameter shows the value returned from my
> > dll correctly.
> >
> > However, I changed the parameter properties of my report in report manager
> > and took the tick out of the prompt user checkbox. The report no longer
> > works - I'm pretty sure that my prmUserID is just parsing an empty string
> > now
> > to the dataset. Maybe once you've hidden a parameter the code from my dll
> > is
> > no longer called?
> >
> > I also know its not a problem with my dll as I did the same test above but
> > used custom code directly in the report (ie added to the code tab of the
> > report properties dialog). This produced the same result - deployed it,
> > worked fine, hide the parameter and the code no longer seems to run.
> >
> > I would be grateful if someone at MS could try and replicate this and let
> > me
> > know if I'm doing something wrong or if its a bug.
> >
> > My Firm is VERY keen to move forward with Reporting Services, the printing
> > issue (which I know is being addressed in SP2) and this parameter problem
> > is
> > the only thing holding us back at the moment.
> >
> > Thanks
> > Jeanine
>
>|||You need to change the report parameter property. Set the PROMPT string to
"" and the prompt value to TRUE.
It will not display the prompt but at least it will be updatable.
=-Chris
"Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
news:E953EF89-AD1F-408D-9729-AC99C109D784@.microsoft.com...
> Hi, I have reports with parameters that use custom code, and when you hide
> the parameters in the report manager the reports no longer work.
> I thought it was a parameter dependancy problem, but have done the
> following
> test to prove its not:
> I have just created a report, with one parameter called prmUserID that
> gets
> its value from my dll. The default non-queried value for this parameter
> is
> set as follows:
> =libIntranetReporting.clsGeneral.GetCurrentUser( User!UserID, True ,
> False,
> False )
> The report displays a table, and the table references a dataset that uses
> the parameter value. This is the string for the dataset:
> ="Select * from mhgroup.docusers where userid='" &
> Parameters!prmUserID.Value & "'"
> The report works fine when I deploy it to the report
> manager. The parameter shows the value returned from my
> dll correctly.
> However, I changed the parameter properties of my report in report manager
> and took the tick out of the prompt user checkbox. The report no longer
> works - I'm pretty sure that my prmUserID is just parsing an empty string
> now
> to the dataset. Maybe once you've hidden a parameter the code from my dll
> is
> no longer called?
> I also know its not a problem with my dll as I did the same test above but
> used custom code directly in the report (ie added to the code tab of the
> report properties dialog). This produced the same result - deployed it,
> worked fine, hide the parameter and the code no longer seems to run.
> I would be grateful if someone at MS could try and replicate this and let
> me
> know if I'm doing something wrong or if its a bug.
> My Firm is VERY keen to move forward with Reporting Services, the printing
> issue (which I know is being addressed in SP2) and this parameter problem
> is
> the only thing holding us back at the moment.
> Thanks
> Jeanine|||Thanks for that. I tried that and it worked - as long as you don't then go
and edit the report parameters in report manager.
What I would really like to do is have linked reports, one with a boolean
parameter set to true and one with a boolean parameter set to false.
So as soon as I use the report manager to alter the report parameter
properties (even though I've done you've said below), the reports don't work
properly again.
I still think this is a bug of some kind, and am hoping MS come up with a
fix for this.
Jeanine
"Christopher Conner" wrote:
> You need to change the report parameter property. Set the PROMPT string to
> "" and the prompt value to TRUE.
> It will not display the prompt but at least it will be updatable.
> =-Chris
>
> "Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
> news:E953EF89-AD1F-408D-9729-AC99C109D784@.microsoft.com...
> > Hi, I have reports with parameters that use custom code, and when you hide
> > the parameters in the report manager the reports no longer work.
> >
> > I thought it was a parameter dependancy problem, but have done the
> > following
> > test to prove its not:
> >
> > I have just created a report, with one parameter called prmUserID that
> > gets
> > its value from my dll. The default non-queried value for this parameter
> > is
> > set as follows:
> >
> > =libIntranetReporting.clsGeneral.GetCurrentUser( User!UserID, True ,
> > False,
> > False )
> >
> > The report displays a table, and the table references a dataset that uses
> > the parameter value. This is the string for the dataset:
> >
> > ="Select * from mhgroup.docusers where userid='" &
> > Parameters!prmUserID.Value & "'"
> >
> > The report works fine when I deploy it to the report
> > manager. The parameter shows the value returned from my
> > dll correctly.
> >
> > However, I changed the parameter properties of my report in report manager
> > and took the tick out of the prompt user checkbox. The report no longer
> > works - I'm pretty sure that my prmUserID is just parsing an empty string
> > now
> > to the dataset. Maybe once you've hidden a parameter the code from my dll
> > is
> > no longer called?
> >
> > I also know its not a problem with my dll as I did the same test above but
> > used custom code directly in the report (ie added to the code tab of the
> > report properties dialog). This produced the same result - deployed it,
> > worked fine, hide the parameter and the code no longer seems to run.
> >
> > I would be grateful if someone at MS could try and replicate this and let
> > me
> > know if I'm doing something wrong or if its a bug.
> >
> > My Firm is VERY keen to move forward with Reporting Services, the printing
> > issue (which I know is being addressed in SP2) and this parameter problem
> > is
> > the only thing holding us back at the moment.
> >
> > Thanks
> > Jeanine
>
>|||Well first off - users shouldn't have rights to modify the report
parameters.
Second, I set those properties in the report designer - not off the report
manager. It would be a pain to update those reports everytime I did a
deployment.
What happens when you do this inside your report designer with your linked
report?
I'll see if I can replicate your issue here, but otherwise I haven't run
into any problems - albeit just a few quirks like the solution I just gave
you to not show parameters but yet allow them to be updatable.
=-Chris
"Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
news:038B93E0-E09F-487E-877F-FC1F2DCDB0E9@.microsoft.com...
> Thanks for that. I tried that and it worked - as long as you don't then
> go
> and edit the report parameters in report manager.
> What I would really like to do is have linked reports, one with a boolean
> parameter set to true and one with a boolean parameter set to false.
> So as soon as I use the report manager to alter the report parameter
> properties (even though I've done you've said below), the reports don't
> work
> properly again.
> I still think this is a bug of some kind, and am hoping MS come up with a
> fix for this.
> Jeanine
>
> "Christopher Conner" wrote:
>> You need to change the report parameter property. Set the PROMPT string
>> to
>> "" and the prompt value to TRUE.
>> It will not display the prompt but at least it will be updatable.
>> =-Chris
>>
>> "Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
>> news:E953EF89-AD1F-408D-9729-AC99C109D784@.microsoft.com...
>> > Hi, I have reports with parameters that use custom code, and when you
>> > hide
>> > the parameters in the report manager the reports no longer work.
>> >
>> > I thought it was a parameter dependancy problem, but have done the
>> > following
>> > test to prove its not:
>> >
>> > I have just created a report, with one parameter called prmUserID that
>> > gets
>> > its value from my dll. The default non-queried value for this
>> > parameter
>> > is
>> > set as follows:
>> >
>> > =libIntranetReporting.clsGeneral.GetCurrentUser( User!UserID, True ,
>> > False,
>> > False )
>> >
>> > The report displays a table, and the table references a dataset that
>> > uses
>> > the parameter value. This is the string for the dataset:
>> >
>> > ="Select * from mhgroup.docusers where userid='" &
>> > Parameters!prmUserID.Value & "'"
>> >
>> > The report works fine when I deploy it to the report
>> > manager. The parameter shows the value returned from my
>> > dll correctly.
>> >
>> > However, I changed the parameter properties of my report in report
>> > manager
>> > and took the tick out of the prompt user checkbox. The report no
>> > longer
>> > works - I'm pretty sure that my prmUserID is just parsing an empty
>> > string
>> > now
>> > to the dataset. Maybe once you've hidden a parameter the code from my
>> > dll
>> > is
>> > no longer called?
>> >
>> > I also know its not a problem with my dll as I did the same test above
>> > but
>> > used custom code directly in the report (ie added to the code tab of
>> > the
>> > report properties dialog). This produced the same result - deployed
>> > it,
>> > worked fine, hide the parameter and the code no longer seems to run.
>> >
>> > I would be grateful if someone at MS could try and replicate this and
>> > let
>> > me
>> > know if I'm doing something wrong or if its a bug.
>> >
>> > My Firm is VERY keen to move forward with Reporting Services, the
>> > printing
>> > issue (which I know is being addressed in SP2) and this parameter
>> > problem
>> > is
>> > the only thing holding us back at the moment.
>> >
>> > Thanks
>> > Jeanine
>>|||Hi,
1) Users will not be modifying report parameters settings. They will
however be able to use the prms that I set as being visible.
2) What I'm trying to achieve is to have 1 main report and create from this,
several linked reports. By linked reports, I'm referring to the ability to
create a linked report from another report in Report manager. These linked
reports would have different parameter settings. This way I can use the
parameter information to tailor 1 main report, dependant upon the parameter
values. This saves me from having to create multiple reports in the report
designer, that contain basically the same information.
I tried your suggestion, with one of my production reports that has quite a
few parameters, and it worked fine. However to achieve 2) I will need to
create from this a linked report, change the parameter settings - which will
involve things such as changing a boolean prm from true to false etc.
If it is indeed a problem it is very easy to replicate, just create a report
with a parameter and set the default value of the parameter to a string
returned from a function in the custom code of the report. Use this
parameter in the datasource of the report, eg, ="Select * from
mhgroup.docusers where userid='" &
Parameters!prmUserID.Value & "'"
Deploy the report, use the report manager to hide the parameter, and the
report should then no longer display the correct information (because the
default value of the parameter was not populated with the custom code value).
Thanks very much.
"Christopher Conner" wrote:
> Well first off - users shouldn't have rights to modify the report
> parameters.
> Second, I set those properties in the report designer - not off the report
> manager. It would be a pain to update those reports everytime I did a
> deployment.
> What happens when you do this inside your report designer with your linked
> report?
> I'll see if I can replicate your issue here, but otherwise I haven't run
> into any problems - albeit just a few quirks like the solution I just gave
> you to not show parameters but yet allow them to be updatable.
> =-Chris
>
> "Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
> news:038B93E0-E09F-487E-877F-FC1F2DCDB0E9@.microsoft.com...
> > Thanks for that. I tried that and it worked - as long as you don't then
> > go
> > and edit the report parameters in report manager.
> >
> > What I would really like to do is have linked reports, one with a boolean
> > parameter set to true and one with a boolean parameter set to false.
> >
> > So as soon as I use the report manager to alter the report parameter
> > properties (even though I've done you've said below), the reports don't
> > work
> > properly again.
> >
> > I still think this is a bug of some kind, and am hoping MS come up with a
> > fix for this.
> >
> > Jeanine
> >
> >
> > "Christopher Conner" wrote:
> >
> >> You need to change the report parameter property. Set the PROMPT string
> >> to
> >> "" and the prompt value to TRUE.
> >>
> >> It will not display the prompt but at least it will be updatable.
> >>
> >> =-Chris
> >>
> >>
> >>
> >> "Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
> >> news:E953EF89-AD1F-408D-9729-AC99C109D784@.microsoft.com...
> >> > Hi, I have reports with parameters that use custom code, and when you
> >> > hide
> >> > the parameters in the report manager the reports no longer work.
> >> >
> >> > I thought it was a parameter dependancy problem, but have done the
> >> > following
> >> > test to prove its not:
> >> >
> >> > I have just created a report, with one parameter called prmUserID that
> >> > gets
> >> > its value from my dll. The default non-queried value for this
> >> > parameter
> >> > is
> >> > set as follows:
> >> >
> >> > =libIntranetReporting.clsGeneral.GetCurrentUser( User!UserID, True ,
> >> > False,
> >> > False )
> >> >
> >> > The report displays a table, and the table references a dataset that
> >> > uses
> >> > the parameter value. This is the string for the dataset:
> >> >
> >> > ="Select * from mhgroup.docusers where userid='" &
> >> > Parameters!prmUserID.Value & "'"
> >> >
> >> > The report works fine when I deploy it to the report
> >> > manager. The parameter shows the value returned from my
> >> > dll correctly.
> >> >
> >> > However, I changed the parameter properties of my report in report
> >> > manager
> >> > and took the tick out of the prompt user checkbox. The report no
> >> > longer
> >> > works - I'm pretty sure that my prmUserID is just parsing an empty
> >> > string
> >> > now
> >> > to the dataset. Maybe once you've hidden a parameter the code from my
> >> > dll
> >> > is
> >> > no longer called?
> >> >
> >> > I also know its not a problem with my dll as I did the same test above
> >> > but
> >> > used custom code directly in the report (ie added to the code tab of
> >> > the
> >> > report properties dialog). This produced the same result - deployed
> >> > it,
> >> > worked fine, hide the parameter and the code no longer seems to run.
> >> >
> >> > I would be grateful if someone at MS could try and replicate this and
> >> > let
> >> > me
> >> > know if I'm doing something wrong or if its a bug.
> >> >
> >> > My Firm is VERY keen to move forward with Reporting Services, the
> >> > printing
> >> > issue (which I know is being addressed in SP2) and this parameter
> >> > problem
> >> > is
> >> > the only thing holding us back at the moment.
> >> >
> >> > Thanks
> >> > Jeanine
> >>
> >>
> >>
>
>|||i myself are having a similar problem
i believe its a BUG in report manager,
that changing any of the options for parameters in report manager
(which is what is needed to be done to make a writable hidden
parameter) causes default calculations (even query based) to not work
for parameters that are not pull down boxes.|||Thanks for that. Its nice to know I'm not the only one experiencing this
problem. I'm hoping somone from MS may be able to shed some light on this as
well.
"klumsy@.xtra.co.nz" wrote:
> i myself are having a similar problem
> i believe its a BUG in report manager,
> that changing any of the options for parameters in report manager
> (which is what is needed to be done to make a writable hidden
> parameter) causes default calculations (even query based) to not work
> for parameters that are not pull down boxes.
>|||Please check this related thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5d83b939-71ab-47fa-9f85-9d15d90dacb9
Also check my recent posting in that same thread for a possible workaround
on RS 2000 (specifying hidden parameters through report designer).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
news:F1B09944-8648-49FD-95AE-66004ECD212D@.microsoft.com...
> Thanks for that. Its nice to know I'm not the only one experiencing this
> problem. I'm hoping somone from MS may be able to shed some light on this
> as
> well.
>
> "klumsy@.xtra.co.nz" wrote:
>> i myself are having a similar problem
>> i believe its a BUG in report manager,
>> that changing any of the options for parameters in report manager
>> (which is what is needed to be done to make a writable hidden
>> parameter) causes default calculations (even query based) to not work
>> for parameters that are not pull down boxes.
>>|||Thanks Robert. I'll look forward to the release of Yukon.
"Robert Bruckner [MSFT]" wrote:
> Please check this related thread:
> http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5d83b939-71ab-47fa-9f85-9d15d90dacb9
> Also check my recent posting in that same thread for a possible workaround
> on RS 2000 (specifying hidden parameters through report designer).
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Jeanine" <Jeanine@.discussions.microsoft.com> wrote in message
> news:F1B09944-8648-49FD-95AE-66004ECD212D@.microsoft.com...
> > Thanks for that. Its nice to know I'm not the only one experiencing this
> > problem. I'm hoping somone from MS may be able to shed some light on this
> > as
> > well.
> >
> >
> > "klumsy@.xtra.co.nz" wrote:
> >
> >> i myself are having a similar problem
> >> i believe its a BUG in report manager,
> >> that changing any of the options for parameters in report manager
> >> (which is what is needed to be done to make a writable hidden
> >> parameter) causes default calculations (even query based) to not work
> >> for parameters that are not pull down boxes.
> >>
> >>
>
>